Public Forums 71,145 posts

[TomC Moderator TomCJoin date: October 2014Posts: 14077Downloads:58Uploads:137 Thanks: 948 Thanked: 3155 times in 2495 posts]

#126157

For those of you who have already upgraded and/or have been using Joomla 1.5, perhaps you can provide some testimonial as to why others (like myself) should also do so.

– What Are The Benefits?
– What is Easier/Better?
– Any Cons ?

Looking forward to reading the comments to follow.

🙂

[Menalto Friend MenaltoJoin date: May 2007Posts: 4736Downloads:0Uploads:43 Thanks: 2 Thanked: 531 times in 361 posts]

#240787

Well, i have tested out 1.5 in different enviroments and its in basic the same as the 1.0.xx version.
– What Are The Benefits?
See below
– What is Easier/Better? Ummm, eh, hmmmmmm. If you have a site today that is buildt up around the 1.0.xx version whats the point to upgrade?
Lets say this, if your car is working fine do you take it to the garage for fix it? No, i thought so.
– Any Cons ?
Nothing special to mention

[brockho Friend brockhoJoin date: September 2006Posts: 6Downloads:0Uploads:0]

#242353

There is a huge difference, most of them under the surface.

The architecture is true MVC as opposed to the mish-mash of the 1.0.X series. What does this mean for you? It means that the new components and modules which you now see coming out will be more stable, more easily pluggable, easier to configure and maintain. In the core, it means more secure, more stable, richer functionality, and much simplified operation. In the presentation level (“View” in MVC), everything is MUCH more logically organized, especially things like the media and menu managers.

One example of how this improves things – in 1.0.x, we were loathe to expose the admin functions to any clients because the organization was so unfriendly and disorganized (although CQI was a godsend). We HAD to use JCE or FCKEditor just to get a WYSIWYG editor that did anything useful with documents or images. With J1.5, no need, just use TinyMCE, because the image control button is right on the edit page itself, not part of the editor array. And there’s a sweet “insert document button” available as a J1.5 plug-in, so you can very intuitively upload and insert documents directly into the editor. This was a nightmare in J1.0.X for clients, unless you had the DocMan link in JCE, but the client usability was low. So with J1.5, we’ve been able to eliminate fully 50-60% of the extensions we needed in J1.0.X, simplifying integration significantly.

Another example is the parameterization of template configs, saves a lot of time and wasted energy. Etc. etc.

Just a lot more intuitive for all functions, especially media handling, template handling, and extension handling. And as mentioned, the J1.5 extensions coming out are more stable and cleaner.

The negatives are 1) installation, which is more problematic than J1, 2) performance, except with caching turned on, that difference is eliminated, and 3) they failed to include the full position display function for templates… very strange but they’re correcting that in J1.5.2.

So the benefits outweigh the negatives about 20:1. We’re converting the most critical (functionally rich) sites all to J1.5 asap, and leaving the light-duty sites as J.1.X. For function-rich sites with Community Builder, DBQ, Acajoom, DocMan, etc., it’s a compelling upgrade. For lightweight sites, not compelling.

[Author]

Posts