jwzumwalt

Just thought I would add my two pennys worth. For three days I have tried calling the us phone number and two days ago I sent a pre-buy email requesting clarification about one of the themes. I have tried to reach "sales", "support", and the "operator". It does not look like Prestashop USA has a ligitimate presence. This is apparently a dead number 1 (888) 947-6543

Solving this problem depends on your web hosting provider. Some hosting companys just require a php.ini file in the PS root directory such as ./store/ with the following line - memory_limit = 128M Others have php config files in custom locations, for example one host said: "We have set necessary PHP settings. You may find them under /cgi-bin/ folder. Please note that in order to keep php.ini settings working 3 files should be present under your domain folder:" /cgi-bin/php.ini /cgi-bin/php53.cgi - should have 755 permissions /.htaccess - should contain strings below: AddHandler php53 .php Action php53 /cgi-bin/php53.cgi The php.ini has:

Yes, it does matter. Each major version of Prestashop is incompatible with other versions.

Use PHPMYADMIN on your website provider site to manipulate your MySql database - export than import your Prestashop database.

I have not got it working. I have several theories but nothing firm. My stats worked after several upgrades but stop at some point. The last thing I remember doing before it failed was try out the different stat modules. I suspect that possibly one of the other stat modules killed some configuration settings. It would be nice if someone that has stats working let us know what package they are using the Artichow module and stats is not working.

There is no sql query because the image is not stored in the database. The image is in a directory and is stored as an ordinary file

Thanks for the additional info "Intra". However I am on ver 1.4.9 and none of the "Image_xx" provides a directory path. There appears to be some type of linked list scheme between the tables, but I do not understand it

Importing products is quite simple using PHP and MYSQL. The two tables that need to be updated are ps_product and ps_product_lang. I have searched but never found where images are kept (or the link to them). I hope this helps.

Would the folks at Prestashop please create a 1.4.x (1.4.9) Forum Group. Many of us have invested $1000's of dollars into 1.4x with no upgrade path yet to 1.5. There is still lots of development and support files for 1.4x. In my particular case, 1.5 has not yet offered a template that meets my particular needs and so I will be staying with 1.4.9 for quite a while. I have over 3000 products and will not be upgrading until it is seamless.

It is for 1.4 I have not updated to 1.5 and probably won't for about 2yrs until it stabilizes. There are reportedly lots of problems with 1.5 and I have 1.4 working quite smoothly.

It is at http://doc.prestashop.com/download/attachments/1409083/PrestaShop-Developer-Guide.pdf

No, there has not been a solution yet. I have taken another look a couple of times but have yet to follow the whole problem. I have ended up fixing several other problems instead.

I have the same problem and noticed a history of problems with visitor information with 1.4x

If you can't login and start getting an error similar to... PHP Warning: base64_decode() has been disabled for security reasons in .... /store/classes/Rijndael.php It is caused because your IP Provider has disabled the base64_decode() function in your server. They must remove the base64_decode string from the disable_functions in the php.ini* config file. I created this short PHP test program and put it in my store directory while they tried to fix the problem. <h2>Test Code For PHP base64_decode()</h2> If the base 64 function works properly, you should<br> see <i>"This is an encoded string"</i> printed out.<br> <br> You are attempting to run this code... <div style="background-color:#def; width: 450px; margin-left:25px;"> <xmp> error_reporting(E_ALL ^ E_NOTICE); ini_set('display_errors', '1'); $str = 'VGhpcyBpcyBhbiBlbmNvZGVkIHN0cmluZw=='; echo base64_decode($str); </xmp> </div> <?php error_reporting(E_ALL ^ E_NOTICE); ini_set('display_errors', '1'); $str = 'VGhpcyBpcyBhbiBlbmNvZGVkIHN0cmluZw=='; echo base64_decode($str); ?>

Wonderful! Thanks! I found a alpha version of the doc and it was so full of errors I could not see why everyone was praising it... Now that I see the finished doc, it does look very helpful. Thanks again for the link.