Support

I have questions about version compatibility and I am confused by what I have read. Maybe I have not read the correct material.

Site one (referred to as ECAM):
Joomla 1.5.26
Akeeba: 3.1.5
PHP: 5.3.27
MySQL: 5.1.73

Site one (referred to as WMP):
Joomla 3.3.6:
Akeeba: 4.0.5
PHP:5.4.34
MySQL: 5.5.40

Kickstart, I have version 4.0.0 and 3.1.5

I am unable to restore the ECAM site on a ECAM or WPM sub-domain.
Are Akeeba 3.1.5 backups compatible with Kickstart 4.0.0? If not, what should I use? The Kickstart 4.0.0 seems to unpack the 3.1.5 file, but will not take the next step of setting up the database it throws a page full of errors. I have tried to manually load the database, but it does not appear that the directory structure is complete (or Kickstart did not really complete the process).

When I try to run Kckstart 4.0.0 on ECAM I get an 500 Internal server error.

The Kickstart 3.1.5 does not seem to work on either system. I starts and shows the screen that lets me select the extract name, but the start button does not work.

Can I load Akeeba 4.0.5 on the Joomla 1.5.26 (ECAM) system? If so, I can try to do a back up and restore that way.

Cheers,
Todd

Hi Todd,

Kickstart is only a simple extractor, it extracts the files from the archive. When the extraction is done, it hands off control to the installer code. This is important in your case because of the different versions involved. Kickstart 4.0.0 should be backwards compatible with all versions of the jpa or jps archive.

The installer code is embedded in your archive by the backup software. So your ECAM backups are using the installer from the Akeeba 3.1.5 version. Your WMP backups are using the installer from the 4.0.5 version.

When dealing with different versions of Joomla! as you are, you can't restore one version on top of a different version, you should delete all the files first. You can restore a 1.5.x site on top of a 1.5.x site, but you can't restore a 3.3.x site on top of a 1.5.x site.

I don't think you are restoring over the existing site, I think you're installing in a sub-folder. Keep in mind that in that circumstance the .htaccess file from the top site is inherited by the sub site. The inherited .htaccess file could cause the 500 error, especially if you are using Admin Tools' .htaccess Maker on the top site.

And last, what does "a page full of errors" look like? I need additional information before I can try to help with that.

Thank you.

I am always installing in a clean directory, However, you .htaccess point is a good one and my be a part of one problem I am having. One at a time:

1) On the ecaminc site when I install in as sub-domain (sub-folder) the site redirects to back the main site. In other words type in joom15.ecaminc.cam and the site ecaminc.com is displayed. Could that be the .htaccess issue you refer to? I am adminttedly over my head in this area. I am a quick study, but not a unix guy.

2) When I restore on the WMP site I get a bunch of errors similar to:
Strict Standards: Non-static method JLoader::import() should not be called statically in /home/watermel/public_html/ec1526/libraries/joomla/import.php on line 29
Strict Standards: Non-static method JLoader::register() should not be called statically in /home/watermel/public_html/ec1526/libraries/loader.php on line 71

I get these errors after the unpacking, or when I try to access the site. I few minutes ago I finished an FTP upload of the and it does tha same thing. So I do not think this is an Akeeba issue it is site related. As I am writing this (my copy just got done), I searched an this is probably a PHP version incompatibility.

So now I am back to the old site ECAM and trying to the the restore to work there.

When I try to use kickstart 4.0.0 on the ECAM site I get an internal server error 500. Does this make sense?

Assuming that you used Admin Tools' .htaccess Maker on the root site:

1. That absolutely makes sense. One of the options in .htaccess Maker is to redirect all index.php calls to the main root and administrator index.php versions. That is exactly what is happening, the SubSite.com/index.php is being redirected to MainSite.com/index.php. See the discussion here: https://www.akeebabackup.com/documentation/troubleshooter/atsubdomains.html for more information about how to get around it.
2. "Strict standards" at least is not an error, it is a warning. Your error reporting is set too high in the configuration.php file. During installation, the PHP settings are controlling, not Joomla!, so you may have to work around it. After the site is up, the Joomla! setting will take over. We may be able to override the PHP settings with an .htaccess command or a local php.ini file, but those are not easy work arounds.

Are you using Kickstart Pro? That version has a vulnerability and must be renamed before it can be used. "Fred.php" will work fine, anything you want to name it except "kickstart". There is a possibility with the Pro version that an attacker could substitute a remote archive for your archive during the extraction process. Not very likely but theoretically possible. The Core version does not have this vulnerability.

Interesting article. Thank you.

However, it points me away from the .htaccess file because http://rescuetheproblemproject.com/ and http://toddcwilliams.com/ are both subdomains on this site and they work fine. (They are next in the upgrade process.) The other is that I can get to the admin panel (http://joom1526.ecaminc.com/administrator/), I think .htaccess would not discriminate at at point.
Thoughts?
Todd

I found it. A module that I had implemented about 2008 to fix a canonicalization issue.
Sorry for making you scratch your head. I owe you a beverage of your choice.
However, I must also think you for the support and great education.

Todd,

I'm glad you got it figured out. Have a great weekend!