Elgg 2.1.0 released
Note! Due to a major bug, this release can only be used for upgrades. 2.1.1 has a working installer.
Hey, look! Elgg 2.1.0 is out. The highlights are some performance improvements, some accessibility improvements in forms, and a new Ajax API for developers.
Contributors
- Steve Clay (40)
- Ismayil Khayredinov (25)
- Juho Jaakkola (10)
- Jeroen Dalsem (2)
- Hereward Mills (1)
- Wade Benson (1)
- Wouter van Os (1)
Features
- actions: adds a generic delete action (4c35fe26)
- ajax:
- cron: allows for a more systematic way of calling cron using one url (3c947fc1)
- discussions: makes "last reply" text into a link (9c1d543a)
- engine:
- entities: give access to original values of modified attributes (56ddabbc, closes #9187)
- files: adds a service for serving files from filestore (1d6b23c7)
- forms:
- groups: profile buttons can now be filtered with a hook (52e82943)
- js:
- menus: delete menu item now checks if delete action exists (84cbb151)
- metastrings: add function to get map of strings to metastring IDs (8d28a8dd)
- notifications: it's now easier to alter translations for notifications (4677d482)
- profiler: allow capture/display of crude profiling data (6ce01fad, closes #9293)
- routing: allow more reliable URL path rewriting (853fc0ef, closes #9388)
- rss: adds functions for adding/removing the RSS link (ae765e19)
- search: search hooks now preserve custom joins and wheres (65041619)
- views: add attributes to input select options (63b04d6a)
Performance
- boot: we order plugins in PHP because MySQL order by CAST is slow (c4b10c1c, closes #8183)
- files: ElggFile no longer queries metadata for filestore data (d9243002, closes #9138)
- http: serve-file URLs can respond without booting core (4f587df0)
Documentation
- js: modernizes the JS docs to emphasize AMD usage (d66cae64)
Bug Fixes
- actions: referrer path is now parsed correctly (6b1bfe26)
- ajax: iframe-based submissions can again be recognized as XHR requests (c25962a0, closes #8735)
- files: files with custom filestore can now be served via file service (1a2b0ca7)
- forms:
- i18n: admin-created accounts now get site language instead of admin's language (561bad37, closes #9454)
- js:
- menus: delete menu item is only registered if canDelete is fullfilled (e13ba511)
- permissions: All permissions functions handle user fetches consistently (b875fd33, closes #8941, #8038, #8945)
- river: opening comment form auto-focuses input (5b68badc)
- search:
Deprecations
- assets: Deprecates URLs like /js/ and /css/ in favor of simplecache (91daac90)
- config: deprecates config value "siteemail" (cdd4bb5f)
- entity: removes the tables_split and tables_loaded properties (4d469183)
- filestore: deprecates giving files custom filestores (0050b1db, closes #9352)
- rss: deprecates using global $autofeed (ae765e1)
Steve Clay
Old Elgg team guy
Latest comments
Light Event on Elgg 1.12.4 released ():
Thank for sharing. Light Event - Tổ chức sự kiện, màn hình LED,...- josephelina on Elgg 2.2.0 RC1 is released ():
group icons are now handled by the new icon service introduced a...
Awesome!
Download fails for me for https://www.elgg.org/download/elgg-2.1.0.zip due to certificate not valid for www.elgg.org. It works with https://elgg.org/download/elgg-2.1.0.zip.
The download URLs have now been fixed.
Very, very, nice release.
Thank you guys!
i just came to test this release by upgrading my test install of elgg 2.0.3, but after running the upgrade script, the statistics page still shows the site as being 2.0.3. did i miss something?
i am not using composer, i just downloaded the zip file and overwrote the existing files on my machine.
@ura are you sure you got the new composer.json (where the version is pulled from)?
looking in the composer.json file in the /vendors/elgg/elgg/ directory that i downloaded from the elgg community as elgg 2.1, i see that the listed version is 2.0.3, whereas it should be 2.1.
i did notice that the download from elgg.org was very slow indeed, so maybe some kind of server bug caused me to get 2.0.3 when i clicked the download link for 2.1?!
I think it's not only the version number displayed that's wrong. I also updated a test installation to "2.1.0" with the zip and it also shows 2.0.3 after running the uprade script (just checked it now and then also checked the content of the zip archive...).
The content of the zip compared to the 2.0.3 zip and to the 2.1 branch on github makes me believe that the 2.1.0 zip archive currently available at the community site is NOT version 2.1 of Elgg but basically just 2.0.3 with only updated versions of some dependencies in the vendor folder (but no changes in /vendor/elgg/elgg/ or in the mod folder at all!!!).
2.1.0.zip is wrong. Working on it.
The zip should now have been fixed.
Fast fix!
Deprecation of global $autofeed (usage of elgg_register_rss_link() instead) seems not mentioned. Are there other possible deprecations introduced in 2.1 that are waiting to get discovered? Problem is with deprecation noticed not included in engine/lib/deprecated-X.Y.php. These are really hard to find if you don't happen to come across them directly on a test installation.
Is updating learn.elgg.org for the 2.1 docs a separate process? Right now these are not online yet, i.e. you can't check for possible hints about deprecation and other changes in the docs.
@iionly This was an oversight. #9489. We'll try to get better at this, but watching error logs for notices (deprecation and general) remains a good idea.
Just downloaded 2.1.0 from elgg.org and contents look odd.
@Ismayil What's odd in your opinion? It seems to me it's no different from previous 2.X zip releases (though I'm not sure the .git folder and .gitignore has been included in each release - I would think it's not necessary for the zip releases).
As some have realized, due to #9486, 2.1.0 cannot be installed. We'll release 2.1.1 soon.
I was under the impression that zip dist includes everything in root, not in vendor, but I haven't used a zip package in ages. I don't use the starter project because I find myself spending too much time trying to locate files jumping back and forth between vendor, root and mod. My current workflow is to clone Elgg in it's entirety, setup client fork, and work with it (with some changes to gitignore, composer, et al). This makes upgrades a lot easier to manage, I can merge any branch from upstream in seconds, I dont need to figure out what files are to be removed, updated etc. I can cherry-pick certain features and don't have to remember these "hacks" because git resolves them on its own.
Yeah the jumping back and forth from vendor is an annoyance...
Hey gang, 2.1.1 is now out and fixes the installer.
Good thing I waited to see if someone encountered bugs.
[comment removed as spam]