I have one website for testing.
And another website is my live PS store.

Both websites were upgraded from v.1.4.4.1 over to v.1.6.0.9 successfully.

On the testing site in PS BO, Advanced Parameters > Configuration Information: I configured Required parameters & Optional parameters successfully.. “Optional parameters OK“

I did this by editing main pHp.ini file on the server (/usr/local/lib/php.ini).

Prior to upgrading the live PS store, I noticed that in live store BO, Advanced Parameters > Configuration Information displayed Required & Optional parameters that I had already configured in server’s main pHp.ini

To confirm configuration, I created phpinfo.php and both testing & live sites display identical configurations.
Configuration File (php.ini) Path /usr/local/lib
Loaded Configuration File /usr/local/lib/php.ini

Regardless, I upgraded live PS store in hopes that the upgrade process would resolve the issue.. It did not.

As a result, when I access PS live store running v.1.6.0.9 and attempt to access translations, I receive the following warning.

Warning! Your PHP configuration limits the maximum number of fields allowed in a form
1000 for max_input_vars.
Please ask your hosting provider to increase this limit to 4043 at least, or you will have to edit the translation files.

I posted some help on PS forum and I was directed with a free module (Display pHP Environment) that allowed me to see another pHp.ini file inside my /admin/ folder. It was like looking for a needle in a hay stack, until I used the free Display pHp Environment module.

Resources

ps configuration not reflecting server’s main pHp.ini: http://www.prestashop.com/forums/topic/367958-ps-configuration-not-reflecting-server%E2%80%99s-main-phpini/#entry1827905
Free Module, Display pHp Environmnet: http://www.prestashop.com/forums/topic/278164-free-module-display-php-environment-phpinfo-back-office/

The post PrestaShop pHp.ini Location Does Not Go To Server’s Main pHp.ini appeared first on My Web Development.

Step 1.) Download and install the autoupgrade module onto your PS.

Step 2.) Place your store under maintenance mode.

Step 3.) Go to: Modules > Administration; and configure 1-click Upgrade.

Step 4.) Backup your files & Click on Upgrade!

Results..

Analyzing the situation …Shop deactivated. Now downloading (this can takes some times )…
[Ajax / Server Error for action download] textStatus: “error ” errorThrown:”Internal Server Error ” jqXHR: ” “

Steps to correct Ajax Error..

Step 1.) Upload PS v.1.5.6.2 with FTP to: /admin/autoupgrade/latest/prestashop

Step 2.) Within the configuration of autoupgrade module, select More options (Expert mode).

Step 3.) Select the channel: Local directory and label your version.

Step 4.) Save

Results..

Settings update successful.

Step 5.) Click Upgrade PrestaShop Now!

Results..

Upgrade complete, with a few issues.. Apparently, these issues are common and can be resolved.

A to do list will generate after upgrade is complete, instructing on how to resolve common issues that may occur.

Out of the 5 to do list items, I experienced product images missing:

1. Cookies have changed, you will need to log in again once you refreshed the page
2. Javascript and CSS files have changed, please clear your browser cache with CTRL-F5
3. Please check that your front office theme is functional (try to create an account, place an order…)
4. Product images does not appear in the front office? Try regenerating the thumbnails in Preferences > Images
5. Do not forget to reactivate your shop once you have checked everything!

Steps to correct missing product images..

Step 1.) BO: Preferences > Image – Product Images: until you move all images to new file system, use Legacy Image File System; set this to ‘yes’ and save.

Results..

Duplicate images were found when moving the product images. This is likely caused by unused demonstration images. Please make sure that the folder/home/domain/public_html/img/p/duplicates/only contains demonstration images, and then delete it.

Step 1.) Delete folder /home/domain/public_html/img/p/duplicates/

Step 2.) Preferences > Image – Regenerate thumbnails = select products, format: all & DON’T erase previous image.

Results..

217 errors
Original image is missing or empty (/home/domain/public_html/img/p/1/7/0/170.jpg) for product ID 96

Steps to correct error message ‘original image is missing or empty’.

Step 1.) First, confirm images exist.

Results..

There are missing product images..

v.1.4.4.1 uses The Legacy File System where all product images are within /img/p/

v.1.5+ uses the new File System using sub directories that match the image ID /img/p/9/6/96-197.jpg .

e.g. 
Legacy File System = /img/p/96-197.jpg | 96- = image ID
New File System = /img/p/9/6/197.jpg | folders /9/6/ = image ID

Step 1.) BO: Preferences > Image – Move Images; click on button ‘move images’.

Images moved successful

