Rhapsody

I am a Prestashop user since version 1.2 and had three shops in Prestashop 1.5.6.2 that I planned to upgrade to PS 1.7. Once I upgraded the first shop, it was a step backwards. The themes are significantly different. Only some of the code has moved to the new Symfony templating system so customizing the back office themes is a real challenge. Shop performance and load times were significantly longer. I wanted to stay with Prestashop, but due to problems, and loss of features that worked and were free in the previous release, had no choice but to move to something different. Next I updated the shop to Thirty Bees 1.0.8. Follow the update directions on Thirty Bees. I customized the default community theme and am very happy with it. All shops are running the "bleeding edge" 1.10 version and work well. I have posted questions on the Thirty Bees forum and received prompt responses. I'm sad to say the Prestashop took a big step backwards with the 1.7 release. With Thirty Bees all the previous orders, customers and products were retained in the shop. If you create a shop with Thirty Bees there are some good paid themes available if you don't want to create your own theme by modifying a free one. ---------------------------------------- Espanol using Google. Perdón por mi mal español Soy un usuario de Prestashop desde la versión 1.2 y tenía tres tiendas en Prestashop 1.5.6.2 que planeaba actualizar a PS 1.7. Una vez que actualicé la primera tienda, fue un paso atrás. Los temas son significativamente diferentes. Solo parte del código se ha trasladado al nuevo sistema de plantillas de Symfony, por lo que personalizar los temas de back office es un verdadero desafío. El rendimiento de la tienda y los tiempos de carga fueron significativamente más largos. Quería quedarme con Prestashop, pero debido a problemas y la pérdida de funciones que funcionaban y eran gratuitas en la versión anterior, no tuve más remedio que pasar a algo diferente. A continuación, actualicé la tienda a Thirty Bees 1.0.8. Siga las instrucciones de actualización en Treinta abejas. Personalicé el tema predeterminado de la comunidad y estoy muy contento con él. Todas las tiendas están ejecutando la versión 1.10 "edge" y funcionan bien. He publicado preguntas en el foro de Treinta Abejas y he recibido respuestas rápidas. Me entristece decir que Prestashop dio un gran paso atrás con la versión 1.7. Con Thirty Bees, todos los pedidos anteriores, clientes y productos se retuvieron en la tienda. Si crea una tienda con Treinta abejas, hay algunos temas bien pagados disponibles si no desea crear su propio tema modificando uno gratuito.

More to report and it isn't all good, but not because of the script. The free script tools allow setting of quantities with some good query tools. Setting of prices for combinations requires a paid version, but I never went to the next step to do that. What I found is PS Version 1.7.6.1 will not handle the same attributes I was able to make work on the 1.5.6.2 version of my shop. A product was defined with 7 dropdown selectors with the following number of options for each dropdown (4,4,4,4,4,4,2). I set a default condition with 0 quantity to prevent people adding to cart unless required selections were made. There is more than a 30 second lag from the time that the dropdown is selected and the cart button is enabled. The same product combination on PS 1.5.6.2 responded in less than 1 second. Based on this limitation, I will not upgrade my shop to 1.7.6.1, and instead will try upgrading to PS version 1.6.1.24. Prestashop 1.7.6.1 is a step back in capability from 1.5.6.2!

I can confirm the purchased module does not meet the requirements. It is better at generating the combinations without timing out, but the ability to edit and set quantities for different combinations is virtually impossible. I ran across this thread [Free Script] Prestools Suite: Mass Edit, Order Edit And Much More that may have a workable solution. I am going to try this and will report what I find.

