On 5/4/2021 at 10:39 PM, musicmaster said:
I am afraid that your main problem is with your server settings.
In case of a 500 error you should enable debug mode and report the error here. You never did so so we couldn't help you.
Noone had asked prior to your suggestions.
I was delving into the debug log, which was not particularly helpful. That is a beyond the key problem of the 1-click not working as implied when following it's instructions and lack of. After uncovering some more server settings, I managed to get most of it, but not all, and only for a fresh default installation, nowhere near upgrading an actual store.
For those attempting to get somewhere with the 1-click module, on a clean fresh 1.6.24 install;
Add these to the end of the .htaccess; it may correct some server level settings, timeouts etc. This at least prevented the upgrade falling over partway through.
=== .htaccess ===
php_value memory_limit 512M
php_value max_execution_time=300
php_value max_input_time=-1
php_value upload_max_filesize 10M
php_value post_max_size 20M
On top of this, ensure that your PHP settings under CPanel, or server configuration have the following enabled;
QuoteMust have PHP extensions: cURL, DOM, Fileinfo, GD, Intl, Mbstring, Zip, Json, iconv
To improve performances: MemCached, Apcu, OpCache
In my case cURL, iconv, OpenSSL were not available for selection, but confirmed with host and testing that they were turned on.
But even with this, the backend is non-functional following an 1-click upgrade. There's a few threads around discussing a long overdue bug requiring you to reset the admin privileges. Ie... if this manual step is required, the 1-click is not functioning as 1-click 1.6.24 to 1.7.x
access not complete until resetting admin account;
In CPanel, start PhpMyAdmin, select the Prestashop database, and in the SQL tab enter; alter psjz_ to whatever prefix your tables may have...
QuoteUNABLE TO ACCESS BACKEND ADMIN FEATURES
https://www.prestashop.com/forums/topic/876786-solved-prestashop-17-access-denied-as-admin-in-bo/?tab=comments#comment-3311835
Solved issue with this query that reset all permissions in SuperAdmin
delete from psjz_access where id_profile = 1;
insert into psjz_access (id_profile, id_authorization_role) select '1' as id_profile, id_authorization_role from psjz_authorization_role;
=part way there, but nowhere near a successful migration. It shows even a fresh install can run into problems with hosting settings, and that 1-click screws up the admin permissions in the database. As far as I can tell the need to reset database has been reported for the past 18months or more.
QuoteYou can try making a copy of your shop with my tool copy_shopdata en upgrade that:
Thank you for that, having given up on the 1-click, I've spent the past few days on the thirty-bees 1.2.0 conversion option (default thirtybees migrate/upgrade to 1.2.0 resulted in shopping carts that empty themselves on checkout), and so today I tried the copy_shopdata path instead.
Another brick wall unfortunately, even with running through prestatools, cleaning etc.
Without inspiration, I'll need to start from scratch or piece together some of the migrated data into a fresh install, or ... give up.
Trying to run copy_shopdata results in "MySQL error 1045: Access denied for user"
This is not the obvious stuff up of users, servers, passwords... or % characters in passwords.
Resetting password etc multiple times, entering into store clone and successfully viewing the frontend...
... as testaccess.php next to the copy_shopdata.php file in the destination admin/prestatools/ directory of a thirtybees Cpanel-softaculous installed version, the following script indicates a successful connection. Variants of localhost etc also tested. I'm stumped on this one. I also tried adding the .htaccess limits and timeouts I posted above into the destination store directory.
Quote
<?php
$servername = 'domain.net.au';
$database = 'domainau_prestst';
$username = 'domainau_prestst';
$password = 'plainpassword5';// Create connection
$conn = new mysqli($servername, $username, $password, $database);
// Check connection
if ($conn->connect_error) {
die("Connection failed: " . $conn->connect_error);
}
echo "Connected successfully";
?>