6.x-1.1 Requires update.php to be called
thekevinday - June 2, 2009 - 21:02
| Project: | Content Templates (Contemplate) |
| Version: | 6.x-1.1 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
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.
#1
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."
#2
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.