Jump to content

Cache clear causes 500 error after update to 1.7.8.1


Recommended Posts

Hi Everyone,

We had a fresh install of 1.7.8.0 which was working fine.  We upgraded to 1.7.8.1 and since the upgrade each time we clear cache under performance we get 500 errors until we manually delete the cache under var/cache.  Any ideas what may have changed to cause this?  Thanks

Link to comment
Share on other sites

Interesting... it appears to be related to our clean urls module.  We've contacted the developer.  Thanks!

 

Dispatcher::createUrl() miss required parameter "categories" for route "category_rule"
at line 923 in file classes/Dispatcher.php

918. if (!$data['required']) { 919. continue; 920. } 921. 922. if (!array_key_exists($key, $params)) { 923. throw new PrestaShopException('Dispatcher::createUrl() miss required parameter "' . $key . '" for route "' . $route_id . '"'); 924. } 925. if (isset($this->default_routes[$route_id])) { 926. $query_params[$this->default_routes[$route_id]['keywords'][$key]['param']] = $params[$key]; 927. } 928. }

Link to comment
Share on other sites

Just an FYI on what we discovered.

When clearing cache in debug mode or prod, prestashop seems to be creating de_ and dev folders or pro_ and prod folders in var/cache. Once both of the folders are created, that's when the 500 error occurs. If we manually delete both these folders(in debug or prod) and then access a web page, only the dev or prod folders get created (not the de_ or pro_) and everything works fine in both debug and prod mode. It looks like the second (we assume) temp folder with the _ that gets created messes things up upon clearing cache.

 

Is anyone else experiencing this for 1.7.8.1? 

Link to comment
Share on other sites

Also interestingly enough.. 

if we delete the non _ folder, then everything works fine and it actually recreates the non _ folder again.  If we delete the _ folder, things don't fix... it's only when we delete the folder that doesn't contain the underscore and then access a webpage for it to be recreated is our shop fine again... so based on this information, it likely doesn't have anything to do with both folders being created, just a conflict in the non _ folder.  

Why is this so complicated?

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

  • 2 years 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...