differences between 2 Joomla releases

45 views
Skip to first unread message

Soheil Novinfard

unread,
May 25, 2013, 4:20:57 AM5/25/13
to joomla-de...@googlegroups.com
hi,

In many sites there are some little hacks need to execute on Joomla! core files. So how we could distinguish the differences between 2 Joomla releases (only find affected files NOT UPDATE ALL FILES! )

Kind Regards

Nikolaos K. Dionysopoulos

unread,
May 25, 2013, 4:27:13 AM5/25/13
to joomla-de...@googlegroups.com
When you hack core a kitten dies. Joking aside, if you "need" to hack core you don't understand how Joomla! works. In 9 years of working with Mambo and Joomla! I never had to hack core. There's nothing you cannot achieve with plugins, components, modules, template modifications and the all important template overrides.

Nicholas K. Dionysopoulos

--
You received this message because you are subscribed to the Google Groups "Joomla! General Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-gene...@googlegroups.com.
To post to this group, send an email to joomla-de...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-general?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Soheil Novinfard

unread,
May 25, 2013, 4:56:11 AM5/25/13
to joomla-de...@googlegroups.com
Hi Nickolas,

Yea, there is nothing that we could not do with Joomla! core architecture. (99%, but not 100%)

But the important fact in some area is the TIME. When you have a little time (due to customer's budget or any other reasons), going on developing extensions need much more efforts. On the other hand, using ready extension from JED is not a case when you could not trust to other developer's qualifications of code. (all of extension developers are not as good as you in programming)

In the previous releases of Joomla! only updated files are provided in update package, but nowadays the pattern is reversed.

Toivo Talikka

unread,
May 25, 2013, 4:56:38 AM5/25/13
to joomla-de...@googlegroups.com
Depending on your operating system, you can use diff, WinDiff, WinMerge and similar other tools to compare files in two Joomla folders, list the files which are different and then compare that list to the list of files in the update package.

Toivo Talikka

Soheil Novinfard

unread,
May 25, 2013, 5:01:57 AM5/25/13
to joomla-de...@googlegroups.com
hi toivo,

Yes, surely we could use many programs like diffmerge and others like you mentioned, but when the case between 2 releases are not so much close to each other (like 2.5.3 and 2.5.11), because the year is changed all files show the changes! so it is very annoying work

On Saturday, May 25, 2013 12:50:57 PM UTC+4:30, Soheil Novinfard wrote:

Nikolaos K. Dionysopoulos

unread,
May 25, 2013, 5:03:52 AM5/25/13
to joomla-de...@googlegroups.com
There are patch packages from one version to the next, e.g. from 2.5.9 to 2.5.10, from 2.5.10 to 2.5.11. However there are no patch packages spanning multiple releases, e.g. 2.5.9 to 2.5.11, or 2.5.1 to 2.5.11.

Regarding time, just the very fact that we're having this conversation is proof that your solution doesn't save you time. You made a quick hack which saved you 20 minutes a few months ago. For the next 18 months you are doomed to redoing the same hack every single time a new Joomla! release is out. If you put the time usage down you'll see that the quick hack costs you 5-6x more than a proper solution.

Nicholas K. Dionysopoulos

Soheil Novinfard

unread,
May 25, 2013, 5:21:43 AM5/25/13
to joomla-de...@googlegroups.com
You're right, You convince me Nikolaos.


On Saturday, May 25, 2013 12:50:57 PM UTC+4:30, Soheil Novinfard wrote:

Nick Savov

unread,
May 30, 2013, 1:13:09 AM5/30/13
to joomla-de...@googlegroups.com
I agree with Nicholas: don't hack. However, if you do need a tool to check
for hacks, check out the Version Verification Tool on the JED:
http://extensions.joomla.org/extensions/access-a-security/site-security/update-check/12026

It's useful for situations where you inherit a site that another developer
or power-user might have modified core files and you need to check it
before upgrading. It might help for your situation too, while you
transition to non-hack mode :)

Kind regards,
Nick
Reply all
Reply to author
Forward
0 new messages