Support

I'm doing a migration from a live J1.5 to dev J3.6. The J3.6 site is installed in a new folder in the J1.5 root location.

It's a basic install, no sample data, no extensions beyond the core ones.

I have Admin Tools Pro installed in the live j1.5 site from which I'll be migrating data from.

I'm having problems, like getting the temp folder recognized, and upgrading the J3.6 core to the newest version, 3.6.1, although the Joomla Updater extension installed fine.

I get this error when trying to update the core: "ERROR: AJAX Loading Error: Forbidden"

Tmp folder exists and is writeable. The temp path is entered as:
/var/www/vhosts/(website.com)/httpdocs/new/tmp
(where "new" is the subdirectory with the new 3.6 install).

Would Admin Tools in the root (1.5) install be creating problems for the subdirectory (3.6) install? (Separate databases.)

If so, how can I allow an exception for the folder containing the 3.6 install.

Thank you!

Absolutely! Both the Admin Tools and the .htaccess files from the 1.5 site would be inherited by the 3.6 site if it is in a sub directory of 1.5.

If you can reinstall your 3.6 in a folder beside 1.5, say in public_html2, that is the right fix. Some hosts allow this, some do not.

If you have to band aid it, you will need to change 1.5's .htaccess maker to allow all files to execute, including php, in the 3.6 folder. You'll also need to disable redirect all index.php to the root feature.

Thank you, Dale!

If you have to band aid it, you will need to change 1.5's .htaccess maker to allow all files to execute, including php, in the 3.6 folder. You'll also need to disable redirect all index.php to the root feature.

I would not have the slightest idea how to do this, unfortunately, but would like to know. :)

If you can reinstall your 3.6 in a folder beside 1.5, say in public_html2, that is the right fix.

I will see if that is possible. Would a subdomain work, also?

Thank you.

It was late, I cheated a little bit and was a tad vague. :-)

I only have the latest version of .htaccess Maker available, so there may be some differences in the version you are using on the 1.5 site. In .htaccess Maker, in the Exceptions section, in the "Allow direct access, including .php files, to these directories" box, add the path to your 3.6 subdirectory. So if you have 3.6 installed in a folder joomla36, you would add joomla36 on a new line in that box. That allows PHP files in that folder to be called directly. We need that to run the 3.6 installation.

In the Optimisation and utility section, set "Redirect index.php to the site's root" to No. This allows the 3.6 index.php file to run without being redirected to the 1.5 index.php file in the root.

As long as the 3.6 install is a sub folder of 1.5, the subdomain will not matter, it will still inherit the .htaccess file.

>It was late, I cheated a little bit and was a tad vague. :-)

I completely understand. No worries on my end. :)

You instructions were quite clear and worked just fine. Thank you! Once you know how to do it, it's easy. :)

My dev/migration 3.6 install may take up to a month to work all the kinks out, then I'll be moving it over and replacing 1.5 root location. Can set up an Admin Tools .htaccess in this dev location (3.6) to prevent any malicious activity, or will that conflict with the root 1.5 .htacces file?

Thanks.

No, the 1.5 site will not inherit from the 3.6 site. I usually use the host's password protect folder to add a user ID and password to the development site. Not so much to keep users out as to keep Google, et. al. from finding it. You can't do that through Admin Tools because it only protects the /administrator folder, not the root of the site.

You're welcome!

Thank you, Dale. Good advice.

One last question relating to issues with htaccess and a Joomla subdirectory install:

The annoying "Tha path to the temporary folder is not set" warning.

Even though I have the path set to /var/www/vhosts/website.com/httpdocs/new/tmp, I get the warning. Setting the path to tmp or /tmp doesn't work, either.

Is this a problem related to the 1.5 or 3.6 htacess or an issue with the "undiscoverable" php.ini file?

Thanks.

That can get tricky because it is normally the path from the root of the server and there are folders in that path that you can't even see. Go to Admin Tools, click the Temp and Log Directory Check button. I am not sure if that will just give you the same message that it is wrong or if it will help you fix it.

Hi, Dale.

