volgens Howard Miller.
Regardless... you need to eliminate the theme as the issue. If your theme is broken then you'll need to do *something*
↧
Re: Problems after upgrading to Moodle 3.4
↧
Re: Migrated to new host & now no images showing
by Rich Debonair.
Hi Howard and Tina,
I have been following this thread because i have exactly the same problem ie images are not showing after migration to Moodle 3.5
I turned on Debugging as Howard advised and clicked on one of the images and the top of the error messages says:
===
pix_url is deprecated. Use image_url for images and pix_icon for icons.
line 267 of /lib/outputrenderers.php: call to debugging()
line 214 of /theme/eguru/renderers/course_renderer.php: call to renderer_base->pix_url()
line 63 of /theme/eguru/layout/frontpage.php: call to theme_eguru_core_course_renderer->promoted_courses()
line 1261 of /lib/outputrenderers.php: call to include()
line 1191 of /lib/outputrenderers.php: call to core_renderer->render_page_layout()
line 112 of /index.php: call to core_renderer->header()
===
When i make the changes where pix_url occurs in the code, and save, i get this error:
is currently unable to handle this request.
HTTP ERROR 500
Can you help me here?
↧
↧
Error messages when upgrading from 3.4.2 -> 3.5
by Finn Majlergaard.
Hello community.
I just upgraded from Moodle version 3.4.2 to 3.5 and followed all the steps in the upgrade procedure.
I get a number of error messages when I go to the admin area afterwards including:
parent does not exist!
- line 913 of /lib/adminlib.php: call to debugging()
- line 68 of /admin/settings/privacy.php: call to admin_category->add()
- line 7999 of /lib/adminlib.php: call to require()
- line 19 of /admin/settings.php: call to admin_get_root()
parent does not exist!
- line 913 of /lib/adminlib.php: call to debugging()
- line 79 of /admin/settings/privacy.php: call to admin_category->add()
- line 7999 of /lib/adminlib.php: call to require()
- line 19 of /admin/settings.php: call to admin_get_root()
Do you have any Idea what that can be?
Site: gugin.online
All the best
Finn
↧
Re: The page isn't redirecting properly with Fresh installation
by Mike Morales.
yeah, all cool & working perfectly on my website, Thanks
↧
Re: outgoing email not working
by Brian Schmidt.
Sorry, poor choice of words - I didn't actually remove any component from Moodle. I meant to convey that I was no longer using the server hosting Moodle's mailing capability and instead wanted to shift that function to another server's SMTP capability.
Thanks for the hint about the email test plug-in; I'll give that a shot.
↧
↧
Re: outgoing email not working
by Brian Schmidt.
10 minutes of troubleshooting and now I'm back in business. This plug-in was a lifesaver - thank you!
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
by Howard Miller.
Slightly worryingly, you are now the second person to report this.
Do you have any optional plugins (especially a theme) and especially ones that are not *definitely* compatible with 3.5?
↧
Re: outgoing email not working
by Ken Task.
Welcome!
Credit where credit is due ... thanks should really go to the maintainer of the plugin:
Maintained by 
So if you're listening Michael ... thanks!
IMHO, it ought to be made part of core as community forums have tons of EMail/SMTP, etc. errors and request for assistance to fix. EMail and EMail relay isn't an easily understandable setup.
'spirit of sharing', Ken
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
by Finn Majlergaard.
Hello Howard,
I am using the adaptable theme, latest edition, which should be compatible. I did try to switch to the default theme to see if the error messages remained. They did
↧
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
by Ken Task.
By chance did you have installed the GDPR plugins on the 3.4.2 prior to upgrading to 3.5 (has those as core in this version).
'spirit of sharing', Ken
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
by Howard Miller.
...or, even, have you still got those plugins installed (you don't need them).
Although, that should be covered by my "are all your plugins compatible" question...
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
by Finn Majlergaard.
I will check up on the plugins and revert to you
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
by Finn Majlergaard.
Switching off/on plugins didn't make a difference.
As everything seems to work ok I changed the debugging level from all to minimal, which leaves me in the belief that everything is ok - at least for now
↧
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
by Finn Majlergaard.
Thank you so much.
Have a great morning/day/evening/night depending on where you are
↧
Re: Error messages when upgrading from 3.4.2 -> 3.5
volgens Howard Miller.
It isn't... you're just hiding the error.
↧
Re: Debug info: Duplicate entry '1-1' for key 'mdl_quizsect_quifir_uix'
volgens Nadav Kavalerchik.
↧
Re: Problems after upgrading to Moodle 3.4
by Karishma Tiwari.
OK so I am looking to customise the boost theme for our use, but I am so bad with css stuff. Can someone advice, given the below files in my existing theme, which are the css and layout files, how/which ones do I put into the custom scss for boost?
Just wondering, is there any way to seamlessly
import theme settings from moodle 2.5 to moodle 3.4?
[root@Moodle2001 style]# ls -lrt
total 40
-rwxr-xr-x. 1 apache apache 5559 Jul 4 09:39 pagelayout.css
-rwxr-xr-x. 1 apache apache 146 Jul 4 09:39 editor.css
-rwxr-xr-x. 1 apache apache 62 Jul 4 09:39 settings.css
-rwxr-xr-x. 1 apache apache 2759 Jul 4 09:39 admin.css
-rwxr-xr-x. 1 apache apache 7805 Jul 4 09:39 core.css
-rwxr-xr-x. 1 apache apache 684 Jul 4 09:39 menu.css
-rwxr-xr-x. 1 apache apache 4502 Jul 4 09:39 report.css
[root@Moodle2001 style]# cd ../layout
[root@Moodle2001 layout]# ls -lrt
total 36
-rwxr-xr-x. 1 apache apache 4379 Jul 4 09:39 frontpage.php
-rwxr-xr-x. 1 apache apache 4994 Jul 4 09:39 report.php
-rwxr-xr-x. 1 apache apache 1802 Jul 4 09:39 scorm.php
-rwxr-xr-x. 1 root root 6509 Jul 5 15:50 general.php_5Jul2018
-rwxr-xr-x. 1 apache apache 6510 Jul 5 15:51 general.php
↧
↧
Re: Problems after upgrading to Moodle 3.4
by Howard Miller.
Read this - https://docs.moodle.org/dev/Themes
Then if (when?) you have specific questions please post them in the Themes forum... you will get lots of great help over there
↧
Git local changes
by Kevin von Spiczak.
Hello everyone,
so I followed the installation quick start guide and have a moodle instance running.
Now we installed some themes and extensions, so we have local changes.
How am I supposed to update to a new moodle version now? Would i stay on the branch that I set the repo up with and just git stash my local changes, git pull, git apply stash?
Kind regards
Kevin
↧
Re: Git local changes
by Howard Miller.
If you'd pulled Moodle from git and then added some non-core plugins then you wouldn't be getting that message.
This implies that you have made changes to files under the control of git, i.e., core Moodle files. It's possible that the only change was to change the file mode. If you don't care about that (and you probably don't)..
git config core.filemode false
...should 'fix' it.
Failing that, you really did change something in core Moodle files. If you are simply updating on the same branch then just commit your changes and then 'git pull'. If you have conflicts you will have to deal with them.
I've been using Git for a long time and have never found a reason to use 'git stash'
↧