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
Friday, August 05 2016, 12:37 AM
Share this post:
Responses (37)
  • Accepted Answer

    Friday, August 05 2016, 12:46 AM - #Permalink
    I tried disabling all modifications and the update still fails. When I check the error log it is blank.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 01:18 PM - #Permalink
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 01:49 PM - #Permalink
    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.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:03 PM - #Permalink
    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, and rename it .user.ini to see if it helps.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:03 PM - #Permalink
    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, and rename it .user.ini to see if it helps.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:04 PM - #Permalink
    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.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:16 PM - #Permalink
    I can't download the attachment. It takes me to this page but download never starts. Can you send another way?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:18 PM - #Permalink
    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;
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:26 PM - #Permalink
    Still failed to update
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:31 PM - #Permalink
    So what does those values show in your system now, after adding the file, did they change?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:37 PM - #Permalink
    I don't think the values changed but I'm not sure where to look
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:45 PM - #Permalink
    Ensure the file is named .user.ini (starting with a dot), add also this to it:
    post_max_size = 999M;


    Check if this value changed after, in the left column. If not, ask you host to increase the values.
    Arastta zip is at the moment 19.6MB
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:46 PM - #Permalink
    Well, I don't think I uploaded the file correctly. I corrected it and the update still failed however I did get information in the error log. If I clear the log and try the update again the error log is empty.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:47 PM - #Permalink
    You didn't change the post_max_size ....
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:52 PM - #Permalink
    I added the additional line you requested. This time I can download the error log. I've attached below. I cleared the error log and tried running the update again. I've attached that file as well. It was a much shorter list.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:53 PM - #Permalink
    I added the additional line you requested. This time I can download the error log. I've attached below. I cleared the error log and tried running the update again. I've attached that file as well. It was a much shorter list.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 09:54 PM - #Permalink
    Yes, the values are changing. max size is now 999M
    The reply is currently minimized Show
  • Accepted Answer

    Friday, August 05 2016, 10:28 PM - #Permalink
    If I log out of administrator and then back in again I can duplicate the smaller error log. If I clear it and then try updating again the error log is empty.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, August 06 2016, 07:27 PM - #Permalink
    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();
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, August 06 2016, 10:25 PM - #Permalink
    Here's the php info. Hopefully that will give you the info you need.
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, August 06 2016, 10:27 PM - #Permalink
    Please send the link to the phpinfo script in a PM ...
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 10:58 AM - #Permalink
    Daniel, in most cases, update fails due to strict file/folder permission settings of hosting/server. You can download the installation package and upload the files manually as there is no database change in 1.3.5 version. Don't upload the install folder.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 06:13 PM - #Permalink
    Hi,

    I do have the same problem. I guess the database in not updated after the update, because if you delete the file "htaccess.txt" before the update he will be there after the update. Further the file "robots.txt" will be overwritten which is annoying. Before each update you've to save the file and put him back onto the server.
    Question; why this update do not function if any update before was OK?

    Kind regards

    Hermann
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 06:59 PM - #Permalink
    Sorry, but I found no obvious issues in your php.ini Daniel.

    Herman, when you delete a file you also deletes the set restrictions/rights on it. Thus it can be recreated/re-uploaded.
    robots.txt it's fixed by Denis for 1.4: https://github.com/arastta/arastta/commit/036acd6c698ac1b222de393f9f0be94fd8e74f6d

    There is no database updates in this release (version is set in a file btw), almost non changes at all, as you can see if you do a diff of 1.3.4 vs 1.3.5 files system - or browse the changes on GitHub: https://github.com/arastta/arastta/compare/1.3.4...master

    Question; why this update do not function if any update before was OK?

    The real question: What was changed on the server in between. If you use cPanel etc., there has been several changes during the summer, I'm quite sure of.

    I hardly see anything in the file changes of Arastta 1.3.5 that could cause any trouble, but haven't looked at 1.3.4 if there was anything there.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 07:50 PM - #Permalink
    Hi Rune,

    I've mentioned the htaccess.txt and robots.txt files to let you know the update is doing something. When I mentioned the database, I guess the version information's must be somewhere. I do not getting any error in the log files like Daniel.
    Further after doing the update I'm getting the message the update was successful. On the top of the header stays still the available update.
    So fare I remember that we've this in the past and it was an issue at the Arastta server.

    Kind regards

    Hermann
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 07:57 PM - #Permalink
    If you delete the version file, I'm sure that will be written too (and everything would look fine). The problem is most likely your file rights not allowing the update to overwrite the existing ones.

    The files is obviously downloaded, end tried extracted, as you self describe with the htaccess.txt, so it's not Arastta server. That was quite different, and if I don't recall wrong, there has been several issues with your server in the past.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 08:04 PM - #Permalink
    Rune, please let me know where is the version file. I don't understand, if the update write the htaccess.txt etc. why the version file is not written.

    Kind regards

    Hermann
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 08:08 PM - #Permalink
    I have told you why Herman,

    Anyhow: /system/library/version.php

    The rest will not update, even if you delete this, only the version. Also the system might break if you delete it, so try chmod 666 instead. ;)
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 08:59 PM - #Permalink
    Hi Rune,

    I've changed the file permission but no difference. Message: Update process has been completed successfully. The update has not proceed. Still same version.

    The php.ini is OK. If this could be a cPanel issue than I'm not alone with it. Would be nice I get an solution if it is so.

    Kind regards

    Hermann
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 09:18 PM - #Permalink
    Hermann Martinez wrote:If this could be a cPanel issue than I'm not alone with it. Would be nice I get an solution if it is so.

    Sure there is a lot of badly configured servers out there, hosts blindly updating etc.

    The fact that you have to delete files to get them updated tells us something, but what ... maybe the server admin could debug it.

    Anyhow, I'm also interested in figuring out more easily what's going wrong on those servers. Thus I posted this some days ago: https://github.com/arastta/arastta/issues/519

    Let's hope the core devs, or anyone else, finds a way to do this. Feel free to contribute if you have the needed coding skills.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 08 2016, 09:48 PM - #Permalink
    Ron, you got me wrong. I've not had to delete files to upgrade them. There were upgraded normally. I just deleted them in a second try to figure if there where written new too.

    Kind regards

    Hermann
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 09 2016, 12:23 AM - #Permalink
    htaccess.txt is nothing, it doesn't work if you don't rename it to .htaccess so it's more than normal to get overwritten.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 09 2016, 02:29 AM - #Permalink
    Ron, I know the difference between a .htaccess filte and an htaccess.txt file, I know tooooooooooooooo that the htaccess.txt file is doing nothing. But what we talking about?

    Kind regards

    Hermann
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 09 2016, 11:11 PM - #Permalink
    Hi Ron,

    there must has been a miracle. I just tried to do the uodate, and you know without I've changed nothing in my server configuration, the update was finished and done.

    Thanks

    Hermann
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 09 2016, 11:16 PM - #Permalink
    I'm curious Hermann, who is this Ron you're talking with all the time?
    Is there some posts I don't see, or is it just a new weird way of being rude you have?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, August 09 2016, 11:24 PM - #Permalink
    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
    Like
    1
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 10 2016, 08:45 AM - #Permalink
    Well, I uploaded the files from the 1.3.5 download (excluding install folder) and the update was successful. I'm now on 1.3.5. Thanks guys for all the help. Hopefully the next update works right without having to go through the other steps.
    The reply is currently minimized Show
Your Reply