> So my moodle was on http://192.168.10.20/moodle (all images was displayed),
So far so good.
> now i changed it to http://192.168.10.20
How?
> (some images missing)
So the step was not complete?
> i set local DNS to moodle.mycompany.com
You try a second step without completing the first step. Get the first step done and also get an understanding of the mechanism. Then you can repeat similar steps any number of times.
Re: Missing images after URL change, please help :-(
Re: Missing images after URL change, please help :-(
Re: Missing images after URL change, please help :-(
Search whole database for
http://192.168.10.20/moodle
Replace with this string
http://192.168.10.20
and than click to "Yes, do it" Button?
Re: Missing images after URL change, please help :-(
Yes, that was what I meant.
> Only thing i need is to go to Search and replace tool and do this:
*Only* thing? I don't think. The web server now needs to look for files in you moodle directory when a request to http://192.168.10.20/. The setting is in the web server configuration, in Apache it is called the DocumentRoot.
Then change $CFG->wwwroot to 'http://192.168.10.20'.
Then:
> Search whole database for
> http://192.168.10.20/moodle
> > Replace with this string
> http://192.168.10.20
Re: Problems with cron tasks after update
First make sure that you have that file and it's not corrupt in some way.
Failing that, I can only think that the class loader isn't working properly as this is going on reasonably early on in the 'bootstrapping' of Moodle.
Re: Problems with cron tasks after update
Is it definitely 4.2.5 (released in December 2023) and not the latest, 4.2.6 (released in February 2024)? What's the exact build number? I ask because your error has:
#0 E:\moodle\lib\moodlelib.php(7300): core_string_manager_standard->__construct('D:\\moodledata/l...', 'D:\\moodledata/l...', Array, Array)
But line 7300 of lib\moodlelib.php
of Moodle 4.2.5 is a comment, the call to core_string_manager_standard constructor's is on line 7286:
7286 $singleton = new core_string_manager_standard($CFG->langotherroot, $CFG->langlocalroot, $translist, $transaliases);
⋮
7296 /**
⋮
7300 * for $module. Uses the same format files as STphp.
So possibly you don't have all the correct source code files for your Moodle version, or maybe your source code files have been modified.
Also please tell us the PHP version, both for the web server, and the one used to run admin/cli/cron.php
(php --version
).
Re: Problems with cron tasks after update
I'm going to review what they say about the file you mention.
Greetings
Re: Problems with cron tasks after update
Regarding what you mention about the version. When the update was carried out it was the latest version 4.2.5+ since we carried out this process in January. However, we did not notice the error until new users were recently registered in the external database. I leave you below what appears at the end of the version.php file
$version = 2023042405.03; // 20230424 = branching date YYYYMMDD - do not modify!
// RR = release increments - 00 in DEV branches.
// .XX = incremental changes.
$release = '4.2.5+ (Build: 20240119)'; // Human-friendly version name
$branch = '402'; // This version's branch.
$maturity = MATURITY_STABLE; // This version's maturity level.
Regarding the php version, we are currently working with PHP 8.2.14
Greetings
Re: Missing images after URL change, please help :-(
Re: Missing images after URL change, please help :-( [SOLVED]
Glad that you SOLVED the issue.
So the question was you've installed Moodle inadvertently at http(s)://something/moodle. The question was how to remove that trailing /moodle.
That involves three steps:
a) Change the web server configuration to point the DocumentRoot to the Moodle code directory
b) Change $CFG->wwwroot to that 'http(s)://something'
c) Visit http(s)://something/admin/tool/replace/ and replace "http(s)://something/moodle" with "http(s)://something".
Re: After upgrading to Moodle 4.3.2+ (Build: 20240119) I get the undefined error
The issue was solved.
Re: Problems with cron tasks after update
$release = '4.2.5+ (Build: 20240119)'; // Human-friendly version name
In that case please ignore my comments about the source code being incorrect or modified. The line numbers in your error are correct for the above version.
Odp: Re: Odp: Re: Plugins to be delete during upgrade
Plugins requiring attention
Plugin name / Directory Current version New version Requires Source / Status
Blocks
quiz_results 2021051700 Standard To be deleted
Question import/export formats
examview 2021051700 Standard To be deleted
webct 2021051700 Standard To be deleted
Text filters
censor 2021051700 Standard To be deleted
Admin tools
health 2022032400 Standard To be deleted
Media players
swf 2021051700 Standard To be deleted
Repositories
boxnet 2022032400 Standard To be deleted
picasa 2021051700 Standard To be deleted
skydrive 2021051700 Standard To be deleted
Portfolios
boxnet 2022032400 Standard To be deleted
picasa 2021051700 Standard To be deleted
Re: Odp: Re: Odp: Re: Plugins to be delete during upgrade
Are the subfolders for the plugins in this list present in your site's source code folder?:
blocks/quiz_results
question/format/examview
filter/censor
, and so on.
These plugins are from Moodle 3.11 and were removed in Moodle 4.0 so these subfolders should not be present in the source code folder for Moodle 4.3.
Cannot get past not in the Plugins directory: theme_boost for 4.2
I am at my wits end! I am upgrading my test server to Moodle 4.2.6 because our IT department upgraded the apache OS server and PHP to version 8.2. I fixed all the issues and this is the last item to resolve. I have read just about all the issues people have tried which have not worked for me. The default theme for my site is adaptable. I downloaded the 4.2 version for every theme and copied the boost folder over from the previous version. There is no new version for the boost theme. I can't delete the boost folder or uninstall it because I either get errors after deleting the folder or when I do access the site every time I click to try and uninstall it goes back to the upgrade window to continue.
Please help me I don't know what else to do besides have the IT group revert back the apache OS and PHP back to version 7 so that I can restore the site and then uninstall those themes before doing the upgrade again.
Re: Cannot get past not in the Plugins directory: theme_boost for 4.2
Re: Cannot get past not in the Plugins directory: theme_boost for 4.2
Glad you have it sorted, but sounds like your IT department needs to coordinate with you about upgrading things for your moodle sites. :|
Noted your screen shot showed 'classic' theme to be upgraded .. there are only 2 themes that come with core ... boost and classic. Best to leave those directories. Matter of fact, many force the theme to boost via config.php file just prior to upgrades to avoid issues with 3rd party themes not being compatible with core upgrade.
And this is your test site ... so what about your production site? Did this experience give you the plan for your production site upgrade?
Kinda curious as to why either boost or classic was missing since those are core themes.
And one more comment ... if site was installed/maintained by git repo (command line only) this issue might have been avoided - or resolved more quickly and with less confusion.
'SoS', Ken
Re: Cannot get past not in the Plugins directory: theme_boost for 4.2
It was a planned upgrade because there were some security vulnerabilities with all of the sites we have that needed to be addressed. They were very helpful with setting up PHP and folder structures for moodle.
I think what may have happened is I overwrote the boost folder with a previous version not realizing that the download already included it so when I downloaded 4.3.3 I checked and classic/boost were already there so I left them alone. It was most likely my mistake!
What I learned is to leave those folders alone! LOL
I don't believe our sites were installed/maintained by git repo. I use WinSCP to connect to the server's file directory and use the Putty command window to perform certain tasks when needed.
I appreciate your feedback!
Odp: Re: Odp: Re: Odp: Re: Plugins to be delete during upgrade
Re: Cannot get past not in the Plugins directory: theme_boost for 4.2
Feedback ...
Yep, you've learned what not to do. Good that it was with a test instance.
The 'standard' way of updating or upgrading a moodle has too many moving parts.
Git, on the other hand, leaves code in place and one literally 'pulls' in either new files/folders needed, removes files/folders no longer needed, and updates files (just parts of files) that need changing.
Takes the human error factor out of the loop.
And since you use Putty - which is ssh/command line - you can use git to update the core code as well as upgrade.
Plus, if you look in code/admin/cli/ you'll see some CLI only scripts that actually performs the the upgrade process.
https://docs.moodle.org/403/en/Git_for_Administrators
https://docs.moodle.org/403/en/Administration_via_command_line
Advice ... in the link above concentrate on core ... using git for moodle add ons is doable but have found best to leave moodle sort those out.
So now (on your test server) the 'trick' is to get you code directory under git versioning.
That can be done by a 'sideload' or an 'upload' (a mis-nomer really). View my profile to get a link to a thing I've put together and called 'gitify' - do read the readme. And do this first on your test instance.
'SoS', Ken