Solved EasyStore

404 Not Found messages in Easystore Product Editor

Asked by Bruce Paine 5 months ago Last activity 5 months ago

SP Page Builder Pro: 5.x (Latest Version)
Site template: Allura
EasyStore: Latest Version
Environment: Hosted Dev Site
Joomla 5.4.3
EasyStore 1.7.7
PHP 8.3.+

Hi Joomshaper Support Team,

I used Akeeba backup to transfer my local Joomla development site (MAMP environment) to a live dev server.

The installation went well and most things are working properly.

However, I have discovered the following:

When editing Easystore Products, there are 404 Not Found messages appearing next to the EasyStore panels (Images, Product Options, Upsells, Cross-sells, etc.)

Otherwise the main product form loads correctly and, so far, I am still able to edit the content successfully, including upload of images and saving.

So it seems like something innocuous going on in the background.

I have investigated and checked everything that is within my capabilities but without resolving the issue.

Can you please advise regarding any possible causes?

Please refer to screen shots I have provided.

Kind regards,

Bruce

Accepted answer

Marked as the solution

Atick Eashrak Shuvo Staff

5 months ago

Thank you for the update—I'm glad to hear the issue has been resolved.

Regarding your question, this is not something we typically include in the Easystore hosting setup instructions. In our experience, this type of issue is not common and appears to be related to a specific ModSecurity rule configured on your hosting environment rather than a general setup concern.

If it were a widely triggered or standard ModSecurity rule, we would expect to see similar reports from other users, which has not been the case so far. That said, we do appreciate you sharing this information, as it may be helpful in identifying edge cases in certain hosting configurations.

Please feel free to reach out if you encounter any further issues.

16 more replies

Bruce Paine Asked this

5 months ago

An update on this issue.

The 404s are appearing in other edit windows e.g. Brands.

Atick Eashrak Shuvo Staff

5 months ago

Hi there!

Thank you for bringing this to our attention, and I sincerely apologize for the inconvenience caused.

To assist you more effectively, may I kindly request temporary administrative access to your site? This will allow me to thoroughly investigate and resolve the issue for you.

Before sharing the credentials, I strongly recommend taking a complete backup of your site to ensure all data remains secure.

Looking forward to your response.

Best regards

Bruce Paine Asked this

5 months ago

Certainly!

Here is the temporary login.

I have taken a new backup.

I look forward to hearing what you discover.

Thank you!

Atick Eashrak Shuvo Staff

5 months ago

Please share your site url

Bruce Paine Asked this

5 months ago · edited

My apologies!

Here it is...

Atick Eashrak Shuvo Staff

5 months ago

Your administrator link showing 404 error https://prnt.sc/UmMoQGRgB4Eo

Bruce Paine Asked this

5 months ago

Sorry - we have IP restriction on the administrator.

I have removed it. Please try again.

Bruce Paine Asked this

5 months ago

In case you missed my edited reply...

I have removed IP restriction on the administrator.

Atick Eashrak Shuvo Staff

5 months ago

Can i take a full backup of your site to check the issue in my local machine?

Bruce Paine Asked this

5 months ago

Yes you can, if it helps and so long as you delete it afterwards.

Atick Eashrak Shuvo Staff

5 months ago

Apologies for the delayed response over the weekend.

I was unable to reproduce the issue on my local environment, which suggests this may be server-specific. Could you please confirm the exact steps you followed when migrating the site from localhost to the live server?

Bruce Paine Asked this

5 months ago

Thanks for your reply.

The migration process was as follows:

The site was developed locally using MAMP.
I created a full site backup using Akeeba Backup.
The backup was restored on the live development server using Akeeba Kickstart (kickstart.php).
During restoration, I followed the standard Akeeba steps, including updating database and path configuration.
After restoration, I confirmed that:
- The frontend loads correctly
- Joomla administrator login works
- EasyStore product editing and image uploads function normally

However, within the EasyStore product edit screen, several sections (Product Options, Upsells, Cross-sells, Additional Data, etc.) display 404 error messages.

These errors appear beside the controls in those sections, while the main product details area works as expected.

I have already tried:

Clearing Joomla cache
Disabling SEF URLs
Restoring the default .htaccess configuration
Ensuring debug mode is off
Removing administrator folder protection (temporarily)

The issue remains unchanged.

As the main functionality is working but these sections consistently show 404 errors, it seems specific to how those parts of EasyStore are loading in this environment.

Could you please advise:

Whether any post-migration steps are required for EasyStore after restoring with Akeeba?
Whether there are any known server configuration requirements that could affect these sections?
I’m happy to provide screenshots or further details if needed.

I should also note that these 404 errors do not occur in the original MAMP local installation. The EasyStore product edit screen displays normally there, with no error messages in those sections.

Atick Eashrak Shuvo Staff

5 months ago

Can you share your server access?

Bruce Paine Asked this

5 months ago

Sorry I cannot share access easily. However, I am contacting my hosting company support team for their assistance. The hosting plan has some limitations that may be causing this issue or might be part of the problem. I will let you know what they say.

Bruce Paine Asked this

5 months ago · edited

Good news! The hosting company observed some ModSecurity rules being triggered by the site. They have now whitelisted these rules from being triggered and there are no longer any 404 errors appearing.

I hope this is useful information.

Do you think this is something that needs to be mentioned for Easystore hosting setup instructions?

Thank you for your efforts even though this turned out to be a hosting settings issue.

Bruce Paine Asked this

5 months ago

That's fair enough thanks. It seems that my hosting provider is running a stricter-than-average security setup which lead to some false positives. Fortunately they were quick to respond and whitelist the triggered ModSecurity rules.

With my limited understanding it just looked like a problem with Easystore and I have spent many hours trying to find a solution. Even so, it has helped me gain a better appreciation of the relationship between Apache, Security rules, error handling and Joomla.

Atick Eashrak Shuvo Staff

5 months ago

Thank you for the update, and I really appreciate the detailed feedback.

You’re absolutely right—this kind of issue is often caused by a stricter ModSecurity configuration at the hosting level, which can occasionally lead to false positives depending on the rule set in use. It’s good to hear that your provider was able to respond quickly and whitelist the affected rules.

I also understand how this initially appeared from the Easystore side. These types of server-level security behaviors can sometimes surface as application issues, even when the application itself is functioning correctly. Your experience is a great example of how multiple layers (Apache, ModSecurity, PHP, and Joomla) interact, and how tricky it can be to isolate the root cause.

I’m glad the situation also gave you a better understanding of the underlying stack—that insight will definitely be useful for future troubleshooting.

If you run into anything else or need further clarification, feel free to reach out anytime.