|
|
|
Posted
28 days
ago
Elgg 1.8.15 has been released with almost 50 bug fixes. We again had participation from a lot of developers so thank you to all of them. You can download the latest version here. Changes in Twitter Support Twitter is retiring their 1.0
... [More]
API. To support their new API, we had to make some changes to our Twitter-related plugins. Here are the key details:
Dropped support for the twitter widget (the plugin was called twitter).
Upgraded the twitter_api plugin. We also added some settings and fixed some bugs.
No longer distributing the oauth_api plugin with Elgg. The library we have been using to talk to Twitter now conflicts with it. You can still download that plugin at our github site.
Twitter is taking more control over how content from their site is displayed on other sites. This has made the twitter widget impossible to update. The twitter_api plugin should continue to work for logging in with your Twitter account and posting to Twitter.
Other Changes
Fixed the "http://" issue for profiles
Auto-registering JavaScript files with calls to elgg_get_simplecache_url(). This helps plugin authors who forgot to register the file. This was exposed when we fixed a bug in 1.8.14.
Added a helpful message for those sites that have a configuration error related to multiple URLs mapping to the same site. This was also exposed by fixing a bug in 1.8.14.
Restoring sub-pages that have been missing after their parent page was deleted (pages plugin).
Better revision support for pages (pages plugin).
Adding nofollow to auto linked URLs to discourage spammers (thanks to Hellekin Wolf for pointing that out)
Added browser caching for languages JS files
Fixed an out of memory error for long running jobs related to the query cache
Developers
Cash Costello
Ismayil Khayredinov
Jeff Tilson
Juho Jaakkola
Matt Beckett
Paweł Sroka
Sem
Steve Clay
Tom Voorneveld
If you would like to contribute to an Elgg release, fork our repository on Github. [Less]
|
|
Posted
about 1 month
ago
It's about time for another Elgg event, and I'm please to introduce Jeroen Dalsem of ColdTrick IT Solutions with an announcement about the next ElggCamp: ElggCamp Amsterdam! After a great ElggCamp San Francisco it is now time for
... [More]
an ElggCamp in Amsterdam, The Netherlands. Organized by ColdTrick IT Solutions, ElggCamp Amsterdam will take place on June 14th, 2013 and will bring a mix of people together in the Planetarium. Expect professional developers, designers, communication specialists but also end users and people who are new to Elgg. This event will bring all these people together to share their experiences with Elgg. The day will be filled with talks about Elgg divided into a general / end user track and a developer track, but there will also be a lot of time to meet new people. Register soon because tickets are limited.
Check out the site elggcampams.com/english for more information. We hope to see you there!
[Less]
|
|
Posted
2 months
ago
Elgg 1.8.14 and Elgg 1.7.19 have been released to address a security issue in the profile tool. Thanks to Fabien Duchene for discovering and reporting this vulnerability to us. Keep your Elgg site secure by upgrading today. The
... [More]
1.8.14 release also includes significant bug fixes to localization in JavaScript, saving blog drafts, and displaying system errors due to token timeouts. In all there were 40 bug fixes and enhancements. Thank you to all the developers who contributed:
Aday Talavera
Brett Profitt
Cash Costello
Ed Lyons
German Bortoli
Hellekin Wolf
iionly
Jerome Bakker
Luciano Lima
Matt Beckett
Paweł Sroka
Sem
Steve Clay
If you would like to contribute to an Elgg release, fork our repository at Github. [Less]
|
|
Posted
3 months
ago
As of Elgg 1.9, we are encouraging all developers to adopt the AMD (Asynchronous Module Definition) standard for writing Javascript code in Elgg. For some time now, we have been working hard to make Elgg’s Javascript more maintainable
... [More]
and useful. We made some strides in 1.8 with the introduction of the “elgg” javascript object and library, but have quickly realized that based on the number of features we’d like to see added to the platform, the approach we were taking was not scalable. The size of JS on the web is growing quickly, and JS in Elgg is growing too. We want Elgg to be able to offer a solution that makes JS development as productive and maintainable as possible for everyone going forward.
What does this mean for me?
First thing’s first: Your current javascript modules will continue to work with Elgg. We do not anticipate any backwards compatibility issues with this new direction and will fix any issues that do come up. We think developing in the AMD format will be great, but we understand that you don’t always have the cycles to convert to The New Way immediately, so we want to give everyone flexibility to switch to the new standard when it’s most convenient for them. For developers ready to make the switch to AMD, read on.
Defining and loading a module in Elgg 1.9 currently takes three steps:
Define your module in the appropriate view (js/my/module.js)*
Register your view as cacheable (elgg_register_simplecache_view)**
Use elgg_require_js to asynchronously execute your module in the current page.
Read on for details.
1. Define your module in the appropriate view (“js/my/module.js”)
Place the code for “my/module” at “views/default/js/my/module.js.php”. (Yes, “.js.php”)
A basic module will look like this:
define(function(require) {
var elgg = require("elgg");
var $ = require("jquery");
return function() { /** Some logic in here */ };
});
Now, someone can use require("my/module") in their code to get access to that function "exported" by your module.
Some things to note:
elgg.provide and elgg.require are obsoleted, replaced by define() and require() respectively.
There is no need to put the name of the module in your code. It is named implicitly based on where you put it in the views system.
Return the value of the module instead of adding to a global variable.
2. Register your view as cacheable via simplecache**
In your plugin’s init function, just add:
elgg_register_simplecache_view(‘js/my/module.js’);
3. Use elgg_require_js to load the module on the current page
Calling elgg_require_js("my/module") tells Elgg to execute your module code on the current page. This is basically the asynchronous version of elgg_load_js. Note that elgg_load_js will not work with AMD modules!
Why AMD?
The reasons to choose AMD are plenteous and well-documented. Let’s highlight just a few of the most relevant reasons as they relate to Elgg specifically.
1. Simplified dependency management
No more “priority” or “location” arguments for your scripts. You don’t even need to call elgg_register_js for new AMD modules. They load asynchronously and execute as soon as their dependencies are available. Also, you don’t need to worry about explicitly loading your module’s dependencies using elgg_load_js. The AMD loader (RequireJS in this case) takes care of all that hassle for you. It’s also possible have text dependencies with the RequireJS text plugin, so client-side templating should be a breeze.
2. AMD works in all browsers. Today.
Elgg developers are already writing lots of Javascript. We know you want to write more. We cannot accept waiting 5-10 years for a native JS modules solution to be available in all browsers before we can organize our javascript in a maintainable way.
3. You do not need a build step to develop in AMD.
We like the edit-refresh cycle of web development. We wanted to make sure everyone developing on Elgg could continue experiencing that joy. Synchronous module formats like Closure or CommonJS just weren’t an option for us. But even though AMD doesn’t require a build step, it is still very build-friendly. Because of the define() wrapper, It’s possible to concatenate multiple modules into a single file and ship them all at once in a production environment.***
Conclusion
AMD is a battle-tested and well thought out module loading system for the web today. We’re very thankful for the work that has gone into it, and are excited to offer it as the standard solution for Javascript development in Elgg starting with Elgg 1.9.
We’d love it if some of you would install Elgg 1.9 from the master branch on GitHub and let us know what it’s like developing and managing AMD modules. We look forward to your feedback and questions!
* Despite the view file having a .php ending, you should not use PHP code in your modules. To get your syntax highlighter to highlight it as js, you can add “// ” as the first line of your file. Support for plain .js files is coming at some point in the future.
** We are looking into auto-registering js modules as cacheable so that you can skip this step entirely.
*** This is not currently supported by Elgg core, but we’ll be looking into it, since reducing round-trips is critical for a good first-view experience, especially on mobile devices. [Less]
|
|
Posted
4 months
ago
Elgg 1.8.13 and Elgg 1.7.17 have been released to address a security issue in the Twitter widget. The issue is present in all versions of Elgg that have included the Twitter widget plugin. Thanks to Moritz Naumann of Naumann IT Security Consulting
... [More]
for discovering and reporting this vulnerability to us.
Keep your Elgg site secure by disabling the Twitter plugin or upgrading today.
Five developers contributed to this release:
Cash Costello
Juho Jaakkola
Kevin Jardine
Krzysztof Różalski
Steve Clay
If you would like to contribute to an Elgg release, fork our repository at Github. [Less]
|
|
Posted
4 months
ago
Today we're announcing the release of the Elgg Showcase, a new section of the community dedicated to showing off the best sites powered by Elgg. For the longest time the place to share the Elgg sites you're working on has been in the Sites
... [More]
Powered by Elgg doc on docs.elgg.org. This was straightforward, but we felt it was not as compelling an experience as it could be, so we've written a plugin for the community site dedicated to showing off sites powered by Elgg.
Right now the page is extremely simple: just a static list of sites that I chose based on the existing list on the wiki linked above. However, it also features screenshots of the homepages of those sites, so you can get an at-a-glance feel for what that site has to offer. We think this important visual aspect will make the showcase that much more compelling than the previous solution.
If there's enough interest, we can put some more effort into letting you upload your own screenshots through the community site. Eventually we envision a ranking system so that the best sites can rise to the top, and profile integration so that people can see sites you or your team have worked on specifically. But all that depends on the interest level, so please let us know what you think!
If you'd like your site to be added to the showcase, please let us know by sending an email to info@elgg.org with your site's URL. [Less]
|
|
Posted
4 months
ago
The Elgg team cares deeply about making sure Elgg is as fast as it can possibly be. That’s why we’ve been submitting lots of performance-enhancing patches for 1.8, and there’s even more to come in 1.9! However, we know we’re
... [More]
not the only ones with ideas for improvement. Lately it feels like the community has had a lot to share in regard to making Elgg run faster and serve more users, and that is exciting!
Since people regularly ask questions about performance, and since the community has had so much great info to share in the past, we figured it would be appropriate to provide a dedicated place to discuss performance tips, get performance help, and do some overall brainstorming about ways we could help make Elgg faster.
So join the Elgg Performance and Scalability Group today and start sharing your ideas! Let’s make Elgg faster together. [Less]
|
|
Posted
5 months
ago
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
... [More]
tickets:
Brett Profitt
Cash Costello
Jerome Bakker
Matt Beckett
Paweł Sroka
Sem
Srokap
Steve Clay
Bugfixes include:
Added an AJAX workaround for the rewrite test.
Code cleanup to prevent some notices and warnings.
Removed "original_order" in menu item anchor tags.
Site menu's selected item correctly persists through content pages.
Static caches rewritten and improved to prevent stale data being returned.
Installation: Invalid characters in admin username are handled correctly.
Messages: Fixed inbox link in email notifications.
The Wire: Fixed objects not displaying correctly when upgrading from 1.7.
General enhancements include:
Performance improvements and improved caching in entity loading.
Added upgrade locking to prevent concurrent upgrade attempts.
Replaced xml_to_object() and autop() with GPL / MIT-compatible code.
Error messages (register_error()) only fade after being clicked.
Groups: Added a sidebar entry to display membership status and a link to group notification settings.
Groups: Added pending membership and invitation requests to the sidebar.
Groups: Better redirection for invisible and closed groups.
Search: User profile fields are searched.
Pages: Subpages can be reassigned to new parent pages.
Twitter: Login with twitter supports persistent login and correctly forwards after login.
Of special interest to users who are looking to use Elgg under the MIT license, we have replaced all code that prevented the dual license and will release an MIT version of Elgg 1.8.12 soon. In the future, this will be a single download. [Less]
|
|
Posted
6 months
ago
Elgg 1.8.11 has been released in order to fix a bug that prevented groups from being created. Please upgrade immediately if your site relies on group functionality.
Otherwise this release is identical to Elgg 1.8.10.
|
|
Posted
6 months
ago
Elgg 1.8.10 has been released with important security enhancements. Be sure to upgrade immediately to protect your sites. The primary security enhancement in 1.8.10 addresses a problem introduced in 1.8.9 that exposes user profile fields and
... [More]
other information stored in certain types of metadata. Versions below 1.8.9 are not affected by the security vulnerability.
Additional changes in 1.8.10 include:
UX: Added a list of Administrators in the admin area
UX: Limiting message board activity stream entries to excerpts
Performance: Prefetching river entries
Performance: Plugin entities are cached
Removed superfluous commas in JS files to fix IE compatibility.
API: Fixed Twitter API.
Performance: Outputting valid ETags and expires headers.
The contributing developers for the 1.8.10 release were:
Krzysztof Różalski
Lars Hærvig
Paweł Sroka
RiverVanRain
Sem
Steve Clay [Less]
|
Copyright
©
2013
Black Duck Software, Inc.
and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a
Creative Commons Attribution 3.0 Unported License
. Ohloh
®
and the Ohloh logo are trademarks of
Black Duck Software, Inc.
in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.