Maybe there is, I just don't know what I'm looking for. Or a simpler way to track down included/third-party plugins. In the future, it would be nice to just have Moodle enable it's OWN plugins, and the let administrators enable each plugin AFTER upgrade installation. I have a backup of our 3.11 site, and it's not imperative that this site is fixed, it is just preferred. I have learned my lessen from it and will just build from scratch next time. I used Softaculous because it was easy to use initially and I haven't had any issues with updates in the past. Totally unrelated to the plugin issue, I assume, but maybe those are plugins, themselves? The other problem is that old files were present after the upgrade and caused some problems, as well. Brijesh said it's likely a plugin issue, which I can't argue with (and was the same conclusion as myself), but disabling/enabling one by one is just not feasible or worth it for me right now. I have talked to both Ken (who gave me some good ideas), and Brijesh (Softaculous). Sorry I haven't had time to update this thread. which could be /var/Do know that git installed moodles don't have the same consideratons/issues. but many sites have moodle code at the document root of the site. assumption is moodle code is in a /moodle directory. There is one thing I haven't seen in these discussions. Plugins would have had to be installed via git pointed to the developers git repo for the plugin. In the past there has been discussion about updating/upgrading moodle core code + all plugins. sh script to upgrade moodle code via side-loading upgraded version of moodle core code via git. The makers of MAMP (a free product), at one time, provided a. Suggested that before, but guess didn't fit commercial nature of Softac (even though it does as there are commercial plugins for moodle!) While this doesn't help Shane at present, maybe Softac should develop a true moodle plugin/addon to handle updates as well as upgrades. Softac works with fresh installs, but not upgrades. Plugin or the one shipped with Moodle Core." (programmatically) if a plugin in the old moodle folder is a custom " From what we had analyzed earlier it is not possible to determine Moving would mean user would have to manually move back those directories in order to revert back to old version should an upgrade fail. Those directories should be *copied* to new code at same locations recursively and with same ownerships/permissions. Ditto if user installed an addon report plugin, then that addon report plugin is in /report. If user installed a non-core theme, that non-core theme is in /themes/. There isn't a single 'plugins' directory for all plugins. Maybe you are mis-communicating again with this question. Plugins are saved if someone can help with the plugins folder path I ![]() ![]() "I am stuck at move the plugin files and cannot find the folder where the sorry you are trapped in infinite Kothari
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |