Major Bob

Over 6 months later I still haven't solved this problem. The products are set to online and visible everywhere. Has anyone else experienced this or can anyone provide a hint on how to solve my issue?

I've made several products in the back office and via CSV uploads. None of them are present in the front end. Everything is correct in the back office and they are set to be displayed. The products are allocated to categories in the front end but they're only visible if you search for them. i.e. not by browsing the categories from the menu. Has anybody got any ideas?

This worked for me as well. Thank you, thank you, thank you.

Can anybody provide a work around for this issue? Does anybody know which files to edit manually?

I've upgraded my store to 1.7.0.0 and tried to upload the exact same csv files again. All files were uploaded quickly and correctly, so the problem was mostly with the uploading process in the 1.6 back office. On a side-note, there is a progress bar in 1.7 that shows the status of the upload and an email is sent to confirm that uploading is complete. Great improvement

I've made several products in the back office and via CSV uploads. None of them are showing up in the categories in the front-end. Everything is correct in the back office and they are set to be displayed. The products are allocated to categories in the front end but the only places they are visible is in 'popular products' on the home page and if you search for them. Has anybody seen this before? Debugging on one of the category pages displays this: [PrestaShopDatabaseException]Access denied for user 'xxx' to database 'yyy' CREATE TEMPORARY TABLE ps_cat_restriction ENGINE=MEMORY SELECT DISTINCT cp.id_product, p.id_manufacturer, product_shop.condition, p.weight FROM ps_category c STRAIGHT_JOIN ps_category_product cp ON (c.id_category = cp.id_category AND c.nleft >= 153 AND c.nright <= 162 AND c.active = 1) STRAIGHT_JOIN ps_product_shop product_shop ON (product_shop.id_product = cp.id_product AND product_shop.id_shop = 1) STRAIGHT_JOIN ps_product p ON (p.id_product=cp.id_product) WHERE product_shop.`active` = 1 AND product_shop.`visibility` IN ("both", "catalog") at line 744 in file classes/db/Db.php 739. if ($webservice_call && $errno) {740. $dbg = debug_backtrace();741. WebserviceRequest::getInstance()->setError(500, '[SQL Error] '.$this->getMsgError().'. From '.(isset($dbg[3]['class']) ? $dbg[3]['class'] : '').'->'.$dbg[3]['function'].'() Query was : '.$sql, 97);742. } elseif (_PS_DEBUG_SQL_ && $errno && !defined('PS_INSTALLATION_IN_PROGRESS')) {743. if ($sql) {744. throw new PrestaShopDatabaseException($this->getMsgError().'<br /><br /><pre>'.$sql.'</pre>');745. }746. 747. throw new PrestaShopDatabaseException($this->getMsgError());748. }749. } DbCore->displayError - [line 378 - classes/db/Db.php] - [1 Arguments] DbCore->query - [line 554 - classes/db/Db.php] - [1 Arguments] DbCore->execute - [line 1654 - modules/ps_facetedsearch/ps_facetedsearch.php] - [2 Arguments] Ps_Facetedsearch->getFilterBlock - [line 37 - modules/ps_facetedsearch/src/Ps_FacetedsearchProductSearchProvider.php] - [2 Arguments] Ps_FacetedsearchProductSearchProvider->getFacetCollectionFromEncodedFacets - [line 143 - modules/ps_facetedsearch/src/Ps_FacetedsearchProductSearchProvider.php] - [1 Arguments] Ps_FacetedsearchProductSearchProvider->runQuery - [line 314 - classes/controller/ProductListingFrontController.php] - [2 Arguments] ProductListingFrontControllerCore->getProductSearchVariables - [line 499 - classes/controller/ProductListingFrontController.php] ProductListingFrontControllerCore->doProductSearch - [line 86 - controllers/front/listing/CategoryController.php] - [2 Arguments] CategoryControllerCore->init - [line 182 - classes/controller/Controller.php] ControllerCore->run - [line 366 - classes/Dispatcher.php] DispatcherCore->dispatch - [line 28 - index.php]

I'm having this problem with many different translations. Any suggestions would be very welcome

Hi Luca, It's on Apache

This is a great solution that I used for Prestashop 1.6. Unfortunately, after upgrading to 1.7, the code doesn't appear to work anymore. I hope that there will be a solution for the future that works with 1.7

After a LOT of trial and error and troubleshooting, my host has realised that there is a set limit restricting timeouts to 300 seconds. However, they are adamant that this should be plenty of time and that there is an underlying issue with the Prestashop import process.

Thank you Andrej for your correct answer and your in-depth explanation. I'm sure that it will help many people who use 1.7. You are also correct that there is no longer a cms block module or access from the back-office to change this text. I searched all of the theme files and module files to find where to make the changes but I couldn't find it without your help. I didn't want the link in the text or the 'ecommerce by' text so I changed the code from this: <p> <a class="_blank" href="http://www.prestashop.com" target="_blank"> {l s='%copyright% %year% - Ecommerce software by %prestashop%' sprintf=['%prestashop%' => 'PrestaShop™', '%year%' => 'Y'|date, '%copyright%' => '©'] d='Shop.Theme'} </a> </p> To this: <p style="font-size:79%;"> {l s='%copyright% %year% - %prestashop%' sprintf=['%prestashop%' => 'My company. All rights reserved | Company info', '%year%' => 'Y'|date, '%copyright%' => '©'] d='Shop.Theme'} </p> This isn't as flexible as your solution for the future but it suits my site better. Besides, the translations don't work properly at the moment but that's a matter for another topic.

I would like to edit the link at the bottom of the footer (© 2016 - Ecommerce software by PrestaShop™). As much as I like to give credit to PrestaShop, it doesn't look as professional as if I put my own company information in this space. I have edited it in previous versions but can't find the correct file or translation in the back office. Can anyone tell me the correct way to change it?

PayPal is definitely a must have module for many shop owners. I look forward to it being available for 1.7

I'm also having this problem

That's a good idea. I've written a similar script and run it multiple times over varying sleep lengths to see what's going on. The script only finished in 5 cases out of 14 but the results showed that it didn't begin when I executed it, there was a delay before the script actually began(up to 215 seconds in one case). In the other 9 cases, the script appeared to run for over 900 seconds in each case before eventually showing 'The connection has reset' error. As it's not timing out at 300 seconds as before, I believe that Prestashop is at fault for the 300 second limit (rather than the server). There is obviously a delay before my script begins though and I think that this is shortening the 300s time limit imposed by Prestashop. Now I know a little bit more about the cause, but I have 2 problems instead of one.