Closed (fixed)
Project:
Node Form Template
Version:
6.x-1.0-beta3
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 Mar 2009 at 23:09 UTC
Updated:
13 May 2009 at 22:50 UTC
Hi Sorry to be a PITA but here is what I have done exactly:
1) Installed the module
2) copied node-form.tpl.php to themes\garland\node-form-autowxob.tpl.php
3) edited the file themes\garland\node-form-autowxob.tpl.php to read:
<?php ?>
<div class="node-form">
<div class="standard">
<?php print $standard; ?>
</div>
<?php print $admin; ?>
<?php print $buttons; ?>
<!-- this is crap to test the template-->
</div>
4) rebuilt the theme registry and deleted all caches
5) tried to create a new autowxob and could not find my comment in the source code of the page
So I am confused, am I doing something wrong here?
Comments
Comment #1
afox commentedI had the same thing. Apparently the content type specific templates are not working.
I just used a short code to determine the content type in node-form.tpl.php:
Comment #2
effulgentsia commentedI just tried it and it works for me. One thing to be aware of is that to make a type-specific tpl file work, you also need the base tpl file in the same folder. So you would need both a copy of node-form.tpl.php (which could be an exact copy of the one that comes with the module or a customized one if you want a customization to apply to all node forms) AND a node-form-TYPE.tpl.php in your theme's folder. This is a generic rule for Drupal 6 which is documented here: http://drupal.org/node/190815#template-suggestions.
@spydmobile: If this works for you, please mark the issue fixed. If not, please add another comment. Thanks.
Comment #3
spydmobile commentedHey thanks! I Indeed did *NOT* have the node-form.tpl.php file in the garland folder, unfortuanately
1) I placed it there,
2) used the devel empty cache function
3) Clicked to created a new autowxob
4) and checked the source of the node creation form and still did not find my comment,
5) so I can only conclude that this did not solve my problem.
I am willing to try whatever else you guys can suggest.
Comment #4
joshmillerOn the homepage of the module, the maintainer says that the content type issue was resolved with beta3. Trying installing beta3 and report back.
Josh
Comment #5
spydmobile commentedOk, it fixed the problem but created a new one, I will open a new ticket.
Thanks folks!!!