Step 2.) BO: Preferences > Image – Use the Legacy Image File System = No

Step 3.) BO: Preferences > Image – Regenerate thumbnails = select products, format: all & erase previous image.

Results..

401 errors
Original image is missing or empty (/home/domain/public_html/img/p/1/7/0/170.jpg) for product ID 96

Step 1.) Investigate product ID 96

Results..

The product ID is missing from image path. I investigated both Live PrestaShop Store (LPS) and Testing Domain (TD); product ID is missing on TD.
e.g. TD missing image = /domain/170-thickbox_default/170.jpg | LPS image displayed = /domain/96-170-thickbox/170.jpg

This error occurred once before, during a copy of my LPS that I migrated to a TD; both running PSv.1.4.4.1.

And it was a permissions issue, the solution was to chmod /img/ including all sub directories to 755; another post was dedicated to this issue.

Step 1.) Set file permissions chmod to 755 to all directories & sub directories.

Step 2.) BO: Preferences > Image – Regenerate thumbnails = select products, format: all & DON’T erase previous image.

Results..

217 errors
Original image is missing or empty (/home/domain/public_html/img/p/1/7/0/170.jpg) for product ID 96

Step 1.) In the BO, clear the cache: Advanced Parameters > Smarty = Clear Smarty cache & Autoload cache

Update successful

Results..

The product images are still missing.

Investigate other options from PrestaShop forum..

–REVERTED– 

Step 1.) Set creation date earlier than 2013-03-26′. Edit the settings file /config/settings.inc.php
e.g. define(‘_PS_CREATION_DATE_’, ‘2011-09-11’);

REVERTED: /config/settings.inc.php, due to _PS_CREATION_DATE_ error: Notice: Constant _PS_CREATION_DATE_ already defined in /config/settings.inc.php on line 20

–END OF REVERTED–

Step 1.) Edit /controllers/admin/AdminImagesController.php
56. $this->display_move = true;

Step 3.) BO: Preferences > Image – Move Images; click on button ‘move images’.

Step 4.) BO: Preferences > Image – Regenerate thumbnails = select products, format: all & DON’T erase previous image.

Images moved successful

Results..

217 errors
Original image is missing or empty (/home/domain/public_html/img/p/1/7/0/170.jpg) for product ID 96

Steps to correct errors through process of elimination using different regenerate options.

Step 1.) BO: Preferences > Image – Regenerate thumbnails = select products, format: all & erase previous image.

I’ve been hesitant on selecting the format option to ‘erase previous image’, however numerous of attempts have been performed without deleting. So far, this option actually seems to be doing something.. After I regenerated images, the web browser indicates it’s processing the action.

It timed out

Let’s try another format..

Step 2.) BO: Preferences > Image – Regenerate thumbnails = select products, format: home & erase previous image.

Results..

401 errors
Original image is missing or empty (/home/domain/public_html/img/p/1/7/0/170.jpg) for product ID 96

Let’s try another format..

Step 3.) BO: Preferences > Image – Regenerate thumbnails = select products, format: large & erase previous image.

Results..

401 errors
Original image is missing or empty (/home/domain/public_html/img/p/1/7/0/170.jpg) for product ID 96

O.k., that is time consuming.. I need to investigate other options.

Step 1.) First, investigate images by disabling Friendly URL.
BO: preferences > SEO & URLs – Set up URLs = disable both Friendly URL & Accented URL.

product image: \public_html\img\p\1\3\4\0\1340-home.jpg
product image: \public_html\img\p\1\3\4\0\1340-home_default.jpg

If I remove _default from the image label e.g. 1340-home_default.jpg = 1340-home.jpg
Then product image is displayed!

–REVERT–

This is one method I tried and it did not work, so I reverted back.

Step 1.) Go to default 1.5.6.2 theme, edit product.tpl and remove _default from image tags:
186 large_default
191 -default-large_default
211 thickbox_default
212 medium_default
551 medium_default

Step 2.) Clear Smarty cache & Autoload cache

Results..

Did not work..

Step 3.) Revert product.tpl back to original state.

–END OF REVERT–

A post on PS forum mentioned a bug similar to mine, but was opposite in how the image label was represented.  There issue was that by default image preferences were set: small_default, medium_default, large_default, thickbox_default, category_default, etc. and required the removal of _default. Mine is not the case.. I require _default

Next, under BO: Preferences > Image

I’ll edit the image names and add the extension _default.

Step 1.) BO: Preferences > Image = renamed all images with _default e.g. small_default, medium_default, large_default, thickbox_default, catgeory_default, home_default large_scene_default, thumb_scene_default

