markb

Thank you Antoine. I can confirm payment has finally been received. Feedback for Addons Team This has been a very frustrating experience - the frustration and stress caused by the missing payment was made much worse by the difficulty getting any response from the Prestashop Team - I initially contacted Addons on Friday 15th September, and then every working day after... It took until the 20th September to finally get a response. I understand there was an important event on - Paris Retail Week - but surely in this world of smart phone mobile communication, someone could have responded to acknowledge my issue.

Hi Bellini, Sorry to keep posting on your thread but this is just unbelievable... I still haven't received any response to my many attempts to reach out and communicate with the Prestashop Team: I have tried - Support requests via addons contact form - PMs sent to Community Manager of forum - Posts to the Addons Forum This feels like no-one gives a damn... it is so disrespectful. Any more ideas on how I might get hold of someone - anyone in the Prestashop Team? Thanks, Mark

Hi Bellini, Thanks for you answer - much appreciated! FYI: I already did contact addons support directly in the way you suggest - In fact this was the first thing I tried - Friday last week. I still haven't received any response. I also sent a PM to Antoine F the Community Manager yesterday at 3.37pm - but my PM thread states he still hasn't even read my message yet! I've already been in contact with my bank - they have checked and there is no sign of the transfer. My bank have asked for a federal tracking/reference number for the wire transfer - but no-one in Prestashop has even responded. So basically I really need someone in the Prestashop Team to contact me and supply me with their federal tracking/reference number for the transaction!!!!

Hi Bellini 13, Yours is an old post I know, but it seems that the process has not been improved any in the time since you opened it! I contacted the Addons Team initially on Friday afternoon 15th September to report that a transfer request has still failed to materialise 3 weeks after the request was made - the date of the last withdrawal is shown as 08/24/2017 and marked as paid in my seller account. It should have completed on the 31st August. The money has been deducted from my seller balance. I have yet to receive any contact other than the usual auto generated reply. I also sent a PM to the Community Manager for Addons - Antoine F - yesterday at 3.37pm. It is still marked as unread today. The amount in question is not insignificant. I would have thought this is a serious issue and would expect the matter to be dealt with promptly. Perhaps some-one in the Prestashop Team can get in contact with me and let me know what is happening with my money. Thank you.

Were you using Firefox? While attempting to install PS 1.6.1.0 the Firefox dev tools reports warnings of a possible Syntax Error: test for equality (==) mistyped as assignment (=)? in JQUERY. The installation failed exactly as described. In Safari the installation completed with no issue. Therefore perhaps this is a browser issue/browser setting issue.

If Tito's solution does not solve your particular issue Error "[Ajax / Server Error] textStatus: "error" errorThrown:"Internal Server Error" jqXHR: """ This states an Internal server error is the problem. Could be a number of things - but in essence it usually means a script did not complete. This can be because it could not find a required (include) file referenced in the script or that the script requires more memory than is allocated in php.ini settings or the script was taking too long and came up against a time limit imposed by either php or apache itself. You need to look at your apache error logs to get more information. If you do not have root access to the server you could try asking your hosting company to look. Even though you are using an upgrade rather than a fresh install the error could be caused by the same issues as below http://www.prestasho...tallation-fail/ http://forge.prestas...owse/PSCFV-2751

This states an Internal server error. Could be a number of things - but in essence it usually means a script did not complete. This can be because it could not find a required (include) file referenced in the script or that the script requires more memory than is allocated in php.ini settings or the script was taking too long and came up against a time limit imposed by either php or apache itself. You need to look at your apache error logs to get more information. If you do not have root access to the server you could try asking your hosting company to look. Even though you are using an upgrade rather than a fresh install the error could be caused by the same issues as below http://www.prestashop.com/forums/topic/187815-solved-prestashop-15017-installation-fail/ http://forge.prestashop.com/browse/PSCFV-2751

