I entered some bad php into a template and now when I view any node of that type, or the template edit page for the type, I get part of the node content and the bad php with an error. Is there a way I can manually "reset" the nodes template--perhaps a url I can use? I looked at the code, but the "reset" submit button runs with some js and I don't know if I can enter code on the page to replicate the function.

I would normally just go into the DB, but I don't have phpmyadmin or anything to easily go through the tables on this server.

Comments

inforeto’s picture

inforeto commented

This module should have a delete or disable link.
Or at least not to run the code in the editing page.
A page to a blank form to resubmit the template should work too.

Suggestions on implementation?

Here's duplicates:
http://drupal.org/node/123061
http://drupal.org/node/137719

jrglasgow’s picture

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

Goto admin/content/templates will allow you to select the node type, then you can reset, or fix the problem.
Does this fix your problem?

inforeto’s picture

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

That's not possible because you get the php error on the template page.

To reset from the database:
update contemplate set body = "blank text" where type = "content_type_name";

There should be a way to reset templates, would this take a feature request or a bug request?

inforeto’s picture

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

ok. leaving this as support request

here's related:
http://drupal.org/node/101144
http://drupal.org/node/113980
http://drupal.org/node/123061
http://drupal.org/node/137719
http://drupal.org/node/220374

jrglasgow’s picture

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

the ability to delete the template(this will remove the row in the database for that template) will be on the admin/content/templates page, this will appear in 5.x-1.9 releasing tonight

inforeto’s picture

inforeto commented

thanks! a much wanted feature.

jrglasgow’s picture

jrglasgow commented
Status: Active » Fixed
Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

primalmedia’s picture

primalmedia commented

Actually you may not have to delete it. I saved my [explative deleted] by deleting the offending code in phpMyAdmin. All I did was search for the exact phrase and I was able to isolate and remove it without having ot re-create an entire Content Type. Whew!

Adam
www.primalmedia.com

mscheine’s picture

mscheine commented

Yep, going to PHPMyAdmin worked for me as well. Go to the Acquia-Drupal database (if you're using Acquia Drupal), and all your custom templates should be on the table "contemplate". Change the body to remove the offending code and you're good to go.

DropInTheOcean’s picture

DropInTheOcean commented

Hi For Drupal 6 - Just in case you don't have access to PHPMyAdmin (and DBA module is unavailable).... You can export the Contemplate table via the 'Backup and Migrate module'. Then you can delete the problematic template on admin/content/types/templates. Then you can obtain a backup of the template from the exported Backup and Migrate file (I imported it to a local version of phpMyAdmin). Modify before re-trying.

sockah’s picture

sockah commented

Beautiful. Using PHPMyAdmin to cut out the bad php just saved me a ton of time.

Not sure why, but when I have bad PHP code in Contemplate, I can't edit the Contemplate fields any longer. When I try to edit, I'm instead taken to actual node content like the original poster. This is in Drupal 6 for me.

inforeto’s picture

inforeto commented

PHP is sensitive to bad code in eval, which is the case with templates.
e.g. things like drupal_goto take you to the node in the same fashion, breaking cron.

Another way to work around is to open two browser tabs with the contemplate fields, so you can clear from the 2nd.