Step 2.) BO: Preferences > Image = Regenerate thumbnails.. This time, I’m going to select one at a time.

e.g. Select an image: products, Select a format, home_default & erase previous images.

Results..

Regenerated thumbnails and browser timed out after 30 or so minutes, however a good majority of product images now appeared!

Now, I need to replace missing images and figure out why it timed out.

Step 1.) Upload the backup folder /img/p/

Thousands of images, nearly 400MB re-uploaded.

Step 2.) BO: Preferences > Image = Regenerate thumbnails.. I’m going to select one at a time.

e.g. Select an image: products, Select a format, home_default & Erase previous images.

Results..

401 errors
Original image is missing or empty (/home/domain/public_html/img/p/1/7/0/170.jpg) for product ID 96

Step 1.) BO: Preferences > Image = Regenerate thumbnails – select image: product, select format: all & erase previous images.

Results..

All product images archived & displayed! However, image categories are still missing.

Step 1.) BO: Advanced Parameters > Performance = Clear Smarty cache & Autoload cache.

Step 2.) BO: Preferences > Image = Regenerate thumbnails – select image: categories, select format: all & erase previous images.

Results..

Browser indicated that PS was processing action, then delivered a blank page
index.php?controller=AdminImages&token

 Step 1.) Confirm all category images reside /img/c/

Not all category images existed..

Step 2.) Upload category images from backup /img/c/

Step 3.) BO: Preferences > Image = Regenerate thumbnails – select image: categories, select format: all & erase previous images.

Results..

Did not work, received a blank page after 20 seconds

Step 1.) Enable Troubleshooting by editing /config/defines.inc.php

Line 28
Find: define(‘_PS_MODE_DEV_’, false);
Replace with: define(‘_PS_MODE_DEV_’, true);

Step 2.) BO: Advanced Parameters > Performance – Clear Smarty cache & Autoload cache; received error.

–ERROR–

Notice: Constant _PS_CREATION_DATE_ already defined in /config/settings.inc.php on line 20
Warning: Cannot modify header information – headers already sent by (output started at /config/settings.inc.php:20) in /classes/Tools.php on line 141

–END OF ERROR–

Steps to resolve error..

Step 1.) Open /config/settings.inc.php and remove line 20.

Step 2.) BO: Advanced Parameters > Performance – Clear Smarty cache & Autoload cache.

Results..

SOLVED: Clear Smarty cache & Autoload cache works!

Now, time to regenerate thumbnails..

Step 1.) BO: Preferences > Image = Regenerate thumbnails – select image: categories, select format: all & erase previous images.

Results..

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 9600 bytes) in /classes/ImageManager.php on line 365

Steps on how to increase the memory on your server from timing out. There are a couple of methods in achieving this.

Step 1.) Using cPanel, select account and edit its php.ini file.
Or you can log-in with SSH and root, edit the php.ini located in /usr/local/lib/php.ini

Step 2.) I adjusted the php.ini file residing on testing domain’s account, following cPanels instructions: http://forums.cpanel.net/f34/php-memory-limit-63777.html

Default settings:

cPanel PHP max execution time –> 90 seconds
cPanel PHP max POST size –> 55 MB
cPanel PHP max upload size –> 50 MB

Desired settings:

cPanel PHP max execution time –> 360 seconds
cPanel PHP max POST size –> 500 MB
cPanel PHP max upload size –> 250 MB

Step 3.) Save & Restart Apache.

Results..

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 9600 bytes) in /classes/ImageManager.php on line 365

Apparently, the php.ini file that I restored to use for that particular account did not take effect.

Oh well, I’ll just edit the server’s main php.ini file..

Step 1.) Edit main php.ini file by logging into your cPanel’s WHM and go to: PHP Configuration, adjust the following.
Or you can log-in with SSH and root, edit the php.ini located in /usr/local/lib/php.ini

memory_limit was 32M | changed to -1
upload_max_filesize was 2M | changed to 500M
max_execution_time was 30 | changed to 360
max_input_time was 60 | changed to 360

Step 3.) Save & Restart Apache.

Results..

SUCCESS !!!

I’m no longer receiving blank pages when I regenerate images, and now all of them are displayed in both BO and FO.

Next, revert any edits made to file(s) during testing that are no longer required.

Revert 1.) Edit /controllers/admin/AdminImagesController.php; change back to false.
56. $this->display_move = false;

Revert 2.) Default PSv.1.5.6.2 theme, edit product.tpl and remove _default from image tags. This has been REVERTED back to original state.

