Does update.php need to be manually run after running plugin manager's update feature, or are all necessary DB adjustments made automatically?
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 336991-plugin-manager-update-php-D6.patch | 1.96 KB | dave reid |
| #9 | 336991-plugin-manager-update-php-D6.patch | 1.78 KB | dave reid |
Comments
Comment #1
jabapyth commentedcurrently it is not automatically done. I will work on this.
Comment #2
jabapyth commentedhmmm actually, this is a wont fix -- database adjustments should be manually overseen.
Comment #3
Anonymous (not verified) commentedSince update.php does not automatically update modules when the page is visited, rather requires some form of user interaction (to approve of the suggested update,) it should be perfectly safe to redirect the user to update.php anytime an module is updated.
Comment #4
fletchgqc commentedYes - or at least update the success text to remind the user that they need to do this, with a link to the update page. I think this would be better than a confused user suddenly ending up on this page and wondering why.
Comment #5
Anonymous (not verified) commentedComment #6
bsimon commentedA link to the update page at the appropriate time sounds like a very good idea. Because of the vague warnings it contains, the Update.php process is actually quite confusing and alarming for people who don't understand how it works and what it does (in other words for many new Drupal admins).
Comment #7
dave reidMarked #362207: Remind users to run update.php after updates as a duplicate of this issue.
Comment #8
ibandyop commented+1 for a link to update.php excellent module saves me a lot of time.
+5 for documenting plan for next version i.e., plugin manager 2
Comment #9
dave reidHere's a patch that fixes the links to README.txt if you don't keep your modules in the sites/all/modules directory (e.g. sites/mysite.com/modules). After all modules are installed, it checks if there are any new updates and if so, shows a link to run update.php (the code is lifted from system_requirements). Please give this a test and review!
Comment #10
dave reidQuick change to check if the module's README.txt actually exists. If not, don't show the link to it. We don't want to link to things that will 404...it's confusing to the user.