Jump to content

kibiribi

Members
  • Posts

    48
  • Joined

  • Last visited

Profile Information

  • Location
    Ukraine
  • Activity
    Web development agency

Recent Profile Visitors

1,797,998 profile views

kibiribi's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare

Recent Badges

7

Reputation

  1. @Mediacom87 You are the best Idea with clear of cache works fine. I've removed manually files in folders: - var/cache/prod - img/tmp - Backend works fine. P.S. I've got a thought before to clear a cache. I've activated Debug mode and try to clear cache with help of Backend menu - it didn't help me But when I remove all cache file manually - Backend and frontend work smoothly. Thanks again for help and advices!
  2. Thanks for idea about of old cache. I'll try to clear and remove old cache for my new server and update the result.
  3. Thanks for your reply. The main problem - Prestashop worked ok on my old server with PHP 7.2.34 , but when I migrate to another new server with different IP and the same configuration of PHP version - I can't enter BackEnd (error 500). When I activate Debug mode - I can login Backend, FrontEnd shows me a lot of errors. Any workaround how to compare source and target servers to identify problems? May be rights? PHP versions are the same versions. Old server = CentOS, new server = Ubuntu. Does it mean - OS version? PHP versions the same 7.2.34
  4. Hi community! I've got PS 1.7.6.1 and started migration from one server to new one. PHP ver. for my old server = 7.2.34 PHP ver. for my new server = 7.2.34 (was installed for compatibility by me) I've faced with Backend login. Frontend works fine Backend got me 500 error. When I set define('_PS_MODE_DEV_', TRUE); - Backend works good, but frontend shows me a lot of internal errors. But when I change setting to define('_PS_MODE_DEV_', FALSE); BackEnd got an error 500, and Frontend operates good. I tried to change PHP ver. from 7.1.33 to 7.4.33 - situation all the same. I'm afraid to upgrade PS version because of my custom version of the Template. Could you advise - any solution for this ? Is it possible to activate Debug mode only for Backend ? :-) In this case I can run Backend and run FronEnd without debug mode. Thanks for your time and advices!
  5. In general, the problem with blocking the Admin for 500 was described in this post - https://github.com/PrestaShop/PrestaShop/issues/17393 I've changed the ps_linklist module to ps_linklist-old - disabled the module, deleted all the cache in the var / cache / folder - and BackOffice was active and operated. Later I downloaded an old module for ver.1.7.4 - https://github.com/PrestaShop/ps_linklist/tree/v2.1.6 replaced - took _old - and it all worked. In debug mode - no errors occur. Maybe someone can use a solution to this problem - that's why I added the solution.
  6. Good morning! Any idea, how to run PrestaShop BO after error 500 ? 😞
  7. Hello! I've moved PrestaShop ver.1.7.4.4 to new server Frontend works fine. When I try to enter BackEnd - first time. next page goes to 500 server error. Log told me - Got error 'PHP message: PHP Fatal error: "AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Symfony\\Component\\DependencyInjection\\Exception\\ServiceNotFoundException: The service "prestashop.module.link_block.grid.data_factory" has a dependency on a non-existent service "prestashop.core.hook.dispatcher". in /httpdocs/vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php:31\nStack trace:\n#0 " Debug mode told me - " (1/1) ServiceNotFoundException The service "prestashop.module.link_block.grid.data_factory" has a dependency on a non-existent service "prestashop.core.hook.dispatcher". " screenshot - https://prnt.sc/vdjzth I investigated this problem All Cache folders were deleted - /..../httpdocs/var/cache - didn't help PHP version from 7.1.3 to 7.3 changed - didn't help test script shows me that it's ok - https://prnt.sc/vdk1ey Any suggestion how to solve this cache OR Symphony problem during the migration to new server? This is not update - only migration. Thank for your advices in advance 🙂
  8. PrestaShop ver. 1.7.6.8 with default template In the Back-end: When I tried to add product I CAN'T select or view Category tree list in the right vertical sidebar in Yandex Browser. But it works fine with Chrome. Watch video example - https://drive.google.com/file/d/16g31WtwoWz72A4jh-QU-xpgHLm7HpXnw/view?usp=sharing Yandex browser version - https://prnt.sc/v6zq95 Console info shows me this error - https://prnt.sc/v70668 the same browser Yandex worked well with prev. Prestashop version before. Any suggestions?
  9. The same problem with 1 active country when Country field was removed from settings - https://github.com/PrestaShop/PrestaShop/issues/9888 Sounds good, but any workaround for the version 1.7.6.5?
  10. So I don't need all those fields - pic 4 VAT, adr2, Tax, etc... how to remove those fields without error 500 code? 🙂
  11. I want to show only special customer fields for customer registration form (Presta 1.7.6.5): 1) firstname, lastname 2) address, 3) phone it will be online store for 1 city only. I don't need country and ZIP. see pic 1 it looks ok for me - pic 2 But it gives me 500 Error during checkout 😞 According to Debufg mode - problem with country code - pic 3 What should I do in this case? It seems I can't remove country field? In this case use hidden field country with value ="country code " for user registration form and set my country everytime? ------- example for CSS hide -------- --- this code hide all address block --- .js-address-form .form-fields > .form-group.row{display:none;} ---- - this code hide only country row --- .js-address-form .form-fields > .form-group.row.id_country {display:none;} -------------------------------------------------- Thanks in advance for advices 🙂
  12. sure, this problem was resolved - Execution time change + more time and Browser Cache clear Thanks for advices. It'll be nice to add such hint in installation wizard - "Please note: Clear your browser cache if server option was changed and you'll install again."
  13. Thanks, you are right! But the main problem for this case - I had to clear browser cache. Max execution time was changed, but installation didn't finished every time. Prestashop didn't mention about cache clearing fix 🙂
  14. Honestly... I would never have thought of clearing the cache :-) Installation finished without problem ! Thanks again for your advice! It's not clear for me which way caching method stops installation? :-( The request is closed.
×
×
  • Create New...