morgar
Beginning Developers
This space is for newcomers, who wish to build a new plugin or to customize an existing one to their liking
Feedback and Planning
Discussions about the past, present, and future of Elgg and this community site.
Elgg Technical Support
Get support from other Elgg users
Elgg Argentina
Grupo creado para nuclear a la comunidad Elgg en Argentina
Professional Services
Get / offer professional help on Elgg; like customization, design, development, setup, hosting... Illegal trades are not allowed.
Tidypics Photo Gallery Plugin
Tidypics Photo Gallery
Spanish Community Group
Spanish support group. Grupo de apoyo de usuarios en español
morgar replied on the discussion topic Upgrading a large Elgg 1.5 community- morgar replied on the discussion topic Upgrading a large Elgg 1.5 community
- morgar replied on the discussion topic Upgrading a large Elgg 1.5 community
- morgar replied on the discussion topic Upgrading a large Elgg 1.5 community
- morgar added a new discussion topic Upgrading a large Elgg 1.5 community in the group Feedback and Planning
@Carlos:
He is right ;)
If you go back thru the Elgg Releases' Notes;
only find a simple reference to 'security fixes' --
with no details of what the security holes were that got fixed
( makes us more secure ).
These usually may have been XSS fixes - investigated and reported
by " those who research " this aspect ;)
And so... " always a good idea " is a good idea.. ;-PYes, you are bpth right, maybe I oversimplify my expression. I understand there are a lot of different risks in not keeping the scripts updated, not only in the topics I mentioned. Our implementation is highly customized, so we delayed the upgrades because it will surely require lot of rewriting, but ok, this seems to be the right moment :)
Hi Morgar,
I've also been rewriting plugins originally written for Elgg 1.5 or earlier and yes, rewriting them correctly for 1.8 is quite a bit of work.
The good side is that the database changes have not been huge - it is more the API and look and feel changes that affect the code.
To be honest, I wasn't that motivated to make major changes for Elgg 1.7. Sure, the new API functions were more convenient but that helps only when creating new code. For existing code, my attitude was: if it ain't broke, don't fix it. So I just added some security tokens and kept going.
For Elgg 1.8 there is no such simple fix. Moreover, the design changes and the new sticky form system are such an improvement that it is worth taking the time to rework my plugins from the ground up.
I keep telling myself that the effort will be worth it once I'm done digging my tunnel to the other side of the mountain.
:)