Jump to content

Huge ps_pagenotfound table: possible reasons?


Recommended Posts

Hi,

I discovered through phpmyadmin that the ps_pagenotfound table occupies more than 100 MB whereas the second biggest table occupies less than 5 MB.

Most common solution is to purge the table, but it does not solve the cause of the problem.
Looking at the table, we see that both offices, front and back, are concerned.

Could someone give any clue to identify the reasons, well-known case to study ?
I am not webmaster so I probably made mistakes during the shop deployment. It was first launched on prestashop 1.4 and it is now running on prestashop 1.6.0.9

Regards

Edited by Marbaf (see edit history)
Link to comment
Share on other sites

  • 4 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...