July 2008
Release Update: Joomla! 1.5.2 and 1.5.3 Improvements
Take a look at new capabilities in core
Written by Andrew Eddie
Amongst the numerous bugs that have been dealt with, there are a few feature improvements that have been made in the recent Joomla! releases 1.5.2 and 1.5.3.
Now, there's a story to this first one because I initially disapproved of its inclusion (my apologies again, JM). The Mass Mail component is pretty basic, but had the annoying property of sending the message to the groups selected in the "To" mail field. Obviously this had some major privacy issues, so the component now allows you to blind carbon copy (bcc) the recipients.
A check box for this on the mail form is set by default (so you can turn it off if you need to).
The second change I want to quickly mention is the ability to now disable the new Flash uploader.
Personally I find this new uploader brilliant but it doesn't seem to work happily on some hosts. You will find the switch to toggle it one or off in the Settings pane of the Global Configuration page.
Finally we have an interesting new feature for Articles. If you look at the Article parameters dialog, you will see several new options at the bottom of the list for Filtering.
Traditionally this has been left to the particularly WYSIWYG editor that is in use, but this is not fool proof, nor does it account for sites that do not use an editor. These new options allow you do apply restrictions on the html tags and attributes that certain user groups are allowed submit in their content.
The Filter groups box allows you to select the groups to which the additional rules will be applied. Use control-click to select more than one.
The Filter Type allows you to specify:
- a White List – this means that you control the tags and attributes that are allowed
- a Black List – this means that you allow all tags and attributes except for the ones you list
- or No HTML – this mean, well, that no HTML tags are allowed – and that's final.
The Filter Tags field allows you to enter the tags that you want to either white or black list.
The Filter Attributes field allows you to enter the attributes of the HTML tags that you want to either white or black list.
This has many uses from being able to avoid the deliberate insertion of malicious javascript from someone who is in the Author Group, or could be used more widely to combat code-bloat caused by that terrible practice of cutting-and-pasting from Word. To give you an example, a simple white list might have the following settings:
- Filter groups: Select Author and Editor
- Filter type: Select White list
- Filter tags: p, br, a, ul, ol, li
- Filter attributes: href, target
This combination will only allow users in the Author or Editor group to save content leaving the most basic of tags, and only allowing the href and target attributes (used in the anchor tag).
If you are more trusting of your users, you may want to choose a Black List and only filter out such things as applet or script tags.
Hopefully you will find these new feature fixes useful from time to time.
Reprinted with Andrew Eddie's permission from the Art of Joomla!, Issue 3, Article What's new in Joomla! 1.5.x?
2008-10-13 23:59:24
2008-10-14 02:42:53
2008-10-14 03:24:30
Luckily all the commercial components that I need now also support Joomla 1.5.
Thanks for all your and the rest of the Joomla team's hard work. Can't wait to see a 1.6 release.
2008-10-14 06:13:30
2008-10-14 09:18:38
2008-10-14 12:24:39
2008-10-14 17:36:29
continue for 1.6
2008-10-14 18:15:56
Very few people, if any, still bother with bug fixing or security checking joomla 1.0, because all eyes are on 1.5 and 1.6. If no date was set, j1.0 would die silently without anyone knowing. This date is a reassurance that j1.0 is indeed still alive and being supported, and users now know exactly what to expect and how much time they have left.
Mathias
2008-10-15 06:45:04
2008-10-15 17:22:34
We discussed the end-of-life date for several months, and our choice balanced between a sudden end or a acceptable period of time to offer users to get ready to migrate. I am happy we have chosen the second option, notify our users up front. The date was a simple math; 1.5 * 1.5 makes July 22nd
2008-10-15 18:41:18
Roll on 1.6.
Nick
2008-10-16 18:29:41
2008-10-16 20:19:37
I recently began migration for all of our sites and - despite the angst - I am glad we did so.
I know everyone looks forward to v1.6, but I really really anticipate what will unfold with Joomla! 2.0
2008-10-17 02:39:03
2008-10-17 05:02:41
Until the dozens of "components" we rely on step up to become "extensions," we won't have much of a site. Might be a while since development of our more useful ones seems dead.
I'm sure 1.5 will be an improvement, but right now it just looks like more work.
2008-10-17 05:03:15
There are still too many important extensions which are not native for 1.5, not speaking of the poor or inexistant implementation of the new language system on many "native" extensions.
2008-10-17 05:04:40
There are still too many important extensions which are not native for 1.5, not speaking of the poor or inexistant implementation of the new language system on many "native" extensions.
2008-10-17 10:19:30
Time for developers to move on, specially on the language matters which are, alas, very much forgotten by most.
2008-10-17 10:31:10
2008-10-17 18:03:57
2008-10-23 16:28:25
2008-10-28 16:37:59
-- comment is too long it says, so part two is below! --
2008-10-28 16:39:11
I'm intrigued by the concept of 1.5, especially to see how much work it would be to transfer the above mentioned site over to use Joomla 1.5, and still get all the templates working on the different parts of the site.
I have one little worry though: if I would manage that transition, would I have to go through a similar ordeal when you bring out 1.6? Or is 1.6 a minor difference from 1.5, like 1.0.15 is a minor upgrade from 1.0.14? Perhaps it would be easier to wait for 1.6 before making any transition at all, or would it be even smarter to wait for 2.0?
2008-10-29 21:04:06
2008-11-01 22:36:29
It seems like everyone using 1.5 needs to worry about security. At least that is how it seems with all of the "My site got hacked" posts.
2008-11-04 09:34:02
2008-11-06 08:52:34
2008-11-09 11:11:30
2008-12-25 02:27:33
In this light, there is absolutely no reason to stop supporting joomla! 1.0.x. until 1.6 comes out. Then, those who enjoy to get hacked all so often can upgrade to 1.6, and those who actually use their joomla for production websites, can stick with 1.5, which at that point has become stable, just because the devellopers have moved on.
Has anyone noticed that joomla. 1.0.x has shown that a CMS can go for almost a year without an upgrade (and a new version can be developped in the meantime)? Hey, what do you know, a CMS thats just there, and it just works, no dramas and all known issues. Such CMS maybe a bore to a developer, but to a USER this sounds GREAT. Infact, every CMS should adopt this policy. WHY would this be taken away before 1.5 is anything near like 1.0 as far as stability goes ??
To me, this feels just like like microsoft ramming vista onto my machine and into my live. I'm allergic to this attitude. I'll make it a matter of principle to KEEP all my sites on 1.0.x for as long as i can, support anyone who does the same, and rather migrate to Mambo or MIA, even frikkin Wordpress, before migrating to joomla! 1.5.
My farewell goes to developers who dump their most stable version without necessity.
2009-01-18 22:01:03
There's no reason to stop the support until the next 1.6 version is released. Every user of joomla 1.0 know that there will be no addition to their version, but they like its stability after all the updates thez had to do - remember, ~1 every month from joomla 1.0 to 1.0.15 ...
It would be so much better to do what was announced some monthes ago, after the 1.0.15 version was released : keep a minimal support, and update it only if a critical security hole is discovered.
2009-02-02 22:25:22
So having what appears to be the most stable version of Joomla abandoned makes very little sense to me.
Granted, I'm loving 1.5.9 -- it has so many great features!
Migrating 1.0.x sites to 1.5.9 looks like it is a significant expense, almost as much as to develop some sites, initially. I just priced one out at $3440 that has a lot of JUGA restrictions.
Having said all of that, it's obvious that there will be a market opening up to some enterprising developers in supporting 1.0.x security fixes.
Go for it gals/guys!
Railer
2009-02-02 22:28:55
A REALLY BIG THANK YOU to all of the 1.0.x developers who contributed so much to the growth of Joomla!
Moore's Law keeps on rolling...
Railer
2009-03-23 10:03:51
2009-03-24 10:01:49
Andalublue
2009-03-27 11:57:35
Shoaib
2009-04-03 10:24:23
2009-05-06 17:27:52
It was not easy to migrate it without legacy plugin (my goal was to migrate entire site and not to use that plugin) but in the and - I made it.
And now a whole new dimension is opened for me with some great extensions to be used. Looking forward to see Joomla 1.6 one day.
Massive respect to Joomla development crew!
2009-06-14 03:09:21
2009-06-15 19:56:27
We have some extra components installed. I haven't worked with Joomla before. Is the migration easy to complete?
2009-07-07 20:00:55
I also had all those questions about migrating from 1.0 to 1.5, specially when you do a lot of hacking in the core. And, above all, I couldn't find a few extensions that I had on 1.0 to work in 1.5.
This is what I made: Searched for similar extensions and installed them. Then, wrote some code to get the data from 1.0 database and inject it to 1.5 DB. This takes time because you must put into paper the old sections and categories Ids and assign them into the new DB. The same goes to the items.
In the end, all went well and a task that I was supposed to do by hand, and for shore would take more than a week was accomplished in one day.
The bottom line is this: Don't be sad because you can't find the extension you want. Just go for the one you need and migrate it as I did.
Now i'll wait for 1.6 release.
2009-07-16 17:39:06
Cheers Creator
2009-07-29 23:10:08
2009-08-13 17:51:49
2009-08-16 21:06:46
2009-08-31 03:34:52
thanks, just what I needed. A lot of old clients asked to be upgraded from 1.0.x either to 1.0.15 or 1.5, so your suggestion came in handy. Thanks!