i just noticed that there is no mention in the documentation of any tips for upgrading from 1.11.x to 1.12.x. does that mean that there are no specific changes needed between these minor revision numbers?
as an aside, i couldn't get 1.12.x to upgrade my 1.11.x install on nginx here. i ended up stepping through the upgrade file and putting in debug statements.. then out of nowhere it just worked. i have no idea why it failed before the debug statements were put in. i suspect this may be an issue that is limited to my pc here in some way.. but don't know for sure.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Evan Winslow@ewinslow
Evan Winslow - 0 likes
- ura soul@tunist
ura soul - 0 likes
- Evan Winslow@ewinslow
Evan Winslow - 0 likes
- ura soul@tunist
ura soul - 0 likes
- Evan Winslow@ewinslow
Evan Winslow - 0 likes
- inca@inca
inca - 0 likes
You must log in to post replies.That's correct. That's what semver means after all!
i'm not clear on the reference to semver here. the upgrade from 1.8 to 1.9 and other recent upgrades from 1.9 to 1.10/1.11 all had code change requirements and were documented as such. so thinking this upgrade may have similar requirements is not out of step with the semver idea, is it?
1.8 and 1.9 were not semver releases. 1.9 to 1.10/1.11 should have been smoother if they did require changes, though I don't recall any ATM.
oh ok, i didn't realise it started at 1.10. thanks
Yea, kinda confusing. Hopefully at 2.0 we'll finally be rid of that confusion...
Hello.
What is semver?
From 1.11 to 1.12: replace i the existing core files completely or can i overwrite over existing files with 1.12 files?
thank you
[Moderator: this comment was off-topic. It was moved to its own topic.]