You never want to be the first with any new software release in a production environment. I think PS is great and sometimes people forget it IS FREE and OPENSOURCE and requires community support to debug. Having said that maybe PS should reword the statement on the download page? p.s. There seems to be two particular issues that are affecting many installs and upgrades - the server returns an Internal server error 500 either reporting this through 1. ajax (upgrade) Error "[Ajax / Server Error] textStatus: "error" errorThrown:"Internal Server Error" jqXHR: " Apart from information below also check http://forge.prestas...owse/PSCFV-4074 incase this is your issue. or 2. on screen (during fresh install) The installer script requires a minimum of 32 MB. See http://forge.prestas...owse/PSCFV-2751 Also the script execution time exceeds the default apache time allowed for a script (usually 30 or 40 secs depending on the server OS). The default for apache is usually set around 30 or 40 seconds depending on the version of apache and exact server setup etc.. This error is likely to affect many users as it is a default setting which probably cannot be changed by users of virtual hosts using Fast CGI. It will most likely require their hosting company to change this value - if they are willing. Those using Fast CGI on a dedicated host and who have root access to their server can change the setting by amending the correct apache configuration file: the exact file and directory for this will depend on server OS. Also to further complicate things there are usually multiple "includes" or locations for files which are read in and combined to create the servers apache configuration. Which one you edit depends on whether you want to make a change global or affect only one domain. Indeed sometimes a new file needs to be created and then the host file rebuilt with a command and apache restarted. Therefore make sure you know what you are doing is correct for your setup and OS before changing any settings. The directive which needs to be amended or added is <IfModule mod_fcgid.c> IPCCommTimeout 150 </IfModule> OR <IfModule mod_fcgid.c> FcgidIOTimeout 150 </IfModule> Depending on the version of apache. 150 is in seconds - this should be enough. This value (FcgidIOTimeout 150) needs to be amended in either httpd.conf or added/amended to a vhosts.conf file. Previous installers for PS have not required such long times for the scripts to complete, therefore perhaps the installer script needs to be reworked to get around this issue?

I know the thread is marked as solved, but moving the installation to a different server isn't really a solution in my opinion. I think the PS team maybe need to look at why the script takes so long to execute and balance this against the fact that the default time limit for a script to execute is 30 or 40 seconds as the default on apache. Not everyone can simply move to a different server. Previous installers worked within the default time limits therefore the ideal situation would be for the new installer to do the same. If it really is not possible to amend the script to work within the default time limits (but surely it can be) perhaps the minimum execution time for the script to execute needs to be stated as a minimum requirement along with the minimum memory requirement for the script to execute of 32 mb.

This sounds very similar to the problem in this thread. http://www.prestashop.com/forums/topic/187815-solved-prestashop-15017-installation-fail/page__p__929964__hl__install%20|%20fails__fromsearch__1?do=findComment&comment=929964 i.e. the installer is taking too long and comes up against the apache time limit for a script. I know the thread in the link is marked as solved, but moving the installation to a different server isn't really a solution in my opinion. I think the PS team maybe need to look at why the script takes so long to execute and balance this against the fact that the default time limit for a script to execute is 30 or 40 seconds as the default on apache. Not everyone can simply move to a different server. Previous installers worked within the default time limits therefore the ideal situation would be for the new installer to do the same.

rzhao The error you are receiving is a timeout as stated by Trip. Unfortunately the timeout is generated by apache not php when running in Fast CGI mode (i.e. settings in php.ini will not solve this, and no override in an .htaccess file will be able to change this setting). The default for apache is usually set around 30 or 40 seconds depending on the version of apache and exact server setup etc.. This error is likely to affect many users as it is a default setting which probably cannot be changed by users of virtual hosts using Fast CGI. It will most likely require their hosting company to change this value - if they are willing. Those who have root access to their server can change the setting by amending the correct apache configuration file: the exact file and directory for this will depend on server OS. Also to further complicate things there are usually multiple "includes" or locations for files which are read in and combined to create the servers apache configuration. Which one you edit depends on whether you want to make a change global or affect only one domain. Indeed sometimes a new file needs to be created and then the host file rebuilt with a command and apache restarted. I'm sure you are getting the drift that this is not a straightforward thing to change The directive which needs to be amended or added is <IfModule mod_fcgid.c> IPCCommTimeout 150 </IfModule> OR <IfModule mod_fcgid.c> FcgidIOTimeout 150 </IfModule> Depending on the version of apache. 150 is in seconds. This need to be amended in either httpd.conf or added/amended to a vhosts.conf file. Previous installers for PS have not required such long times for the scripts to complete, therefore perhaps the installer script needs to be reworked to get around this issue?

Hi mun 00093, You must scroll down the admin product page until you see "Click here to improve product's rank in search engines (SEO)" Then you will see where to enter the friendly url (or not so friendly in your case).

Hi Yzzy, You may need to log into your database with something like phpMyAdmin and edit the table called ps_category_lang to undo your changes. But I'm wondering what you could have done to get a Forbidden notice - this notice means you are trying to access a password protected directory. Did you change the Rewritten URL for index.php? You should leave this as blank!

You should be downloading from prestashop to get the latest stable version http://www.prestashop.com/en/download or if you have an older version and want to match missing files for a particular version you can get them here http://www.prestashop.com/en/developers-versions

Yes, this should work fine: download a copy from prestashop If I understand you right you are saying this file is missing from the latest download zip? If that is the case you can download the svn copy: http://svn.prestashop.com/trunk/ You'll see it listed.