Can not update and change order status

Hi,

Regarding the update, it's probably because the zip of HikaShop is bigger than AcyMailing or Convert forms. HikaShop has a lot of files so it takes a lot of time for Joomla to extract. If the max execution time limit is too low in your php.ini or you have some other processing restrictions on your server, it's possible for the install to hang like this.
The solution if you can't increase the max execution time, or it comes from something else you don't have access to, is to extract the install package on your local computer, upload all the extracted files and folders to the tmp folder of your website via FTP and use the "install from folder" of the Joomla installer pointing at that folder. That way, the install will directly proceed to the next step, circumventing the processing limitation with the extraction.

Regarding the order status, it's hard to say what the problem is without looking into it. When you change the status of an order, many plugins can be triggered. For example, it could be that you created a mass action with a trigger "after an order is updated" and you made a mistake somewhere which generates an error. And thus, in that case, updating HikaShop won't help.
There are two things you can do to find the issue:
- activate the "debug" setting of the joomla configuration, and try again, while you have the "network" tab of your browser's developer tools open:
www.geeksforgeeks.org/network-tab-in-google-chrome-browser/
With it, you can see what the server respond when you change the status and nothing displays on the screen. In the "response" of the HTTP request, you should be able to see the error message, which will point at the problem. For example, if the problem comes from a mass action, the error message will point at a file of the mass actions system.
- Similarly, the error message will normally be logged by PHP in its PHP error log file. So, if you look in that file, you should be able to get the error message too.

Hi,

In the network tab of the devtools, click on the HTTP request with the 503 error. And open the "response" tab. You will be able to see what your server answered.
With the debug activated, it's possible you'll see the PHP error message there.
If you see a generic message (with no file path), then you'll have to look in the PHP error log for the real error message.