The idea of a new Joomla! podcast was raised during Joomla! Day UK 2017 by an attendee who was keen to be its creator. I really would like to see this as there have been some great ones in the past. If you want to see this too, then feedback via Github so he is encouraged to make it happen. https://github.com/joomla/joomla-marketing/issues/109. Here's a link to some of the other podcasts that either still run or have run in the past.
Our next meeting is on the 16th of August, that's 15 days away, just over two weeks. Register to attend (for free) and come down and learn more about Joomla! and surrounding topics. Last meeting had an excellent talk from Gary Barclay (Barclay.Works) regarding Google Tag Manager. We also had some great information from George Wilson (in charge of Joomla! releases) relating to Joomla! 3.6 as well as some feedback from the rest of the room.
Joomla haJoomla has been around for a little over 10 years. in that time much of the code base has benefited from extensive development, to get it to the current version 3.5. Some parts however, have seen very little change, the router is one such area of code, now that's about to be overhauled....completely!s been around for a little over 10 years. in that time much of the code base has benefited from extensive development, to get it to the current version 3.5. Some parts however, have seen very little change, the router is one such area of code, now that's about to be overhauled....completely!
I recently migrated a clients site from Joomla1.5 to Joomla2.5 and would like to share with you some of the issues I ran into. Essentially the migration was a success but only after a lot of extra work trying to recover from poor decisions along the way.
As far as I know there are 4 ways you could migrate your site:
- Manually table by table using the process detailed here: link to joomla migrate
- Using the new JUpgrade Pro Restful methodology (Sounds great)
- Using the older Jupgrade free utility (doesn't sound too bad)
- SP Migrate (Another Commercial App)
During my migration, I used 2 and 3 and a bit of 1.
I implemented the popular RSEvents component for a client. Everything went well including setting up the individual paypal payments option which was a specific requirement for my client. This was to be used by franchisees to collect their own payments.
We were 1 hour before go-live(literally) when my client asked "how do we turn off VAT for some owners and not others?"...
If you manage websites and have gone through or about to go update PHP to 5.3, you will almost certainly come accross the following error on your sites as a result. You may not even have know about the upgrade and suddenly start seeing these warnings all over your site:
ereg-is-deprecated in ..
If you upgraded to PHP 5.3, chances are high you’re going to run into a few warnings or deprecated function messages. An example is the
ereg family of functions, which are gone for good, as they were slower and felt less familiar than the alternative Perl-compatible
To migrate ereg():
ereg('\.([^\.]*$)', $this->file_src_name, $extension);
preg_match('/\.([^\.]*$)/', $this->file_src_name, $extension);
Notice that the pattern (
\.([^\.]*$)) is wrapped with
/ /, which are RegExp delimiters. If you find yourself escaping
/ too much (for an URL for example), you might want to use the
# delimiter instead.
but the above snippets provided me enough to work with and clean up several clients sites after my hoster upgraded PHP.