See the accompanying blog post about Elgg 2.0!
(Several of these bugs did not exist in 1.12. They were introduced in the preview releases)
Fixes #9110 (a6a512e3)
Fixes #8862 (67cff474)
Here we bypass the separate owner container check if the desired owner_guid is the logged in user GUID. This eliminates the check under all normal circumstances but leaves it in place in case a poorly coded plugin allows the impersonation described above.
This also denies creation if the owner/container GUIDs are set but can't be loaded. Before, create() would simply bypass the permissions check if it couldn't load the owner/container.
Fixes #4231 (5adf98fd)
You may access it at https://github.com/Elgg/categories
Fixes #7584 (ba0c12f2)
Fixes #5996 (cb6ebcc9)
Fixes #4878 (20e606b7)
Fixes #8629 (ee7f14ed)
Fixes #8438 (541a5cd1)
fixes #8582 (fd7b8e0a)
The Markdown library is available as a composer package, this requires less maintenance by Elgg developers.
fixes #8597 (df68d986)
Replace the Elgg sprites icons by FontAwesome icons, this allowes for more icons and easier styling of the icons
fixes #7239 (ea7b17d5)
The following views are not available anymore:
Also the [object, groupforumtopic] subtype has been replaced with the [object, discussion] subtype.
Nothing changes from the group owners' point of view. The discussions feature is still available as a group tool and all old discussions are intact.
Fixes: #5994 (a4e484e6)
If you'd prefer to just add it back, you can use this code in your plugin's init:
elgg_register_js('jquery-migrate', elgg_get_simplecache_url('jquery-migrate.js'), 'head'); elgg_load_js('jquery-migrate');
Also, define a jquery-migrate.js view containing the contents of the script. (8f58da98)
Certain uses of the view,$view_name and view_vars,$view_name hooks will not work. See the docs on "View aliases" for more info.
Refs #8381 Fixes #8382 (881e2128)
Removed views:
Removed functions:
Removed methods:
Also the following arguments have been dropped:
Fixes #8440 (8ae86f16)
Fixes #7763 (6be0f97c)
Fixes #5918 (e9de196d)
Fixes #5729 (c0e81a40)
Fixes #2718 (c91f1f3e)
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.
@Cim Maybe the best way to proceed when updating plugins for Elgg 2.0 that still use functions already deprecated in later 1.X version of Elgg is to do it in two steps.
First, fix the deprecation issues while still testing it on Elgg 1.12. You can use the Code Analyzer plugin (https://elgg.org/plugins/1213751) to get a quick overview of most deprecation issues (the plugin will not report 100% of deprecation issues because some warnning only turn up when calling the deprecated functions directly). If you using inline JS code in your plugins it might be best to convert this code to AMD modules while still on Elgg 1.12, too, as the AMD modules will also work on Elgg 1.12 while it's a requirement for plugins for 2.0 (there's some "workaround" descriped also in the upgrade docs that wouldn'r require full conversion to AMD modules). Almost all changes you would have to make for plugins to work on Elgg 2.0 can already be done also for the plugins already for them still to work on the recent versions of Elgg 1.X.
The second step would be to get the plugin working for Elgg 2.0 - if there are any additional changes necessary anymore at all. If a plugin of yours allows adding some content type that users are supposed to be able to like there would be one additional step necessary (as entities are no longer likeable by default on Elgg 2.0). A "bonus" change (not absolutely necessary but useful in long term) could be migrating pages views to resource views but this might not be a necessary step for all plugins either. If any additional changes might be necessary depend on each plugin specifically. Only testing the plugins on Elgg 2.0 will reveal it. But by my experience (after updating all my plugins for 2.0) most of the work necessary is updating the JS code and fixing deprecation issues if they are still included in the plugin versions for Elgg 1.X.
@Cim While developing, turn on all error logging and watch the error log in a console window. e.g. tail -f /var/log/apache2/error_log
That simple advice I got from Cash Costello has served me well.
@steve
Or enable error logging, enable the Elgg developers plugin and set it to log to screen. Then below your page you get all the errors, no need to look at a different screen ;)
Screen logging doesn't catch:
The first two are pretty big blind spots.
- Previous
- 1
- 2
- Next
You must log in to post replies.