>Go to Admin Tools, click the Temp and Log Directory Check button

I did that check and no warnings came up. The paths looks good (for the brief time I could see them).

I'll go ahead with the SPUpgrade tool to migrate my 1.5 site, then I'll turn on Admin Tools protection when that is complete. I'm afraid of interfering with the migration in some way I wouldn't understand.

Sound good?

Thx.

Yes!

Please let me know if I can be of any more help.

Dale,

It turns out the the php.ini file had max upload set to 8MB already.

/etc/php.ini

The other day I had no problem installing Admin Tools Pro (1.6MB), but the J3 install balked at installing Akeeba Backup (2.6MB).

The host changed the php.ini file ( /etc/php.ini) to 10MB today.

Still won't accept Akeeba Backup. Error: php max upload size too small.

Admin Tools is not "live".

Any ideas?

Thsnks.

Yes, there is another setting that has to be changed in connection with max_upload_size. You also need to change post_max_size, which can override max_upload_size. (Are we having fun yet?)

There are examples of the two settings here: https://www.akeebabackup.com/documentation/troubleshooter/abinstallation.html.

Thanks, Dale. Yes, I'm having fun.

Adding

php_value upload_max_filesize 10M
php_value post_max_size 10M

to the root .htaccess caused an internal server error and killed the J3 admin page (at least, I didn't check live b/c there is no content.

BTW, the J3 install does not have the .htaccess activated in the subdirectory. Just a plain J3 install w/o content.

Trying the "install from URL" method yielded: Error connecting to the server: 403

In the J3 install, under PHP Info at the open_basedir field, I see the path to the temp directory is:

/var/www/vhosts/website.com/:/tmp/

That differs from what the Admin Tools J3 install shows in configuration.php:

/var/www/vhosts/website.com/httpdocs/tmp

What should be where? (I can change the configuration.php but don't know who to change the first line, open_basedir field.

Thanks.

In your open_basedir path, the colon is a separator, so those are two separate paths.

For the "Install from URL" please double check your Download ID. I don't expect that is the problem, but it could cause a 403. There are a couple of other gotchas at https://www.akeebabackup.com/documentation/akeeba-backup-documentation/installation-updates-upgrades.html#installing-from-url. Also there is the way to get the right URL for the install.

Dale,

>In your open_basedir path, the colon is a separator, so those are two separate paths.

Which, then, is the correct path? The one to the root's tmp folder?
/var/www/vhosts/website.com/httpdocs/tmp

How would I change the other, the one with the semicolon that appears in the open_basedir?

IOW, which tmp path is the appropriate one for the subdirectory J3 install?

>For the "Install from URL" please double check your Download ID.

Can't use the ID until I've installed Akeeba Backup. :(

Akeeba Backup Pro is installed in the root 1.5 install. If I try the manual install method (the only option left) from the root tmp folder, will that mess up the root, live site?

I may have to forgo the Akeeba Backup install in the J3 site while I'm it is in dev, but I'd prefer to have it.

:)

I'm sorry, I think the proper tmp path for the 3.6 site is:

/var/www/vhosts/website.com/httpdocs/new/tmp

I missed the new folder. What you currently have is the right path for the 1.5 site. The open_basedir doesn't affect the 3.6 site because it is farther down the tree from the 1.5 site.

Thanks, Dale.

the proper tmp path for the 3.6 site is:

/var/www/vhosts/website.com/httpdocs/new/tmp

That is the path being reported by Admin Tools, and that is the path listed in the configuration.php.

So it is that path I should attempt the manual install of Akeeba Backup Pro?

Or should I just move on and wait until I make the dev site live, then install ABP?

don

Yes, that would be the path for the manual install. Sometimes you want a backup of a development site too, so I think the manual install is worth a try.

Thanks, Dale.

The manual install worked fine.

Now I'll be using the SPUpgrade app to transfer core files and other data from the 1.5 site. The SP app connects to the 1.5 site fine, so I'm going to hope this is the end of my troubles related to the title to this thread.

Thanks for your support and patience.

You are welcome!