Error upgrading form J3.10.11 to 3.10.12

[antonios]

Hi,
I am on my way to upgrade my actual version of J fro 3.10 to 4.x, I thought that upgrading to the lates 3.10.x would better before engaging with 4.x. But maybe it is not necessary?
So when I try to Upload and install 3.10.12 get the following issue:

Error
COM_INSTALLER_MSG_INSTALL_WARNINSTALLUPLOADERROR

and

Warning: is_writeable(): open_basedir restriction in effect. File(/home/permacul/domains/permacultura-es.org/public_html/tmp) is not within the allowed path(s): (/mnt/home3_1/permacul/:/tmp/:/var/tmp/:/opt/alt/php81/usr/share/pear/:/dev/urandom:/usr/local/php74/lib/:/usr/local/php81/lib/:/usr/local/php74/lib/:/usr/local/php56/lib/:/usr/local/php83/lib/:/usr/local/lib/php/) in /mnt/home3_1/permacul/domains/permacultura-es.org/public_html/administrator/components/com_installer/models/warnings.php on line 12

Also when I go to the "Upload & Update" tab a message appears saying:

Warnings
The PHP temporary folder is not set.
The PHP temporary folder is the folder that PHP uses to store an uploaded file before Joomla can access this file. Whilst the folder not being set isn't always a problem, if you are having issues with manifest files not being detected or uploaded files not being detected, setting this in your php.ini file might fix the issue.

The Joomla temporary folder is not writable or does not exist.
The Joomla temporary folder is not writeable by the Joomla instance, or may not exist, which may cause issues when trying to upload extensions to Joomla. If you are having issues uploading extensions, make sure the folder defined in your configuration.php exists or check the '/home/permacul/domains/permacultura-es.org/public_html/tmp' and set it to be writeable and see if this fixes the issue.

I tried looking for and setting this temporary folder in my php configuration panel, but could not find any php variable related to this.
I also changed access privileges to the /public_html/tmp folder to make it writable by all, to no avail.
What else can be done?

[Per Yngve Berg]

Empty the Open_Base Directive in PHP.ini that blocks you.

Updating is done using the Update Component, not the Installer.

[antonios]

Empty the Open_Base Directive in PHP.ini that blocks you.

Updating is done using the Update Component, not the Installer.

Hi Per,
I cannot access the PHP.ini file directly. My Joomla is using PHP 7.4
I seem to have a limited access to some of the directives but Open_Base doesn't seem to be there
What I did was creating a

Code: Select all

user.ini

file and inserted

Code: Select all

open_basedir 'none'

and then

Code: Select all

open_basedir ""

but I get the same results / error messages
If this is not the right way to do it, how else can I empty it?
Regards

[Per Yngve Berg]

Contact your host.

[antonios]

To ask what?

[Webdongle]

To ask what?

To make the changes you were requested to but can't.

[antonios]

Well the host said to me to use softacolous....by importing the actual instance of joomla into it and then doing the upgrade and it actually worked!
(I wonder if this also works for migrating to J4)

[Webdongle]

So originally you didn't install Joomla using the Joomla full installation package zip?

[antonios]

I did, I did it manually following the instructions

[gws]

Be aware that softaculous doesn't use the joomla installer and is a lot less fussy to joomla standards. I doubt you will find anyone on the forums who recommends softaculous or similar for a live site.

[antonios]

I see. The problem was that the sys admin didn't probably want to touch open_basedir and directed me to doing something which was better for him, however I managed to upgrade to 3.10.12 while before I couldn't.
Let's see how I fare with upgrading to J4.
By the way, do I have to go through J4 before upgrading to J5 or can I just upgrade to J5?

[Webdongle]

Yes you do
Best (imho) https://wampserver.aviatechno.net/ on your pc.
Install wamp then create a new folder in Wamp's \www folder
Use Akeeba to backup your site and kickstart to unpack and run the backups installer https://docs.joomla.org/Copying_a_Jooml ... _Method.29

On wamp localhost the database will be created during install.
If the update fails just create a second new folder in Wamp's \www folder and install the backup to that one.

I use 01, 02, 03 at the end of the folder names and match the database name to the folder name.

With Wamp
user: root
pass: is left blank by default.

Once updated you can remove the live site and drop the live site's database tables then install the updated site.

[Per Yngve Berg]

Change Host. Configuring a server with open_base is so Old Fashion.

[antonios]

Thank you all for your advice!

[antonios]

Change Host. Configuring a server with open_base is so Old Fashion.

Per, what would be a more appropriate/modern way to configure the server without using open_basedir?

[gws]

Its not necessary these days. Most servers are far more secure these days out of the box.

[Webdongle]

https://support.plesk.com/hc/en-us/arti ... ce-Booster

Disabling restriction for open_basedir increases the website loading speed significantly and according to PHP documentation keeping the restriction active doesn't provide a noticeable security benefit.

The industry standard for most of the largest web hosting companies is to have open_basedir set to none, but disabling undesired PHP functions in order to increase security instead.