Elgg 1.8.12 has been released with numerous bugfixes and improvements. Keep your Elgg site running smoothly by upgrading today!
A total of 8 developers contributed to this release. Thanks to everyone who submitted pull requests and trac tickets:
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.
...../ )
.....' /
---' (_____
......... ((__)
..... _ ((___)
....... -'((__)
--.___((_)
+1 :)
i'm seeing a fatal error.. though i was also seeing it when upgrading to 1.8.11..
after the upgrade the site functions without noticable glitches.. and the status page shows the site is at 1.8.12.
there's also a bunch of time/server related warnings on the upgrade 'in process' page before the fatal warning renders in the browser..
anyone got any pointers for me as to what this might be caused by?
->>
SecurityException Object
(
[message:protected] => Redirect could not be issued due to headers already being sent. Halting execution for security. Search http://docs.elgg.org/ for more information.
[string:Exception:private] => exception 'SecurityException' with message 'Redirect could not be issued due to headers already being sent. Halting execution for security. Search http://docs.elgg.org/ for more information.' in /mysite/engine/lib/elgglib.php:151
Stack trace:
#0 /mysite/upgrade.php(67): forward()
#1 {main}
[code:protected] => 0
[file:protected] => /mysite/engine/lib/elgglib.php
[line:protected] => 151
[trace:Exception:private] => Array
(
[0] => Array
(
[file] => /mysite/upgrade.php
[line] => 67
[function] => forward
[args] => Array
(
)
)
)
[previous:Exception:private] =>
)
@ura soul: http://docs.elgg.org/wiki/Redirect_could_not_be_issued_due_to_headers_already_being_sent
This error could be caused by any 3rd party plugin installed on your site. If you modified any files on your own and saved in "with BOM" then these files are likely candidates for your issue.
wow ok; that could take a while to locate, thanks for the pointer.
@ura soul: works for me
Nothing suspicious here as well: https://github.com/Elgg/Elgg/compare/1.8.11...1.8.12
sure ok; i imagine it is a plugin issue as i have many installed.
ah i fixed the issue. i had mis-spelled the date.time variable in php.ini.
re-ran the upgrade and all is well again. :)
Kudos
ok this update is very good