I applied the patch from another issue (http://drupal.org/node/573500) that had similar symptons, but to no avail.

When I click on the link to edit a custom content type's contemplate, the resulting page is blank. No error messages displayed. If I view source, it is totally blank.

Not sure what to do next.
The apache2 log file says this:

 192.168.0.102 - - [18/Jun/2010:08:17:28 -0500] "GET /admin/content/node-type/pottery/template HTTP/1.1" 500 398 "http://madden.homedns.org/admin/content/types/templates" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3"

I was ready to show the client the page layout but needed to make some final edits. Drat! I can try to revert to a backup...

Comments

jrglasgow’s picture

jrglasgow commented
Status: Active » Postponed (maintainer needs more info)

what does the apache2 error_log say?

maddentim’s picture

maddentim commented

It seems that the root cause of issue was caused by a computed CCK field checking the status of a flag to decide if something was available. If it was flagged, it was supposed drive a computed cck field that was embedded in the contemplate. While the flag would have been nice easy for my client to click available or not, it wasn't tight enough even without it breaking the contemplate field here. I ended up backtracking and recreating what I was building without flag using just a CCK field.

In the end, I really don't understand why that branch of work with the flag broke our contemplate edit field. Even if I took out the reference to the flag from the computed field and / or disabled / uninstalled flag module completely, I just could not edit the contemplate for this content type. I back tracked to a backup from just before I start the branch and have what I need working fine now (although now that I don't have flag's nice javascript check it on / off interface, I will need to find a method to let her change the status of a piece without going into the full node edit form...)

Anyhow, so far as I need, we can let this issue pass...

For what it is worth, here is what the apache error log had for the edit attempt that I pasted before:

[Fri Jun 18 08:17:29 2010] [error] [client 192.168.0.102] PHP Fatal error:  Call to a member function is_flagged() on a non-object in /home/tim/public_html/cherie/includes/common.inc(1699) : eval()'d code on line 2, referer: http://madden.homedns.org/admin/content/types/templates

Thanks for taking a look. Gotta love the backup / migrate module! Use it and use it often! In fact, I am going to go save a backup of my now working code right now :)

maddentim’s picture

maddentim commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

I ended up finding the problem code in the database. The root issue was not from contemplate's code. Thanks.

dalegrebey’s picture

dalegrebey commented

I ended up finding the problem code in the database. The root issue was not from contemplate's code. Thanks.

...do tell?

maddentim’s picture

maddentim commented

As I vaguely recall, it was some php code I had put into an individual node that was calling the non-existent (in this install) is_flagged() function. I had thought I had just put it in the contemplate but apparently in my tinkering, I put it in a node too. I had to use phpmyadmin and manually get the code out of the node...

gaellafond’s picture

gaellafond commented

FYI:
#1119036: Error 500 when executing the cron
Similar symptoms, different cause.