Jump to content


  • Content count

  • Joined

  • Last visited

About peter4661

  • Rank
    PrestaShop Apprentice

Profile Information

  • Location
  • Activity

Recent Profile Visitors

7,779,493 profile views
  1. After weeks of struggle trying to pgrade, we decided to install fresh second PS and migrated old to new with help of MigrationPro module . Worked like sharm.
  2. Recently we upgrated Prestashop 1.6.x to In finishing the installation we regerated .htaccess and robots.txt through the backoffice. When visitors to the site continue to drop we started the search for potential cause, With Google webmaster tools, search console / crawl, using Google robots.txt tester reported All URL Blocked !! Fresh backoffice generated robots.txt contained no follow instruction for the whole site: Disallow: */ Looking further Googlebot type: Desktop (render requested) robots.txt it also blocked access to two folders for search engines to render the site properly: Disallow: */css/ and Disallow: */js/ It is adviced to check, your robots.txt when fresh regenerate from your backoffice. Could reproduce this behaviour. Bug report generated.
  3. we were on PS and tried to update with 1 click upgrade, initial with failures. Here is how we worked around. We had to go expert mode, module could not find updates beyound 1st attempt: with create full backup. Result: ErrorThrown:"Internal Server Error " jqXHR: While our server makes full backup every hour, we deceided to update without backup through 1 click upgrade 2 nd attempt: update proccess reported OK. 500 error in front and backoffice. restore backup from server throught server admin panel. 3 third attempt to upgrade. under Advanced settings, Performance tab: disabled all non native Prestashop modules, disabled all overwrites, disable cache. Now update through expert mode. Update process reported O.K. Check front: Worked O.K. Check backoffice: access to, edit and save orders, custumers, products O.K. Visit backoffice module folder : result white screen, error in Prestashop app dashacitivity. Action: FTP, copy folder to local hard disk en removed folder daskactivity. re-visit modules folder: result white screen, error in Prestashop app dashgoals. Action: FTP, copy folder to local hard disk en removed folder dashgoals. Re-visit modules folder: result white screen........ We repeated this process of visiting backoffice modules folder and deleting FTP the module which caused a problem. After this PS ran smooth. Then enabled non native Prestashop modules and enabled overwrites. To cut a long story short: We repeated this process of visiting backoffice modules folder and deleting FTP the module which caused a problem. After this PS ran smooth. We found alle Prestashop (3) native dash modules, (23) native stats modules and (3) non Prestashop native modules created error. We assume non compatibility with 1.7.1, did not investigate further, will try to get 1.7.1 compatible versions of the modules. Attached: screenshot of found incompatible modules.
  4. Dear all, Since weeks i'm trying to to figure out why our product pages in Google cache are without style. Suggestions are welcome Peter I came across this issue while trying to publishing a page set with Google Data Highlighter. example of product page in google cache https://webcache.googleusercontent.com/search?q=cache:8iNZgWOEiZgJ:https://www.derks-wielersport.nl/kettingen/kmc-ketting-11-speed-x11el-silver.html+&cd=5&hl=nl&ct=clnk&gl=nl page in front office: https://www.derks-wielersport.nl/kettingen/kmc-ketting-11-speed-x11el-silver.html
  5. We use app Store Manager for test to edit PS backoffice ( PS After editing/save an product, this product appears multiple time in PS backoffice with the same product ID. Every time a product is edited, an additional line is added / visible in PS backoffice. See example: http://screencast.com/t/PLt0Ym3ukS1q Checking the database there is only one line for subject product ID. The product is only one time visible in front office. We contacted the developer of Store Manager and shared with him the details. Developer believes this an PS issue. Is there anyone who has simular experiense? And / or knows the solution to this problem? Thank you for taking the time to respond, Peter
  6. CSV export file verminkt

    Met tekt editer ziet de file er uit als getoond in 't linkje.
  7. CSV export file verminkt

    Hallo medestrijders, Wij werken met PS Wij lopen tegen volgend probleem. CSV export functie genereert een CSV file. Als we die importeren in een speadsheet programma dan lijkt de inhoud op een tekenreeks op een pyramide. Zie bijgaand screenshot: http://screencast.com/t/gjs7WT9dBc Heb gezocht op het engels forum maar kom daar geen aanknopingspunten tegen. Heeft iemand ervaring met het aanpakken van dit probleem? We hebben de export functie nog niet eerder gebruikt. Grt, Peter
  8. PDF invoice disappeared

    I would like to pick up on this topic. After modification of an order to admin side (added product) PDF orders and delivery notes can not be printed. Reporting to print attempt PDF document can not be opened. In debug mode "true",ini_set ('display_errors', 'on'); no error message. Do not have enough in-house expertise to tackle a problem. On the English forum there are some indications for database error without concrete steps that could lead to solutions. Who knows advice? Any help is welcome, We are at PS version Peter
  9. PDF wil niet openen

    Ik wil graag inhaken op dit onderwerp. Na aanpassing van een order aan admin zijde ( product toegevoegd ) kunnen PDF orders en pakbonnen niet meer worden geprint. Melding bij print poging: PDF document kan niet worden geopend. In debug mode "true", @ini_set('display_errors', 'on'); geen foutmelding. Helaas onvoldoende kennis in huis om probleem te tackelen. Op engels forum zijn er wat aanwijzingen richting database fout zonder concrete stappen die zouden kunnen leiden tot oplossing. Wie weet raad? Alle hulp is welkom, Wij zitten op PS versie Peter
  10. We also experienced slow BO, This helped in our situation: https://github.com/PrestaShop/PrestaShop/commit/7e891c594e3cc8b48aea0a57ed674189abc19493 Good luck, Peter
  11. Hi El Patron, Bought your Bozoom module. It improved backoffice speed for items which are cached and cut loading by approx 50% ( results by Chrome webmaster tools ) On product on edit however it still takes ~ 30 seconds to load. The slow rendering items are the product tabs jquery-1.11.0.min.js:4 ( not from cache) . See example: http://screencast.com/t/kOUhWvWs We have warning at the bottom of the screen using Chrome webmaster tools. I do not understand what this means. Can you elaborate on this? Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help jquery-1.11.0.min.js:4. check http://xhr.spec.whatwg.org/. VM2596:2 'webkitMovementX' is deprecated. Please use 'movementX' instead. Additional observation. After we re-indexed the site. Backoffice speed was terrible slow ( load product for edit in 3 minuts or so, was 30 seconds) Cleared smarty cache and rebuilding cache. Wait and see if this will get backoffice up to speed again.
  12. Backoffice slow, front O.K. On trying to identify / troubleshooting really slow request: On editing a product ( loading time 8 minuts, really bad example ) using Google Chrome developer tabs, you get the url by name. see http://screencast.com/t/1Y3jLF02 Really slow request, loading product tabs; price, associations, shipping, quantities, suppliers, ect... Looking into the details for each request most of the time spent is waiting time . Found this explaination: waiting TTBF: Time spent waiting for the initial response, also known as the Time To First Byte. This time captures the latency of a round trip to the server in addition to the time spent waiting for the server to deliver the response. see example http://screencast.com/t/4nLvh2jhzzg Now we know this question comes up : is this a server thing ( qwe are on shared server ) or something else? Peter
  13. We also observe slow back office after upgrading from to implemented Github modification for smarty.config.inc.php No improvements. After enabling debug error warning, we get error warming below. Al suggestions are welcome, Peter Notice op lijn 509 in bestand /home/wieler/domains/derks-wielersport.nl/public_html/cache/smarty/compile/93/f8/9b/93f89b985c5757f5ce176088979b54f2c97989e9.file.header.tpl.php [8] Undefined index: current_version Notice op lijn 509 in bestand /home/wieler/domains/derks-wielersport.nl/public_html/cache/smarty/compile/93/f8/9b/93f89b985c5757f5ce176088979b54f2c97989e9.file.header.tpl.php [8] Trying to get property of non-object We did put backup back. Error warning is gone now, be backoffice remains slow. Product edit takes 90 seconds to load and up to 50 seconds to save.
  14. PS 1.6.1 Klant / admin kan adres niet aanpassen

    Hoi MDekker, dank voor je reactie Nog wat testen gedaan. Klantzijde PS biedt de klant mogelijkheid om verzendadres te wijzigen, wissen of toe te voegen. Dat blijkt deels niet te werken. We kunnen bestaand verzendadres niet aanpassen, noch verwijderen. Wel een nieuw verzendadres toevoegen. In debug mode geen foutmelding. Dit lijkt op een bug... Admin zijde Verzendadres / factuur adres zijn aan te passen. De wijziging wordt op de pakbon weergegeven, niet op de factuur. Lijkt hier niet correct te werken. In debug mode geen foutmedling. Lijkt op niet correcte werking van PS. We melden 't als bug, Groet, Peter
  15. Goeie middag PS gebruikers. Van een klant kregen we de melding dat hij achteraf het verzendadres niet kon aanpassen. Toe we vanuit backoffice zelf probeerde het adres aan te passen lukte dit wel. Tenminste als getoond in backoffice. Bij het afdrukken van de factuur stond daar nog de oude informatie. Cache geleegd, template geforceerd. Mocht niet baten. Gewijzigde adressen als te zien in backoffice worden niet getoond op de factuur. Is dit een bug? Peter