Need help modifying back office customer edit form to accommodate custom fields I'm moving a 1.5.6.2 shop to 1.7.6.1 due to required server PHP upgrades. The existing 1.5.6.2 shop has additional text fields that were added to the customer table. The database has been imported to a clean 1.7.6.1 install with the extra fields. I have accomplished the following on the 1.7.6.1 install: Successfully modified the classic theme to add the extra fields and saving them on New User registration Successfully modified the Edit your personal information page so the fields may be updated and saved. Successfully modified back office to display the extra fields when viewing a customer. I am having problems trying to figure out how to modify the form to edit the new fields in the back office. The approach I've taken is not optimal because I did it with overrides and template mods. What I would like to know if anyone can help with how this may be done using hooks. I am not familiar with this approach but see that is the recommended approach. Can anyone provide tips on how to accomplish this? The code below provides the field definitions in the override file. <?php /** * THC created from 1.7.6.1 of customer.php * Adds custom field definitions * spouse, yachtclub, boat, model, sailnum, phrfspin, phrfnonspin, officer * **/ class Customer extends CustomerCore { /** @var string spouse - THC add for spouse name */ public $spouse; /** @var string yachtclub - THC add for YC name*/ public $yachtclub; /** @var string boat - THC add for boat name*/ public $boat; /** @var string model - THC add for boat model*/ public $model; /** @var string sailnum - THC add for sail number*/ public $sailnum; /** @var integer phrfspin - THC add for PHRF spinnaker*/ public $phrfspin; /** @var integer phrfnonspin - THC add for PHRF non-spinnaker*/ public $phrfnonspin; /** @var integer officer - THC add for Officer Position*/ public $officer; // this was from core with custom fields added to array public static $definition = array( 'table' => 'customer', 'primary' => 'id_customer', 'fields' => array( 'secure_key' => array('type' => self::TYPE_STRING, 'validate' => 'isMd5', 'copy_post' => false), 'lastname' => array('type' => self::TYPE_STRING, 'validate' => 'isCustomerName', 'required' => true, 'size' => 255), 'firstname' => array('type' => self::TYPE_STRING, 'validate' => 'isCustomerName', 'required' => true, 'size' => 255), 'email' => array('type' => self::TYPE_STRING, 'validate' => 'isEmail', 'required' => true, 'size' => 255), 'passwd' => array('type' => self::TYPE_STRING, 'validate' => 'isPasswd', 'required' => true, 'size' => 255), 'last_passwd_gen' => array('type' => self::TYPE_STRING, 'copy_post' => false), 'id_gender' => array('type' => self::TYPE_INT, 'validate' => 'isUnsignedId'), 'birthday' => array('type' => self::TYPE_DATE, 'validate' => 'isBirthDate'), 'newsletter' => array('type' => self::TYPE_BOOL, 'validate' => 'isBool'), 'newsletter_date_add' => array('type' => self::TYPE_DATE, 'copy_post' => false), 'ip_registration_newsletter' => array('type' => self::TYPE_STRING, 'copy_post' => false), 'optin' => array('type' => self::TYPE_BOOL, 'validate' => 'isBool'), 'website' => array('type' => self::TYPE_STRING, 'validate' => 'isUrl'), 'company' => array('type' => self::TYPE_STRING, 'validate' => 'isGenericName'), 'siret' => array('type' => self::TYPE_STRING, 'validate' => 'isGenericName'), 'ape' => array('type' => self::TYPE_STRING, 'validate' => 'isApe'), 'outstanding_allow_amount' => array('type' => self::TYPE_FLOAT, 'validate' => 'isFloat', 'copy_post' => false), 'show_public_prices' => array('type' => self::TYPE_BOOL, 'validate' => 'isBool', 'copy_post' => false), 'id_risk' => array('type' => self::TYPE_INT, 'validate' => 'isUnsignedInt', 'copy_post' => false), 'max_payment_days' => array('type' => self::TYPE_INT, 'validate' => 'isUnsignedInt', 'copy_post' => false), 'active' => array('type' => self::TYPE_BOOL, 'validate' => 'isBool', 'copy_post' => false), 'deleted' => array('type' => self::TYPE_BOOL, 'validate' => 'isBool', 'copy_post' => false), 'note' => array('type' => self::TYPE_HTML, 'validate' => 'isCleanHtml', 'size' => 65000, 'copy_post' => false), 'is_guest' => array('type' => self::TYPE_BOOL, 'validate' => 'isBool', 'copy_post' => false), 'id_shop' => array('type' => self::TYPE_INT, 'validate' => 'isUnsignedId', 'copy_post' => false), 'id_shop_group' => array('type' => self::TYPE_INT, 'validate' => 'isUnsignedId', 'copy_post' => false), 'id_default_group' => array('type' => self::TYPE_INT, 'copy_post' => false), 'id_lang' => array('type' => self::TYPE_INT, 'validate' => 'isUnsignedId', 'copy_post' => false), 'date_add' => array('type' => self::TYPE_DATE, 'validate' => 'isDate', 'copy_post' => false), 'date_upd' => array('type' => self::TYPE_DATE, 'validate' => 'isDate', 'copy_post' => false), 'reset_password_token' => array('type' => self::TYPE_STRING, 'validate' => 'isSha1', 'size' => 40, 'copy_post' => false), 'reset_password_validity' => array('type' => self::TYPE_DATE, 'validate' => 'isDateOrNull', 'copy_post' => false), 'spouse' => array('type' => self::TYPE_STRING, 'validate' => 'isGenericName'), 'yachtclub' => array('type' => self::TYPE_STRING, 'validate' => 'isGenericName'), 'boat' => array('type' => self::TYPE_STRING, 'validate' => 'isGenericName'), 'model' => array('type' => self::TYPE_STRING, 'validate' => 'isGenericName'), 'sailnum' => array('type' => self::TYPE_STRING, 'validate' => 'isGenericName'), 'phrfspin' => array('type' => self::TYPE_INT, 'validate' => 'isInt'), 'phrfnonspin' => array('type' => self::TYPE_INT, 'validate' => 'isInt'), 'officer' => array('type' => self::TYPE_INT, 'validate' => 'isUnsignedId'), ), ); }

I am in the process of modifying four of my working 1.5.6.2 shops to 1.7.6.1. The 1.5.6.2 templates allowed display of a field name to the left, the field, then a helper description below the field. I am unable to see how a description may be added to the 1.7.6.1 fields. This is the sample code from the 1.5.6.2 address.tpl file modified with the span class="form_info" section that displays a description under the field in the form: {if $field_name eq 'address2'} <p class="required text"> <label for="address2">{l s='Address (Line 2)'}</label> <input type="text" id="address2" name="address2" value="{if isset($smarty.post.address2)}{$smarty.post.address2}{else}{if isset($address->address2)}{$address->address2|escape:'html'}{/if}{/if}" /> <span class="form_info">{l s='(Apartment, suite, unit, building, floor, etc.)'}</span> </p> {/if} Anyone have an idea on how to accomplish the same using 1.7.6.1?

I developed a universal solution for version 1.7.6.x that works on all sites I have. In my application, the Prestashop install is running on a subdomain of a site it is related to. The text and link goes to the main domain. Search for this in prestashop_directory\themes\classic\templates\_partials\footer.tpl and prestashop_directory\themes\classic\templates\checkout\_partials\footer.tpl and replace it with

I too am upgrading a shop from 1.5.6.2 to 1.7.6.1 and have found this limitation. I'm wondering if this paid module will restore the capability that used to be included in the back office for free. Bulk Combinations Generator Module - $59.99 The current 1.7 "simplified" attributes and combinations method is unusable! Has anybody found a workable solution? <rant on> When Prestashop updates software with major releases, the team should make sure all existing capabilities are maintained. Many of us Prestashop users have shops that rely on features and capabilities we don't want to lose by a software upgrade. I am upgrading from 1.5.6.2 only because it will not run under PHP 7 which I am being forced to migrate to. Otherwise, I'd be happy to stay with the Prestashop 1.5 version. I've been using Prestashop since version 1.2. The upgrade to 1.7 is the first I've needed to purchase a 3rd party data migration module to move my data. The One click upgrade process just doesn't work for me. </rant off>

I'm returning to this thread after a number of years using PS 1.5.6.2 and was wondering if anyone developed a solution for PS 1.7 since I will be upgrading all the old shops.

El Patron, That was one of my earlier posts and request PSCV-6672 was posted on the forge on 23 July 2013 for this capability in version 1.5. Unfortunately, nothing has been done with the request. The work around solution for PS 1.4 does not work in PS 1.5.

ZenVisuals, Thanks for that! I tried it on my test shop using 1.5.6.2 and it works with the default theme. I have made enough changes on my custom theme that I believe take out all the ajax calls, so it doesn't work there.I plan on going back to the custom theme and restoring that code. Have you checked operation with the mobile theme? I found there were some things on the default mobile theme that didn't work, so I significantly customized it to meet my needs. Nice work!

The solution is in my Post #80 in this thread.

I had the same problem because I created a custom BO theme. What I did was rename the custom theme to temp, then renamed the default theme to the name of my custom theme and was able to display the BO.

I've got no problem with PHP 5.3.28 Try turning debug on to see what is causing the blank screen

Lordcracker - thanks very much for the affirmation of the solution. I have this fix that Lordcracker provided to my original problem successfully operating on four shops running PS 1.5.6.2 As a general rule, whenever you change a template, clear the cache and recompile per my post #10 in this thread.

I'm using PS 1.5.6.2 and am trying to change the order of the CMS links in the footer. In the BO Preferences, CMS I have changed the position of CMS entries using the arrows to slide them in the order I want. This has no effect on the position of the CMS links displayed in the footer. I cleared the cache and forced compile - still no change. Does anyone know how to put the CMS links in the order desired?