Correct, this is one of the new features of the File API for Moodle 2.0.
We now have far greater correlation between texts and the images they contain, to make them easier to move around.
However, even in 1.9 for this case in question ... the backup/restore in 1.9.x SHOULD be rewriting those URLs ... if it isn't then that's a regression and should be reported in the tracker.
Martin Dougiamas
Příspěvky uživatele Martin Dougiamas
Moodle in English -> Moodle community sites -> Useful ratings problem on these forums? -> Re: AJAX forum rating
autor Martin Dougiamas -
In case you hadn't seen it: http://moodle.org/useful/
Moodle in English -> General help -> Should I use slash arguments or not?? -> Re: Should I use slash arguments or not??
autor Martin Dougiamas -
You can safely experiement without breaking things permanently.
I would leave it on, though, especially if you use SCORM.
I would leave it on, though, especially if you use SCORM.
Moodle in English -> Security and privacy -> Prevent profile spam on your Moodle site
autor Martin Dougiamas -
One of the most common security issues that we see in Moodle sites is profile spam.
Profile spam is primarily a problem on sites with the combination of these two settings:
The problems with these settings is that spammers can create a page on the Moodle site which they can fill with links and pictures of porn and other nasty stuff. This in turn comes up in Google searches for those things, and is used to boost ratings to porn sites or hacking sites designed to take over your personal computer. Note that this content is designed for people using search engines, and is usually not available from within the Moodle site itself (since spammers don't join any courses) so users and admins are usually not even aware their site is having this problem.
Please pass the word to all Moodle admins that you know to check these Moodle site settings and make sure their sites are not vulnerable to profile spam. Email authentication should be disabled if not needed, and if it can't then forceloginforprofiles should definitely be enabled.
Please also use our spam-cleaning tool to scan your site to find affected profiles and delete them. This page in the docs has more details: Reducing_spam_in_Moodle or ask for help here.
Profile spam is primarily a problem on sites with the combination of these two settings:
- email authentication is enabled, allowing people to self-create an account on the site
- the admin setting forceloginforprofiles is disabled, allowing anyone to see and link to user profiles
The problems with these settings is that spammers can create a page on the Moodle site which they can fill with links and pictures of porn and other nasty stuff. This in turn comes up in Google searches for those things, and is used to boost ratings to porn sites or hacking sites designed to take over your personal computer. Note that this content is designed for people using search engines, and is usually not available from within the Moodle site itself (since spammers don't join any courses) so users and admins are usually not even aware their site is having this problem.
Please pass the word to all Moodle admins that you know to check these Moodle site settings and make sure their sites are not vulnerable to profile spam. Email authentication should be disabled if not needed, and if it can't then forceloginforprofiles should definitely be enabled.
Please also use our spam-cleaning tool to scan your site to find affected profiles and delete them. This page in the docs has more details: Reducing_spam_in_Moodle or ask for help here.
Moodle in English -> Testing and QA -> Are old Moodle code-bases archived? -> Re: Are old Moodle code-bases archived?
autor Martin Dougiamas -
Some of those are not releases yet 
For example, 1.7.7 and 1.8.8 were only announced yesterday.
For example, 1.7 is a branch, and the .x after that is a point release in that branch. Branches run in parallel. We do not release number-sequentially through 1.7.7 -> 1.7.8 -> 1.7.9 -> 1.8.0 -> 1.8.1 . However the number sequence does apply when considering an upgrade (you can only upgrade to higher-numbered versions).
This diagram explains the branching:
This history of Moodle releases will be helpful:
http://docs.moodle.org/en/Moodle_version_history
For a fairly authoritative list of tags, look at the "Sticky tag" menu on this log for the main index.php file:
http://cvs.moodle.org/moodle/index.php?view=log
For example, 1.7 is a branch, and the .x after that is a point release in that branch. Branches run in parallel. We do not release number-sequentially through 1.7.7 -> 1.7.8 -> 1.7.9 -> 1.8.0 -> 1.8.1 . However the number sequence does apply when considering an upgrade (you can only upgrade to higher-numbered versions).
This diagram explains the branching:
This history of Moodle releases will be helpful:
http://docs.moodle.org/en/Moodle_version_history
For a fairly authoritative list of tags, look at the "Sticky tag" menu on this log for the main index.php file:
http://cvs.moodle.org/moodle/index.php?view=log