Jump to content

Mavenace

Members
  • Posts

    6
  • Joined

  • Last visited

Contact Methods

Profile Information

  • Location
    Southampton, UK
  • First Name
    Fedor
  • Last Name
    Alphenaar

Mavenace's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Upgrading PrestaShop 1.6.0.14 to PrestaShop 1.6.0.19 gave me the following problem. As usual former developer has updated the default-bootstrap theme and although I created a new theme, using the default-bootstrap, I got into the following problem. The production site show that the newsletter is using GLOBAL.SCSS after upgrading the newsletter is using blocknewsletter.css Using Firefox it is clearly to see that the GLOBAL.SCSS is ruled out. I have checked the newsletter files between PROD and TEST but I just cannot find the reason why it is. You can see the difference at: http://fjernstyret.dk/ http://test.fjernstyret.dk/ I just cannot figure out why the TEST environment keeps using blocknewsletter.css where PROD uses GLOBAL.SCSS thanks for helping me out Fedor
  2. Are the no override folders? This leaves the core files as is, and modifications are in an override folders and you can upgrade the core software. Obvious you need to test because you might need to rewrite the modifications
  3. One question: Will these same modifications be overwritten again with the next PrestaShop update?
  4. You always should update but what I would do is the following: setup a TEST/QA environment Test all the upgrades, patches etc Then have let's say an update release schedule every 3 months. This way you are always up to date with the latest patches. 2 weeks before your patch release you freeze any update on the TEST/QA environment giving you 2 weeks time to test everything again. Then put your shop in maintenance mode, copy your DB to QA, the upgrade in QA Test again and then move all over to PROD This in high level terms.
  5. Hi I just performed an upgrade for a customer from 1.4 to 1.6 1) Setup a TEST environment (copy of your current prod) and do the upgrade in that test environment write down step by step what you do 2) Setup a QA environment, this is for the customer to test finally when approved move it to PROD Backup is interesting, but I would not even touch the production environment and you do not need to. I can do this for you, but then contact me Fedor
  6. I just migrated Prestashop 1.4.6.2 to Prestashop 1.6.1.7, despite some issues, especially with picture and birthday required, which I solved I have one issue remaining. The developer, unfortunately, has updated the default PrestaShop template which I finally could solve but it might mean that he/she has changed more "core" files that I do not know and you guessed it, this developer did not leave any documentation. The issue: On 1.4 when someone adds something to the shopping_cart, the trolley turns green by using the global.css file. Both the 1.4 and 1.6.1.7 have the following #header_nav.green in the global.css #header_nav.green { background-image:url('../img/cart_green.png'); In 1.6.1.7 however, the global.css file is the same but in the source on 1.4 you can read: <!-- Block user information module HEADER --> <div id="header_user"> <ul id="header_nav" class="green"> <li id="shopping_cart"> where on 1.6.1.7 <!-- Block user information module HEADER --> <div id="header_user" > <ul id="header_nav"> <li id="shopping_cart"> Where in the system is PrestaShop telling the shopping cart that something has been added for the trolley to turn GREEN. Appreciate your help
×
×
  • Create New...