Revert 3.) /config/settings.inc.php, remove _PS_CREATION_DATE_: define(‘_PS_CREATION_DATE_’, ‘2011-09-11’);
Due to error.. Notice: Constant _PS_CREATION_DATE_ already defined in /config/settings.inc.php on line 20

NOTES: Apparently, when images are missing from /img/p/ folder, and you attempt to regenerate thumbnails an improper file system takes place.

e.g. 
proper File System = /img/p/9/6/197.jpg | folders /9/6/ = image ID
improper File System = /img/p/1/9/7/197.jpg | image ID missing

BEWARE: Before upgrading to PSv.1.5.6.2, all product images using Legacy File System /img/p/ existed and store displayed correctly with the migrated data from PSv.1.4.4.1 At some point during the upgrade process, PS deleted a good majority of images. As long as current backups are accessible, then there is little to worry about.

Resources

Can’t auto upgrade any version, same error every time: http://www.prestashop.com/forums/topic/192406-cant-auto-upgrade-any-version-same-error-every-time/
Product Images Missing: http://www.prestashop.com/forums/topic/272842-solved-product-image-missing/
Product Images Missing after upgrade: http://www.prestashop.com/forums/topic/272333-solved-how-to-dont-show-product-images-after-upgrade-to-155/
Troubleshooting: http://doc.prestashop.com/display/PS15/Troubleshooting

The post 1-Click Upgrade PrestaShop Auto Upgrade Module appeared first on My Web Development.

Migration was successful, allowing access into PrestaShop Back Office.  

However, in attempts to access Front Office, I would get redirected to the live site.

To resolve this redirect issue, I logged into the BO and adjust the following.

—————————————-
preferences > SEO & URLs

PS directory: /MyProject/

Shop domain name: localhost
Shop domain name for SSL: localhost

save
—————————————-

If you are receiving “Page not found” or /MyProject/en/ is blank, then a couple of things need to be done.

Step 1.)
Generate a new .htaccess file in BO, or copy/paste your existing one into root of your PrestaShop installation.

Step 2.)
Enable the rewrite_module for Apache on your WAMP Server, and restart Apache: Apache > Apache Modules > rewrite_module

Resource

localhost keeps being redirected: http://www.prestashop.com/forums/topic/211778-localhost-keeps-being-redirected/
“Page not found” with PrestaShop 1.4.8.2 on WAMP: http://www.prestashop.com/forums/topic/175273-page-not-found-with-prestashop-1482-on-wamp/
PrestaShop Blank Page: http://www.prestashop.com/forums/topic/10115-big-problem-blank-page/

The post Using WAMP to test site, localhost redirects to live site appeared first on My Web Development.

After a successful data migration onto WAMP, in attempts to log into the Back Office (BO) resulted with error ’employee does not exist or incorrect password’.  To resolve this error, follow two simple steps for password change phpMyAdmin.

Step 1.) You will need to copy your _COOKIE_KEY_ located in /config/settings.inc.php
This will be a random alphanumeric string of characters (e.g. Pi32n2bx6koC31bq7mndpc32ihfYcZ1bKMCogBIq1LExF5nGcOdWm3gc)

Step 2.) Log into phpMyAdmin and select SQL and enter the below syntax and click Go.
Note: DO NOT enter any spaces between your _COOKIE_KEY_ and PASSWORD

UPDATE `ps_employee` SET `passwd` = MD5(‘Pi32n2bx6koC31bq7mndpc32ihfYcZ1bKMCogBIq1LExF5nGcOdWm3gcNEWPASSWORD’) WHERE `ps_employee`.`id_employee` = 1;

There is no space between the _COOKIE_KEY_ and your password; they run together..

Resources:

Screen Shot Instructions on how to restet PrestaShop employee password via phpMyAdmin: http://www.templatemonster.com/help/how-to-reset-prestashop-admin-details.html

The post password change phpMyAdmin for user in PrestaShop appeared first on My Web Development.

PrestaShop taxes not working in the product page, when user enters ‘Pre-tax retail price’ and selects the ‘Tax rule’, nothing changes in the Back Office or Front Office of PrestaShop.

Step 1.) Confirm that you have enabled the feature to display tax in the Back Office as ‘tax included’: BO > Customers > Groups

If that did not resolve your taxes from displaying, then go on to step two.

Step 2.) Go to theme and edit product.tpl

Line 256

{if $tax_enabled && ((isset($display_tax_label) && $display_tax_label == 1) OR !isset($display_tax_label))}
{if $priceDisplay == 1}{l s=’tax excl.’}{else}{l s=’tax incl.’}{/if}
{/if}

Replace with..

