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.

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.

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.

Internal Server Error 500
No response from subprocess (php) with exit signal: 127
cpsrvd/11.35.0.4 Server at myhost.name.com

This issue can be fixed by logging into your server and running the bellow command through Putty

/scripts/check_cpanel_rpms –fix

The post No response from subprocess (php) with exit signal appeared first on My Web Development.

However, in phpMyAdmin section, I noticed the importation duplicated the products five times; each with a different id_lang.  This seems overboard on how many products are consuming the php memory and should only be uploading the one language as per selection in BO.

In the BO upon importing your CSV, you can select the language from a drop down menu.  The 5 languages that are offered as options within the drop down menu are consistent with the importation found in phpMyAdmin. It appears that the CSV importation, did so for all 5 languages and not the one selected one (English).

According to PrestaShop’s Bug Tracker the CSV imports all languages as a default behavior.: http://forge.prestashop.com/browse/PSCFV-4972

After some more research and troubleshooting, I decided to remove the languages instead of disabling them and it works!

The post PrestaShop CSV Import appeared first on My Web Development.

Investigated file /classes/ImportModule.php

The syntax NULL is caps on v.1.4.4.0 and small-lettering on v.1.4.4.1
17 protected $_link = NULL;
39 if ($this->_link != NULL)

There are roughly 100 files inside /classes/, so I decided to copy & paste the entire directory with files from v.1.4.4.0 over to v.1.4.4.1.. The copy/paste method completed and did not disrupt the Back Office, so that’s a positive step; however, CSV import still generates Column Function Error: Column function (b) { var a = this.indexOf(b); if (a != -1) { this.splice(a, 1); } return this; } must be set

I also copied & paste the following “/admin/tabs/AdminImport.php” and the method did not disrupt the BO, however it also did not resolve CSV import error either.

I’ve posted on the PrestaShop forums, to no prevail: http://www.prestashop.com/forums/topic/207574-csv-import-results-in-column-function-error/

Eurika,
I now know what is causing my CSV import to stop working; it’s my custom module!!!!

The post PrestaShop CSV Import Generates Column Function Error appeared first on My Web Development.

According to PrestaShop documentation, the typical upgrade method has depreciated and is not recommended.  There is a free module ‘1-click-upgrade’ from addons.prestashop.com that is recommended, however good luck in having it work!

I’m left with a couple of options.
a.) fix the module
b.) perform depreciated upgrade

However, before I attempt anything; I want a complete copy of my Live PrestaShop (LPS) store over to a Testing Domain (TD).

Step 1.) Download and install the version of PrestaShop that you are using on your LPS onto your TD.

Step 2.) Copy any unique directories (mails, img, theme, modules, etc) and files from your LPS over to your TD and overwrite with unique ones.

Step 3.) Now, export prestashop database phpmyadmin from your LPS over to your TD.

Step 4.) On your TD, copy the _COOKIE_KEY_ located in /config/settings.inc.php and update phpMyAdmin with your _COOKIE_KEY_ and password then run SQL command. Instructions on how to change password for user via phpMyAdmin.

Step 5.) Access the BO of your TD.

Step 6.) In the BO, a warning will display that you are connected with the following domain ‘your-LPS.com’, you have to adjust in “Preferences > SEO & URLs” and set to your TD.

Step 7.) In the BO, generate a new .htaccess file “Tools > Generators”.

You now have complete copy of your LPS onto your TD.. Make a backup and get to work!

NOTE

Data migration is possible using phpMyAdmin with similar versions of PrestaShop v1.4, however data migration between different versions are problematic.

Resources

PrestaShop_v.1.4.x /classes, ImportModule.php: http://scm.prestashop.com/browse/PrestaShop_v.1.4.x/classes/ImportModule.php
CSV Import improvements, change logs: http://scm.prestashop.com/browse/~br=root%3A/PrestaShop_v.1.4.x/docs/csv_import/products_import.csv
1 Click Upgrade Module: http://addons.prestashop.com/en/administration-tools-prestashop-modules/5496-1-click-upgrade-autoupgrade.html

The post How to Export PrestaShop database phpMyAdmin onto a Testing Domain. appeared first on My Web Development.

When I installed prestashop, I thought I had selected to install with modules disabled. However, all the bells and whistles where included with my fresh install.. I figured, I would begin disabling/uninstalling all the unnecessary modules and in doing so, I came across a few bugs.

Modules that won’t uninstall:

1. Cart Block
2. Footer
3. Block Payment Logo

After these 3 bugs, I decided to install PrestaShop onto my local WAMP server..

I installed 2 versions onto WAMP server; my current store version is 1.4.4.1 and before I upgrade over to 1.5.2.0 I need to see if there will be any problems..

WAMP Server: PrestaShop V1.4.4.1 & V1.5.2.0

In both installations, no product demos where selected and yet, V1.5.2.0 enables some of the demos with V1.4.4.1 displaying correctly.

Anyhow, I imported my data using phpMyAdmin and I didn’t see my data listed in PrestaShop?
This was because I had my custom theme enabled instead of PresthaShop’s default theme.. Apparently, it’s buggy; I reverted to PrestaShop’s default theme and all was good

Well, apparently PrestaShop has some major differences in how 1.5 is treated, compared to 1.4.  I looked into what version of PrestaShop carries the CSV import bug fix and according to PrestaShop’s tech support, that fix is presented in 1.4.9

I’ve tested 1.4.9 and the CSV import bug still exists.

I posted on PrestaShop forum, where a solution was reached for one user (axel_afp): http://www.prestashop.com/forums/topic/97785-import-error-prestashop-14/page__st__20__gopid__1002780#entry1002780 Of course, the image that displays the resolution was not accessible and I’m hoping that he will comply with updating the post.

Resources:

Importing CSV generates error in Column Function: http://forge.prestashop.com/browse/PSCFI-6101

The post My PrestaShop v1.5.2 Bug Report appeared first on My Web Development.