Don’t remove any files within the root directory. You want to be checking the var folder. So, change directory to var and run ls -la. Or just run ls -la var from the Magento root directory.
That’s what I’ve got. So I presume I should delete the .update_in_progress.flag. Or all of the files connected to update? Because the maintenance mode was activated by me and I’d like to keep it this way.
Remove .update_in_progress.flag and you should be good to go. The file doesn’t contain any information. It’s simply a “flag” just like the .maintenance.flag file.
Let me know how you get on. I’ll check back in later.
So, removing the flag worked. I’ve decided to try the web setup wizard one more time and it appears I have slightly different problem this time.
When I try to enter either front or back end I get the message: An error has happened during application run. See exception log for details. Could not write error message to log. Please use developer mode to see the message.
I did delete the flag again as I had thought it may have been the issue but it is not. Also I’ve tried to find the solution and all I found was to comment out (not sure if it means to delete?) the # SetEnv MAGE_MODE developerfrom .htaccess file. but it didn’t do anything.
Did you go into Developer Mode as it suggests? In this mode, you’ll be presented with the error message directly in the browser. I wouldn’t mess with .htaccess until you check that first.
Looks like you’re taking the Documentation too literally. “{}” and “” refer to placeholder examples. Therefore, you don’t actually use it in the command. Like “My name is {name}. I live in [city]”.
Also, bin/magento commands need to be ran as the “magento” user. So, you never prefix the command with sudo. Also, you shouldn’t need to prefix your command with ‘php’ either, unless you have an old PHP setup.
If you read a little further down the Documentation, you’ll see the command would actually be:
bin/magento deploy:mode:set developer
And if you want to switch to developer mode and skip compilation then you’d use:
bin/magento deploy:mode:set developer -s
Hopefully, that helps explain the way the Documentation is written.
Change to developer mode
When you change from production to developer mode, you should clear generated classes and Object Manager entities like proxies to prevent unexpected errors. After doing so, you can change modes. Use the following steps:
If you’re changing from production mode to developer mode, delete the contents of the generated/code and generated/metadata directories:
This is probably connected to all the permission issues I run into earlier when trying to install a template. So can I do this with super user or will it not work at all?
Your original post was about having problems upgrading from 2.3.0 to 2.3.1 in May. If your original post is solved, you should consider starting a new one. It’s getting a bit confusing and hard to follow.
Also, you already reported the issue with “No such file or directory” in this post: Magento backup problem
Yea, that’s correct. Sorry about that, I have had few breaks from doing anything and I just forgot about that. I used the tips you gave me there and Magento is working for me again.
That’s also true. This time I will try to update via CLI as the Web Setup Wizard is clearly not working for me. Also I’ve just noticed that there is even newer version, 2.3.2. Should I go for this?
Anyway, thanks so much for your help. I will try to keep thing more organised from now on. I will let you know how did the update go
No problem. Sorry if I sound anal. This forum works best when it’s presented in a way that helps other people who stumble across the same problem, not just the Original Poster.
I’d give 2.3.2 a couple of weeks before upgrading. This way if anyone runs into any bugs with the update, it allows time for people to fix them. Don’t wait longer than a month though
Hi. Coming back to the thread. I’ve just finished updating Magento via CLI using your tutorial (although it was 2.2.8 to 2.3.1 I figured it should still work).
So it seemed to me that everything was just fine but when checking for new update in Web Setup Wizard it shows me I still got 2.3.0 and can update to 2.3.2.
Did I do something wrong or does it not show the current version properly?
Those instructions are to get from 2.2 to 2.3, which is a big upgrade requiring a lot of instructions.
The small ones are far simpler to do (e.g. 2.3.0 to 2.3.2). Just follow the steps listed in the Official Magento Documentation. It shouldn’t take much longer than 5 minutes because there aren’t many steps.
Ok, so I followed the instructions and succesfully updated Magento to the newest version.
Thanks for your help and patience also expect more problems coming up