Jump to content

nicoledesignstore

Members
  • Posts

    51
  • Joined

  • Last visited

Profile Information

  • Location
    Italy
  • Activity
    Other

Recent Profile Visitors

3,885,544 profile views

nicoledesignstore's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Ciao a tutti, Come da titolo, mi chiedevo se esistesse un modo per mantenere valida la password dei clienti prestashop durante la migrazione a una nuova installazione del cms. Ho migrato con successo (manualmente) l'intero database nella mia sandbox e l'unico "problema" per cui mi ritrovo nei guai è la password di quesi clienti la cui registrazione è avvenuta dopo l'aggiornamento alla 1.6, che sono crittografati con cookie_key, cookie_iv, new_cookie_key o segreto, uno dei i valori in setting.inc o parameters.php. Grazie per qualsiasi contributo! Buona giornata!
  2. Hi everyone, As per Title, I was wondering if there was a way to maintain prestashop customers password alive while migrating to a fresh install of the cms. I have successfully migrated (manually) the whole database in my sandbox and the only "issue" I find myself in trouble with is customers password which sign up happened after upgrading to 1.6 which are encrypted with cookie_key, cookie_iv, new_cookie_key or secret, one of the values in setting.inc or parameters.php. Thanks for any contribution! Enjoy your day!
  3. Hi, thanks for your feedback. So, in you opinion, I'll better start trying a customization from the classic theme instead of presta-rocket, or you actually meant you have used presta rocket as a solid base for each of your in-house developed customizations? I came from a heavy Apollo personalization framework and my website scores a 34 and 85, so I am in trouble with google still I would like to maintain a good level of personalization. My skills bettered last couple of years and the objective is to create a personally tailor made theme.
  4. That's a rocket, I get 97 and 94, and you are even implementing rounded graphical elements as the trend is pushing all of us forward. Wider and nicer, Yet minimal, without shadows or textures. I like it much more. Great job! Scheduled release?
  5. Hi @cyssoo, have you managed to implement the team ever fidelite module? Please let me know and thanks for your attention
  6. Hi! Following the previous comments to the topic, I wanted to ask if someone managed to obtain the same issues I hereby expose: I am basically deciding on which theme base a personalized version for my webshop, so I installed a fresh 1.7.7.4 and tested the page speed insights on both the regular Classic 1.0.0 theme and PrestaRocket 3.1.1.0 (compatible with 1.7.7.x) and I have obtained a 97/98 score on the classic and a disappointing 74/96 on the Rocket. Am I doing something wrong or certain improvements have been taken into account on the classic PrestaShop that managed to beat in performances PrestaRocket optimized theme? Any Clue? Thanks!
  7. [SOLVED] After posting the problem also on stackoverflow I was made to notice that the error message clearly referred to a field regulated in the database by a VARCHAR of up to 32 characters including spaces which appeared to be populated in excess. Found the field, reduced the content from 35 to 29 characters and this error was resolved, allowing me to reach completion of the update. In any case, given the excess of errors from previous installation (database and prestashop are carried out, without reset, since 2013), I connected the database updated to 1.7 to a fresh install 1.7. I currently have permissions problems on this new database, but this specific issue has been fixed.
  8. Ciao @fedesib [RISOLTO] Dopo aver postato il problema anche su stackoverflow mi è stato fatto notate che chiaramente il messaggio d'errore rimandava ad un campo regolato in database da un VARCHAR di massimo 32 caratteri spazi inclusi che si presentava popolato in eccesso. Trovato il campo, ridotto il contenuto da 35 a 29 caratteri e questo errore si è risolto, permettendomi di raggiungere il compimento dell'aggiornamento. In ogni caso, data l'eccedenza di errori da precedente installazione (database e prestashop vengono portati avanti, senza reset, dal 2013), ho collegato il database aggiornato alla 1.7 ad una fresh install 1.7. Attualmente ho dei problemi di permessi su tale nuovo database, ma questo problema è stato risolto.
  9. Ciao @fedesib, grazie mille per il feedback! Il problema con la migrazione è che ho dei contenuti generati da alcuni moduli non nativi, quali le carte di credito, le recensioni ed i punti fedeltà, che speravo di mantenere, mentre sia moduli di migrazione da marketplace che la migrazione vera e propria mi pare di capire non siano in grado includere esattamente tutti i dati, ma solo quelli salienti. Inoltre, con la migrazione, i clienti sarebbero costretti a rigenerare le password, mentre con l'aggiornamento no. Starei cercando di mantenere una certa continuità il più possibile, essendo questo database originariamente un PS 1.4, poi aggiornato a 1.6 e ora da portare ad 1.7. Faccio ancora qualche tentativo, magari iniziando da capo con la disinstallazione di quasi tutti i moduli non nativi e lo spostamento a nuovo installer 1.6.1.24. Se ho aggiornamenti in positivo, aggiorno direttamente qui, altrimenti spero qualcuno possa aver riscontrato errori simili e fornirmi qualche indicazione su come risolversi. a presto!
  10. Ciao a tutti, Sto aggiornando in sandbox una copia del mio sito web prestashop live in MAMP (gratuito) seguendo questa iterazione: - il mio sito web è su 1.6.1.3 - Eseguo un aggiornamento da 1.6.1.3 a 1.6.1.24 con modulo aggiornamento in 1 clic e tutto va liscio, quindi cambio in MAMP il php da 5.6.40 a 7.1.33 e proseguo la disinstallazione e l'eliminazione (in questo ordine) di tutti i moduli e temi non nativi eccetto revws e payplug - Installo, in una diversa directory di htdocs e in un diverso database, un prestashop 1.6.1.24 e copio manualmente al suo interno i moduli revws e payplug, la cartella img e il file di impostazione - Cancello la directory 1.6.1.3 aggiornata a 1.6.1.24 e il database della nuova appena effettuata installazione 1.6.1.24 e collego, per mezzo di una copia del file settings, la directory prestashop 1.6.1.24 di questa nuova installazione al database dell'installazione 1.6.1.3 aggiornato a 1.6.1.24 e modifico la directory della nuova installazione 1.6.1.24 affinché combaci con quella originariamente aggiornata e che ora è stata cancellata - Quindi mi ritrovo con una nuova installazione di prestashop collegata al mio precedente database storico completo - In tutto questo processo ho mantenuto i moduli non nativi e gli override disattivati e ho eseguito il check up dei database con il modulo prestashop cleaner 1.8 e, una volta tornato al tema ufficiale, mi sono ritrovato ad una situazione molto "vanilla" e priva di errori se visulaizzata con la debug mode attiva. A questo punto, ho testato tutte le funzioni di questo sito web locale che mi ritrovo ibridato (vecchio database, nuova installazione) e tutto sembra andare bene, con nessun errore durante l'utilizzo della modalità di debug. Mi sento quindi a mio agio nell'usare il modulo 1-click per aggiornare a PS 1.7.7.4. - Metto lo zip nella cartella dei download e procedo con l'aggiornamento. Tutto fila liscio nell'aggiornamento dei file (tutto verde), ma quando il processo va al database, mi ritrovo con un errore e un back office poco accessibile, con front-office e back office zona ordini, clienti e setting inaccessibili a causa di troppi reindirizzamenti. Ecco la situazione e gli errori di aggiornamento del database: Updating database schema... Executing: CREATE TABLE ps_translation (id_translation INT AUTO_INCREMENT NOT NULL, id_lang INT NOT NULL, `key` TEXT NOT NULL COLLATE utf8_bin, translation TEXT NOT NULL, domain VARCHAR(80) NOT NULL, theme VARCHAR(32) DEFAULT NULL, INDEX IDX_ADEBEB36BA299860 (id_lang), INDEX `key` (domain), PRIMARY KEY(id_translation)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_module_history (id INT AUTO_INCREMENT NOT NULL, id_employee INT NOT NULL, id_module INT NOT NULL, date_add DATETIME NOT NULL, date_upd DATETIME NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_admin_filter (id INT AUTO_INCREMENT NOT NULL, employee INT NOT NULL, shop INT NOT NULL, controller VARCHAR(60) NOT NULL, action VARCHAR(100) NOT NULL, filter LONGTEXT NOT NULL, filter_id VARCHAR(191) NOT NULL, UNIQUE INDEX admin_filter_search_id_idx (employee, shop, controller, action, filter_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: DROP INDEX lang_iso_code ON ps_lang Executing: ALTER TABLE ps_lang CHANGE active active TINYINT(1) NOT NULL DEFAULT '0' , CHANGE iso_code iso_code VARCHAR(2) NOT NULL, CHANGE language_code language_code VARCHAR(5) NOT NULL, CHANGE date_format_lite date_format_lite VARCHAR(32) NOT NULL DEFAULT 'Y-m-d' , CHANGE date_format_full date_format_full VARCHAR(32) NOT NULL DEFAULT 'Y-m-d H:i:s' , CHANGE is_rtl is_rtl TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_2F43BFC7BA299860 ON ps_lang_shop (id_lang) Executing: ALTER TABLE ps_lang_shop RENAME INDEX id_shop TO IDX_2F43BFC7274A50A0 Executing: DROP INDEX id_lang ON ps_attribute_lang Executing: CREATE INDEX IDX_3ABE46A77A4F53DC ON ps_attribute_lang (id_attribute) Executing: CREATE INDEX IDX_3ABE46A7BA299860 ON ps_attribute_lang (id_lang) Executing: DROP INDEX deleted ON ps_shop_group Executing: ALTER TABLE ps_shop_group CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: DROP INDEX id_parent ON ps_tab Executing: DROP INDEX class_name ON ps_tab Executing: ALTER TABLE ps_tab ADD route_name VARCHAR(256) DEFAULT NULL, CHANGE position position INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE hide_host_mode hide_host_mode TINYINT(1) NOT NULL DEFAULT '0' , CHANGE icon icon VARCHAR(32) DEFAULT '' Executing: DROP INDEX id_shop_group ON ps_shop Executing: DROP INDEX id_category ON ps_shop Executing: ALTER TABLE ps_shop CHANGE id_category id_category INT NOT NULL DEFAULT '1' , CHANGE theme_name theme_name VARCHAR(255) NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_CBDFBB9EF5C9E40 ON ps_shop (id_shop_group) Executing: ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' 01:24:42 ERROR [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ':\n \n SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 """] In AbstractMySQLDriver.php line 106: An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE colo r color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 90: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 88: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--] Avete qualche soluzione da suggerire? Come posso stabilire quali tabelle stanno provocando il problema per correggerle prima di procedere con l'aggiornamento 1.7.7.4? Grazie mille per qualsiasi suggerimento possiate fornirmi. Di seguito sono riportate le specifiche di MAMP al momento dell'errore: PHP: 7.1.33 max_execution_time30000 max_file_uploads20 max_input_nesting_level64 max_input_time60000 max_input_vars10000 memory_limit1024M post_max_size256M Server web: Apache [RISOLTO] Dopo aver postato il problema anche su stackoverflow mi è stato fatto notate che chiaramente il messaggio d'errore rimandava ad un campo regolato in database da un VARCHAR di massimo 32 caratteri spazi inclusi che si presentava popolato in eccesso. Trovato il campo, ridotto il contenuto da 35 a 29 caratteri e questo errore si è risolto, permettendomi di raggiungere il compimento dell'aggiornamento. In ogni caso, data l'eccedenza di errori da precedente installazione (database e prestashop vengono portati avanti, senza reset, dal 2013), ho collegato il database aggiornato alla 1.7 ad una fresh install 1.7. Attualmente ho dei problemi di permessi su tale nuovo database, ma questo problema è stato risolto.
  11. Hi everyone, I am sandbox upgrading a copy of my live prestashop website in MAMP (free) following the iteration: - my website is a 1.6.1.3 - I perform an update of the stated 1.6.1.3 to a 1.6.1.24 with 1-click update and everything goes smooth, than I change MAMP from php 5.6.40 to 7.1.33 while uninstalling and deleting (in this order) all non native modules and themes except revws and payplug - I fresh install, in a different htdocs directory and in a different database, a 1.6.1.24 and I copy inside modules revws and payplug, the img folder and the setting file - I delete the 1.6.1.3 updated to 1.6.1.24 directory and the fresh install 1.6.1.24 database and connect the 1.6.1.24 fresh install to the 1.6.1.3 updated to 1.6.1.24 database and I modify the fresh install 1.6.1.24 directory to match the updated one that has been deleted - So I have a fresh install of prestashop connected to my previous historical complete database - In all of this process I kept non native module and overrides deactivated and performed multiple database checkout with module prestashop cleaner 1.8 and reverted to official theme, so a very "vanilla" situation. At this point, I tested all the functions of local website I find myself with and everything seems to go fine, no errors while using debug mode, so I feel comfortable in using 1-click module to update to PS 1.7.7.4. - I put the zip in the download folder and proceed with the update. Everything goes smooth in the files update (all green), but when the process goes to the database, I find myself with an error and a barely accessible back office, with front-office, and back office orders, customers and setting unaccessible due to too many redirects. Here you are the database update situation and errors: Updating database schema... Executing: CREATE TABLE ps_translation (id_translation INT AUTO_INCREMENT NOT NULL, id_lang INT NOT NULL, `key` TEXT NOT NULL COLLATE utf8_bin, translation TEXT NOT NULL, domain VARCHAR(80) NOT NULL, theme VARCHAR(32) DEFAULT NULL, INDEX IDX_ADEBEB36BA299860 (id_lang), INDEX `key` (domain), PRIMARY KEY(id_translation)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_module_history (id INT AUTO_INCREMENT NOT NULL, id_employee INT NOT NULL, id_module INT NOT NULL, date_add DATETIME NOT NULL, date_upd DATETIME NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_admin_filter (id INT AUTO_INCREMENT NOT NULL, employee INT NOT NULL, shop INT NOT NULL, controller VARCHAR(60) NOT NULL, action VARCHAR(100) NOT NULL, filter LONGTEXT NOT NULL, filter_id VARCHAR(191) NOT NULL, UNIQUE INDEX admin_filter_search_id_idx (employee, shop, controller, action, filter_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: DROP INDEX lang_iso_code ON ps_lang Executing: ALTER TABLE ps_lang CHANGE active active TINYINT(1) NOT NULL DEFAULT '0' , CHANGE iso_code iso_code VARCHAR(2) NOT NULL, CHANGE language_code language_code VARCHAR(5) NOT NULL, CHANGE date_format_lite date_format_lite VARCHAR(32) NOT NULL DEFAULT 'Y-m-d' , CHANGE date_format_full date_format_full VARCHAR(32) NOT NULL DEFAULT 'Y-m-d H:i:s' , CHANGE is_rtl is_rtl TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_2F43BFC7BA299860 ON ps_lang_shop (id_lang) Executing: ALTER TABLE ps_lang_shop RENAME INDEX id_shop TO IDX_2F43BFC7274A50A0 Executing: DROP INDEX id_lang ON ps_attribute_lang Executing: CREATE INDEX IDX_3ABE46A77A4F53DC ON ps_attribute_lang (id_attribute) Executing: CREATE INDEX IDX_3ABE46A7BA299860 ON ps_attribute_lang (id_lang) Executing: DROP INDEX deleted ON ps_shop_group Executing: ALTER TABLE ps_shop_group CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: DROP INDEX id_parent ON ps_tab Executing: DROP INDEX class_name ON ps_tab Executing: ALTER TABLE ps_tab ADD route_name VARCHAR(256) DEFAULT NULL, CHANGE position position INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE hide_host_mode hide_host_mode TINYINT(1) NOT NULL DEFAULT '0' , CHANGE icon icon VARCHAR(32) DEFAULT '' Executing: DROP INDEX id_shop_group ON ps_shop Executing: DROP INDEX id_category ON ps_shop Executing: ALTER TABLE ps_shop CHANGE id_category id_category INT NOT NULL DEFAULT '1' , CHANGE theme_name theme_name VARCHAR(255) NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_CBDFBB9EF5C9E40 ON ps_shop (id_shop_group) Executing: ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' 01:24:42 ERROR [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ':\n \n SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 """] In AbstractMySQLDriver.php line 106: An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE colo r color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 90: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 88: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--] Do you have any solution to suggest? How do I address which tables are provoking the issue in order to correct them before proceeding with the 1.7.7.4 update? Thanks a lot for any suggestion provided. The following are the specifications of MAMP at the time of the error: PHP: 7.1.33 max_execution_time30000 max_file_uploads20 max_input_nesting_level64 max_input_time60000 max_input_vars10000 memory_limit1024M post_max_size256M Web server: Apache [SOLVED] After posting the problem also on stackoverflow I was made to notice that the error message clearly referred to a field regulated in the database by a VARCHAR of up to 32 characters including spaces which appeared to be populated in excess. Found the field, reduced the content from 35 to 29 characters and this error was resolved, allowing me to reach completion of the update. In any case, given the excess of errors from previous installation (database and prestashop are carried out, without reset, since 2013), I connected the database updated to 1.7 to a fresh install 1.7. I currently have permissions problems on this new database, but this specific issue has been fixed.
  12. Buongiorno, sapete se esiste un modulo analogo, capace di inserire contenuti solo su determinate pagine o addirittura determinati prodotti, come d'altronde fa questo modulo, ma non per delle slider di immagini ma per del semplice HTML? Grazie in Anticipo!
  13. Yes, same issue here. Uncompressed and re-compressed from the tool "compress while right clicking. It worked just fine.
  14. So, Vekia, as of I really needed to solve the situation, i took a look at tiny mce guides and html5 <base> tag rules. In first instance, I have managed to add to "header.tpl"file of my theme the following code: With this modification, all images issues with relative path vanished, but I started Having issues with link, as of all relative ones redirected to the home page. Than, i decided to make another try, while dismantling previoulsy made header modification and modifing directly the js/admin js file of the tiny mce, by setting: relative_urls:false, and adding the following line: remove_script_host:true, Everything is smooth and fine (for now)!
×
×
  • Create New...

Important Information

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