Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Moderator: General Support Moderators
Forum rules
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting, this means YOU.
Forum Post Assistant - If you are serious about wanting help, you will use this tool to help you post.
Forum Rules
Absolute Beginner's Guide to Joomla! <-- please read before posting, this means YOU.
Forum Post Assistant - If you are serious about wanting help, you will use this tool to help you post.
-
- Joomla! Fledgling
- Posts: 1
- Joined: Fri May 25, 2012 5:26 am
Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Hello,
We are about to migrate 200 Joomla websites to a new server.
Some of these sites are Joomla 2.5 websites but most of them are 1.5.
We are aware about requirements for Joomla 1.5.x
- PHP 5.2+
- MySQL 4.1.x
- Apache 2.x+
Our new server configuration is:
- PHP 5.3.13
- MySQL 5.1.63
- Apache 2.2.22
After moving a couple of Joomla 1.5 webistes to this new server, we have experienced blocking issues.
Several different reasons:
- missing menus in websites frontend
- missing menus in Joomla backend within Menus > my_menu > *
- not able connect to Joomla backend (built-in http://www.my_site/administrator login)
- 3d part booking systems down
Would you be able to advise on:
- any PHP 5.3.13 / MySQL 5.1.63 / Apache 2.2.22 settings we could get to run Joomla 1.5 websites without issues
- any Joomla 1.5 patches that we should use or create
in order to avoid well known issues that we are going to eperience going through our migration?
We cannot afford to upgrade 150 Joomla 1.5 websites to a Joomla 2.5 version.
Thanks,
Qclick
We are about to migrate 200 Joomla websites to a new server.
Some of these sites are Joomla 2.5 websites but most of them are 1.5.
We are aware about requirements for Joomla 1.5.x
- PHP 5.2+
- MySQL 4.1.x
- Apache 2.x+
Our new server configuration is:
- PHP 5.3.13
- MySQL 5.1.63
- Apache 2.2.22
After moving a couple of Joomla 1.5 webistes to this new server, we have experienced blocking issues.
Several different reasons:
- missing menus in websites frontend
- missing menus in Joomla backend within Menus > my_menu > *
- not able connect to Joomla backend (built-in http://www.my_site/administrator login)
- 3d part booking systems down
Would you be able to advise on:
- any PHP 5.3.13 / MySQL 5.1.63 / Apache 2.2.22 settings we could get to run Joomla 1.5 websites without issues
- any Joomla 1.5 patches that we should use or create
in order to avoid well known issues that we are going to eperience going through our migration?
We cannot afford to upgrade 150 Joomla 1.5 websites to a Joomla 2.5 version.
Thanks,
Qclick
- dpacadmin
- Joomla! Champion
- Posts: 6029
- Joined: Sat Aug 16, 2008 1:46 pm
- Location: the Bat Cave
- Contact:
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
You need Joomla 1.5.15 or higher for your sites to be compatible with php 5.3. Those sites that are older then 1.5.15 will need to be upgraded first before moving.
http://joomlacode.org/gf/project/joomla ... ge_id=4947
I strongly suggest you update all 1.5 sites to the latest version 1.5.26 so they have the latest security updates as well. You can use this patch to update all older Joomla 1.5 sites to the latest version;
http://joomlacode.org/gf/download/frsre ... ackage.zip
If your sites use any of the default templates with modifications you may need to redo the modifications again after the update. If any of your sites have modified core Joomla files you may need to redo the modifications after the update. Use Akeeba Backup to backup all sites before updating them so you have a backup to fall back to should you need to.
http://joomlacode.org/gf/project/joomla ... ge_id=4947
I strongly suggest you update all 1.5 sites to the latest version 1.5.26 so they have the latest security updates as well. You can use this patch to update all older Joomla 1.5 sites to the latest version;
http://joomlacode.org/gf/download/frsre ... ackage.zip
If your sites use any of the default templates with modifications you may need to redo the modifications again after the update. If any of your sites have modified core Joomla files you may need to redo the modifications after the update. Use Akeeba Backup to backup all sites before updating them so you have a backup to fall back to should you need to.
- dpacadmin
- Joomla! Champion
- Posts: 6029
- Joined: Sat Aug 16, 2008 1:46 pm
- Location: the Bat Cave
- Contact:
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
What module problem?goodgirlsx wrote:Hi
.....but please guide me whether it was not my problem with the module installed?
thank you .
You should be able to use the 1.5.0 to 1.5.26 update file to update your site. Make sure to backup your site first, files and database. The Akeeba Backup extension can do the backup for you. If you are not comfortable FTP'ing the update files to your site you can install the Admin Tools extension, it can update your site for you.
-
- Joomla! Enthusiast
- Posts: 154
- Joined: Wed Aug 25, 2010 11:10 pm
- Location: Australia
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Hi,
This info was posted a while ago. My server guy is considering mysql 5.6.
Is 1.5.26 compatible with this and are there any known issues with later Joomla versions that I should be aware of?
Any advice appreciated.
This info was posted a while ago. My server guy is considering mysql 5.6.
Is 1.5.26 compatible with this and are there any known issues with later Joomla versions that I should be aware of?
Any advice appreciated.
- dpacadmin
- Joomla! Champion
- Posts: 6029
- Joined: Sat Aug 16, 2008 1:46 pm
- Location: the Bat Cave
- Contact:
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
The requirement page here;
http://www.joomla.org/technical-requirements.html
says Joomla 1.5 should work on MySQL 4.1 and higher but it does not work on MySQL 6.
http://www.joomla.org/technical-requirements.html
says Joomla 1.5 should work on MySQL 4.1 and higher but it does not work on MySQL 6.
-
- Joomla! Enthusiast
- Posts: 154
- Joined: Wed Aug 25, 2010 11:10 pm
- Location: Australia
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Thanks dpacadmin,
better safe than sorry
better safe than sorry
- Webdongle
- Joomla! Master
- Posts: 44037
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Also please see http://docs.joomla.org/Security_hotfixe ... L_versions
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
-
- Joomla! Apprentice
- Posts: 6
- Joined: Tue Mar 08, 2016 6:31 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
@dpacadmin: You mentioned Akeeba Backup as a component/functionality which is critical to the problem of migration discussed in this topic. (attention of moderator: that indicates that the question is relevant to the topic)dpacadmin wrote: The Akeeba Backup extension can do the backup for you.
So what is a recommended course of actions during migration if Akeeba backup was not earlier installed on the currently outdated 1.5 site that now should be migrated to 3.x. ? Installing it now might be a risky proposition. Thank you in advance.
- Webdongle
- Joomla! Master
- Posts: 44037
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Akeeba Version compatibility
https://www.akeebabackup.com/compatibility.html
https://www.akeebabackup.com/compatibility.html
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
-
- Joomla! Apprentice
- Posts: 6
- Joined: Tue Mar 08, 2016 6:31 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
@Webdongle: Thank you for your response. Yes, of course I looked at the official compatibility article before asking my question. Very old versions of Akeeba backup still exist and can be downloaded but they are not supported by Akeeba anymore. An attempt to install backup component might fail for unpredictable reasons leaving the site in unpredictable state. And if backup files do not exist the site might be completely lost. Pure gamble. So I am very interested in expert opinions what is the reasonable course of actions during migration in those cases.Webdongle wrote:Akeeba Version compatibility ...
- Webdongle
- Joomla! Master
- Posts: 44037
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Then make a database dump and make a backup of your files from your Host's cp before you install Joomla. That way if the install mucks things up you have a backup but if it installs and works you have an installable backup.bonfa wrote:... An attempt to install backup component might fail for unpredictable reasons leaving the site in unpredictable state. And if backup files do not exist the site might be completely lost. Pure gamble.....Webdongle wrote:Akeeba Version compatibility ...
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
- dpacadmin
- Joomla! Champion
- Posts: 6029
- Joined: Sat Aug 16, 2008 1:46 pm
- Location: the Bat Cave
- Contact:
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
@bonfa
It is always good practice to have a working backup of your site, that is why Akeeba always recommends testing your backup to be sure it is a working backup. Your Host, if it is a good one, should have a backup system for your site as well. A backup should include all site files as well as a database backup, this is what Akeeba Backup(AB) creates. Older versions of AB were not as intuitive as the latest version but it should be complete.
If you install an AB version that is recommended for the Joomla version you are running you should be OK, just check your php version against the recommendation for the AB version you want to install.
With a robust backup system by your Host the AB backup should be a fall back, but you need to test the backup AB creates to be sure it is a valid working backup. I test locally in a WampServer environment but if you create a new database on your Host you should be able to test your AB backup in a sub-folder on your Host. You could then use that backup to test with if it is a working backup.
Hope this helps.
It is always good practice to have a working backup of your site, that is why Akeeba always recommends testing your backup to be sure it is a working backup. Your Host, if it is a good one, should have a backup system for your site as well. A backup should include all site files as well as a database backup, this is what Akeeba Backup(AB) creates. Older versions of AB were not as intuitive as the latest version but it should be complete.
If you install an AB version that is recommended for the Joomla version you are running you should be OK, just check your php version against the recommendation for the AB version you want to install.
With a robust backup system by your Host the AB backup should be a fall back, but you need to test the backup AB creates to be sure it is a valid working backup. I test locally in a WampServer environment but if you create a new database on your Host you should be able to test your AB backup in a sub-folder on your Host. You could then use that backup to test with if it is a working backup.
Hope this helps.
-
- Joomla! Apprentice
- Posts: 6
- Joined: Tue Mar 08, 2016 6:31 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
@Webdongle
Yes, it is a good idea. I've never tried using CP backup and the time is now. Interesting though how to test this CP backup file(s) because restoring will be probably exactly "in place". So bad backup could overwrite the good site. But it is something to clarify with the specific provider if restore location could be different from the source one (in the same account)
Thank you for a good hint. You are right and I will remember it!
Yes, it is a good idea. I've never tried using CP backup and the time is now. Interesting though how to test this CP backup file(s) because restoring will be probably exactly "in place". So bad backup could overwrite the good site. But it is something to clarify with the specific provider if restore location could be different from the source one (in the same account)
Thank you for a good hint. You are right and I will remember it!
- Webdongle
- Joomla! Master
- Posts: 44037
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
If you are allowed only one database you can still use the backup but it is tricky. Try https://docs.joomla.org/XAMPPbonfa wrote:... So bad backup could overwrite the good site. But it is something to clarify with the specific provider if restore location could be different from the source one (in the same account) ...
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
-
- Joomla! Apprentice
- Posts: 6
- Joined: Tue Mar 08, 2016 6:31 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
@WebdongleWebdongle wrote: Try https://docs.joomla.org/XAMPP
Do you mean that it is possible to restore Control Panel backup (files + db) on local XAMPP? Actually I use XAMPP all the time for development purposes and in particular I test Akeeba backups made on the Host server by restoring them on my localhost XAMPP. But restoring CP backup on local server is some new scenario (if that is what you meant).
-
- Joomla! Apprentice
- Posts: 6
- Joined: Tue Mar 08, 2016 6:31 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Yes, there is some overlap in acceptable PHP versions for 1.5 sites and the earliest available Akeeba backup software. Looks like the most realistic scenario is first to upgrade whatever 1.5.x we have to the highest 1.5.26 using the upgrade package that you suggested earlier. Joomla 1.5.26 requires PHP 5.3. And then to install AB 3.4.6 that also requires PHP 5.3.dpacadmin wrote:
... just check your php version against the recommendation for the AB version you want to install.
... you need to test the backup AB creates to be sure it is a valid working backup. I test locally in a WampServer environment but if you create a new database on your Host you should be able to test your AB backup in a sub-folder on your Host.
As for testing AB. For a long time now I had been using my local XAMPP to restore AB backups made on the Host for testing their quality.
It seems (see discussion below) that it was suggested to test Control Panel backups made on the Host by restoring them on local XAMPP. If this is realistic then it solves the problem and even for the worst case scenario of migration (Joomla 1.5.x to 3.x) we have solid and reliable workflow in place.
Thank you.
- Webdongle
- Joomla! Master
- Posts: 44037
- Joined: Sat Apr 05, 2008 9:58 pm
Re: Joomla 1.5 / PHP 5.3.13 - MySQL 5.1.63 - Apache 2.2.22
Yes ... it's not rocket science.bonfa wrote:...
Do you mean that it is possible to restore Control Panel backup (files + db) on local XAMPP? ...
- Create a database and import the sql file
- Create a folder in C:\xampp\htdocs and copy the files to it
- Edit the configuration.php to connect to the database
The php in xampp may be to high to run Joomla 1.5. You may wish to try http://www.uniformserver.com/ ? You can install different php versions into it and select which php you wish to use.
http://www.weblinksonline.co.uk/
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".
https://www.weblinksonline.co.uk/updating-joomla.html
"When I'm right no one remembers but when I'm wrong no one forgets".