Immediately after updating to version 1.1, I could no longer access any contemplates.
I would get page not found.

I decided to run update.php, even though there are 0 updates to be made.
This somehow fixes the problem.

Perhaps cache needs to be regenerated with this update?

Please add an entry such that contemplate appears on the update.php page as needing to be updated.

Comments

Anonymous’s picture

Anonymous (not verified) commented

Personally I dont see the need for this "feature"

Especially as it clearly states on the Modules page

"It is important that update.php is run every time a module is updated to a newer version."

thekevinday’s picture

thekevinday commented

My concern is that it is misleading when there are 0 updates to be made, I click submit anyway and then it says 0 updates were applied.

It suggests that nothing was done, despite the opposite.

alxp’s picture

alxp commented

The "number of updates to be made" only counts database table changes I believe. Modules still might need to update things like variables that don't require table changes. This is "normal" for Drupal but can be a bit of a gotcha if you don't run update.php. I think this is more of a general shortcoming of the update system rather than a specific problem with Contemplate.

jrglasgow’s picture

jrglasgow commented
Status: Active » Closed (won't fix)