Jump to content

MarcoGiuliani

New Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MarcoGiuliani's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Have you delete all files in prestashop folder from ftp before restore backup? Because the restore don't delete them (only rewrite). If the problem is in an old file or a file not in the backup the restore don't delete it.
  2. Before update go to phpMyAdmin and try to convert DB to utf8mb4. If some field fails the conversion try to allow Null value on that field and try to convert this field again. Then delete all Prestashop files from FTP before restore your backup. When DB use utf8mb4 Prestashop upgrade should go right.
  3. Già provato... Quando copio la cartella le mail vengono trovate. Ma se faccio una modifica viene spedita la vecchia versione non modificata.
  4. Allora, Io ho solo l'italiano attivo, cerco la traduzione delle mail sotto traduzioni>traduzioni mail (contenuto|nucleo|italiano) Prestashop sembra cercare le core mail nella cartella /mails/it ma in realtà le cerca in mail/en (vedi immagine) dando errore e trovando 0 core emails perché mails/en non esiste. Se creo mail/en smette di dare errore e trova le oltre 60 core mails, ma quando ne modifico una viene spedita la vecchia versione non modificata. Dato che Prestashop cerca le mail in /en anche se ho chiesto le traduzioni in italiano immagino che leghi la mia modifica alla mail inglese, poi quando spedisce manda quella in italiano non modificata.
  5. Hi, I've Prestashop 1.7.7.0 Languages activated: Only Italian When I go to translation>email translation (body, core, Italian) Prestashop search core mails in root/mails/en instead of root/mails/it Obviously /en folder doesn't exist and Prestashop tells me: "C'è un problema nel ricevere il file di posta. La lingua inglese deve esistere nella cartella /home/wafqewqk/domains/adomedical.it/public_html/mails/en/" If I create /en/ folder with emails and modify one Italian email Prestashop send older version. I think he took my change in en (not in it) and send it version. Does anyone know how to solve this?
  6. My problem was on DB. In this upgrade Prestashop try to convert DB fields from utf-8 to utf8mb4. In one field this conversion failed. I did manual conversion on DB from phpMyAdmin (to convert that field I allow Null value) and then successfully repeat Prestashop upgrade.
  7. Hi! Trying to update prestashop I had error 500 only in backend. Frontend seems to work. I restored my previous server backup but error still exist. DEBUG: (1/3) ParseException The constant "\PrestaShop\PrestaShop\Adapter\News\NewsDataProvider::CLOSED_ALLOWED_FAILURES" is not defined at line 10 (near "- !php/const \PrestaShop\PrestaShop\Adapter\News\NewsDataProvider::CLOSED_ALLOWED_FAILURES"). (2/3) InvalidArgumentException The file "/(...)/public_html/src/PrestaShopBundle/Resources/config/services/adapter/news.yml" does not contain valid YAML: The constant "\PrestaShop\PrestaShop\Adapter\News\NewsDataProvider::CLOSED_ALLOWED_FAILURES" is not defined at line 10 (near "- !php/const \PrestaShop\PrestaShop\Adapter\News\NewsDataProvider::CLOSED_ALLOWED_FAILURES"). (3/3) FileLoaderLoadException The file "/(...)/public_html/src/PrestaShopBundle/Resources/config/services/adapter/news.yml" does not contain valid YAML: The constant "\PrestaShop\PrestaShop\Adapter\News\NewsDataProvider::CLOSED_ALLOWED_FAILURES" is not defined at line 10 (near "- !php/const \PrestaShop\PrestaShop\Adapter\News\NewsDataProvider::CLOSED_ALLOWED_FAILURES") in /(...)/public_html/src/PrestaShopBundle/Resources/config/services/adapter/news.yml (which is being imported from "/(...)/public_html/src/PrestaShopBundle/Resources/config/services.yml"). Some help? Thanks a lot!
×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More