{if $tax_enabled && ((isset($display_tax_label) && $display_tax_label == 1) OR !isset($display_tax_label))}
{if $priceDisplay == 1}{l s=’tax excl.’}{else}{l s=’tax incl.’}{/if}
{/if}

Line 275

{if $tax_enabled && $display_tax_label == 1}
{if $priceDisplay == 1}{l s=’tax excl.’}{else}{l s=’tax incl.’}{/if}
{/if}

Replace with..

{if $tax_enabled && $display_tax_label == 1}
{if $priceDisplay == 1}{l s=’tax excl.’}{else}{l s=’tax incl.’}{/if}
{/if}

Don’t forget to recompile your smarty template after editing any .tpl file in the Back Office.
BO > Preferences > Performance > Smarty > Force compile

Resources

Display (tax included) with the price PrestaShop: http://www.prestashop.com/forums/topic/243182-display-tax-included-with-the-price-prestashop-154-solved/
Price display and tax included: http://www.prestashop.com/forums/topic/246841-solved-pricedisplay-and-tax-included/

The post PrestaShop Taxes Not Working In Product Page appeared first on My Web Development.

adm/tabs/AdminProducts.php

BO > Catalog > Add & Delete Product Accessory

When you attempt to delete product accessory, an error prompt “Bad Size” is generated and you have to manually delete the accessory from the database.

Bug Fix found on github: https://github.com/PrestaShop/PrestaShop-1.4/commit/38c46b70f4cef35f67a9ce55d5a5cde0e22008f4

Easy solution was to copy the entire file from GitHub and replace with your file (adm/tabs/AdminProducts.php).

There are some additional postings found on PrestaShop Forum as well.

Resources

Receive “Bad Size” error when I try to delete Accessories in product: http://www.prestashop.com/forums/topic/177462-solved-receive-bad-size-error-when-i-try-to-delete-accessories-in-product/

GitHub PrestaShop v1.4.11.0: https://github.com/PrestaShop/PrestaShop-1.4/commit/38c46b70f4cef35f67a9ce55d5a5cde0e22008f4

The post PrestaShop ‘Bad Size’ Deleting Product Accessory appeared first on My Web Development.

For example, I require a cms page to be in both English & Spanish, and even though I’ve enabled the language packages, some cms pages did not have dual tables for the ID’s within the Data Base..

PrestaShop > BO > Tools > Languages

English ID = 1
Spanish ID = 6

In phpMyAdmin, select the portion to ‘copy’ the table that you want to duplicate for your other language.

CMS Table in English

In your newly copied table, adjust your contents language and change the id_lang to your language’s variable; in my case it’s #6.

Adjust Copied Table

After adjustment, your new table should appear with the new language id.

New CMS Table in Spanish

Fairly simple and effect!

The post phpMyAdmin ps_cms_lang Copy Table Row appeared first on My Web Development.

If you have attempted to configure the CMSblock and upon editing, there are no select cms pages to chose from, and if you attempt to save, an error generated “You must choose at least one page or subcategory to create a CMS block.”

No CMS pages are listed

The problem is within the web browser Google Chrome.. If you use IE or Fire Fox, the CMS pages become visible and thus are allowed to continue with your process.

Resources

CMS Block – No Choice of pages: http://forge.prestashop.com/browse/PSCFI-612?focusedCommentId=71740#comment-71740
No Page Choices for CMS Block: http://www.prestashop.com/forums/topic/87240-no-page-choices-for-cms-block/page__st__20

The post PrestaShop CMSblock error “you must choose…create CMS block” appeared first on My Web Development.

In attempt to translate a module, I experienced suhosin warning.
“The server is using the suhosin patch for PHP, which limits the maximum number of fields to post in a form; 1000 for suhosin.post.max_vars & 1000 for suhosin.request.max_vars.
Please ask your hosting provider to increase the suhosin post and request limit to 5003 at least. or edit the translation file manually.”

After some research, the solution was to do the following.
Step 1.) I used notepad++ to create a php.ini file with the following code:
suhosin.post.max_vars=5003
suhosin.request.max_vars=5003

Step 2.) Using FileZilla, I FTP the file to the admin directory of PrestaShop.

Step 3.) Refresh browser and it works now!

Resources

Warning, your hosting provider is using the suhosin patch for PHP: http://www.prestashop.com/forums/topic/110663-solved-warning-your-hosting-provider-is-using-the-suhosin-patch-for-php/

The post Warning, your hosting provider is using the suhosin patch for PHP. appeared first on My Web Development.

Example of the sitemaps labeling by ‘ID’:

The post Google Sitemap for PrestaShop appeared first on My Web Development.