I just tried upgrading from 1.3.4 to 1.3.5 and the upgrade has failed - please try again. I would download the error log and post however I get an error saying duplicate headers. On of the error messages says:
2016-08-04 21:33:31 - PHP Notice: Undefined variable: options_to_list_status in /home/digitadr/public_html_system_modification/catalog/view/theme/default/template/common/footer.tpl on line 130
2016-08-04 21:33:31 - PHP Notice: Undefined variable: options_to_list_status in /home/digitadr/public_html_system_modification/catalog/view/theme/default/template/common/footer.tpl on line 130
Share this post:
Responses (37)
-
Accepted Answer
Rune, sorry if I wrote your name wrong. I never being root to nobody.But anyhow the issue is solved. I don't know how.
Kind regards
Hermann -
Accepted Answer
-
Accepted Answer
Please post your system info: https://arastta.org/docs/user-manual/tools/system-information
Also try setting your site offline manually, then disable all modification and run refresh, plus cleaning the site cache in settings. Then try the upgrade again, and if still any error, post the exact message / image of it. -
Accepted Answer
The update still failed after trying your suggestions. I put the site in maintenance mode. Is that what you mean by setting the site off manually?
I disabled all modification, ran refresh and cleaned the site cache in settings. I've shown a list of modifications I have in the attachments. The ones enabled are the only ones I normally enable. I disabled each of these when I tried the upgrade. -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
Weird. But I don't see what the max values are, maybe I overlooked it, but what are the values for t.ex.:
- max_input_vars
- memory_limit
- max_execution_time
- upload_max_filesize
- mysql.connect_timeout
Try adding the attached file to your store root (unzip first), and rename it .user.ini to see if it helps. - max_input_vars
-
Accepted Answer
I can't download the attachment. It takes me to this page but download never starts. Can you send another way? -
Accepted Answer
Create a .user.ini in stores root, with t.ex. this content:
magic_quotes_gpc = Off;
register_globals = Off;
default_charset = UTF-8;
max_input_vars = 20000;
memory_limit = 300M;
max_execution_time = 36000;
upload_max_filesize = 999M;
safe_mode = Off;
mysql.connect_timeout = 90;
session.use_only_cookies = On;
session.use_trans_sid = Off;
session.cookie_httponly = On;
session.gc_maxlifetime = 3600;
allow_url_fopen = on; -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
-
Accepted Answer
The "errors" in log is just notifications, not show stoppers, and they are not related to the update ...
Is Suhosin and/or ModSecurity active on the server? They often have own limits, overriding those in php.ini, which only server admin normally can change.
Maybe you could add a file in the root displaying the full php info? Just give the file a random name ending in .php and PM the link to me, easier to get the full picture then.
Add into the file:
<?php
phpinfo();
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »