Here are the most common connection issues and solutions:
If not done yet, please read and follow all steps of the include readme.txt file. Particularly, be cautious to copy paste the connection parameters from the connection module configuration page.
In 98% of the escalated cases, people included by mistake a leading space while doing this copy paste.
Symptom: Connection looks ok but tables remain empty
Most probable causes/solution: -Folder access right: Change the access right of /modules/MPRApplicationsConnect to 755 and its files to 644. Primary root cause if hosted at OVH. -The name of the database or the database prefix entered are not correct. Please check for leading space and typo errors. -The value set in the language id is not correct. Leave it to 0 or try 1 for English, 2 for French,… -The choosen key does not respect the rules: 12 to 16 letters, only CAPITAL letters, no numbers, accent or special character, no space
The categories are displayed, but not the products:
-Have You correctly activated the link between the two tables, by clicking the button representing the gears? -The value set in the language id is not correct. Leave it to 0 or try 1 for English, 2 for French,… -error very common: you have not left a pre-filter enabled on the table of products (fields above the table)?
The categories and the products are displayed, but some characters are replaced by question marks (?):
-If It occurs following an update of PrestaShop, uninstall and reinstall the sitologapplicationconnect module (aniennement MPRApplicationConnect) -If You are PS1.5 or more, do not check the "Force UTF8 encoding and decoding" -Check That the choice of the alphabet is well suited to characters used in the default language -Before PP version 6.1 and 4.1 of PC, the module does not support Unicode encoded bases. From these versions always choose the alphabet "UTF8 (Unicode)"
Simple red cross, without explanation or randomly ok connection. And when the connection goes, it quickly went on random errors may explanatory (a simple red cross without explanation).
The red cross, without more info, means that SQL error came without being due to the application. We know three different causes:
Problem stability of the network connection from the PC to the server. The timeout or micro connecting cuts come at random, which in effect corrupt SQL queries.
-Try From another PC, ideally with another network cable (no wifi) -Regarder Server-side logs to see if there are cuts or micro timeout .. If this is the case, solve with the help of your web host. -Check Also the setting of the server is not too restrictive on the execution time and the maximum length of SQL queries.
Some server are protected against DDOS attacks. Sometimes this kind of protection do too much work and also blocks, randomly SQL queries our application.
-No Choice but to pause the DDOS protection. And look for a more efficient and customizable.
Some anti virus like Avira and Kaspersky, can block network access.
Try at first to disable the "Web or WWW protection of these anti virus", or better exclude the application of this protection system.
The connection fails (error message indicating the)
Connection-module (MPRApplicationsConnect previously sitologapplicationconnect now) not installed or installed incorrectly or too old (always use the latest version available). Uninstall, remove and re-install. -In Particular, it is very important to uninstall the plug before making Prestashop migration and re-install the new version of PS. -Cases Classic, bad domain configuration in Prestashop. Load the Home page back office, if a domain configuration error is indicated, correct it in the "Settings> SEO and URLs". -Cases Vicious met once, on a multi-boutique Prestashop: the sitologapplicationconnect Module was installed and activated in one of the shops, not in the default store in particular. -URL Incorrect: Check the URL to enter (included in the connection module configuration window) -In Especially if you use subdomains, including the subdomain to the URL (even if the sitologapplicationconnect module does not include it in the URL provided. -With Ps1.5: Add to Facebook www. to the url provided by the module or otherwise remove www. This may be necessary if your domain is redirected. Incorrect Keyword -The Database name contains dashes ("minus" sign). With older versions of PrestaPricing and PrestaCatégories, put the name of the database between two `` (that is no longer required with version less than a year). -On A Linux server to the / modules / sitologapplicationconnect 755 and 644. Possibly content (not critical) also put the / tools / smarty / complete 777. -On A Windows server, ask the system engineer to provide equivalent rights of access to these folders and files. -Désactivez Web protection of your anti-virus, or better exclude the application of this protection system. -If You are on a Mac with a Windows emulation, so check it out Windows MAC access to the network. -New Highly technical cases appeared from version 6.0 and above in 6.1.1 and 6.1.3 until the beta included: some servers running PHP badly needed orders mb_ type for unicode decryption requests sent encrypted . In short, it refuses to connect (even in "unencrypted" mode which acted only on downlink data) and it is very difficult to guess what happens. This type of problem is now solved from the beta version 6.1.4 and 4.6.a connection module, choosing the mode "Neither encrypted or compressed" mode or "compressed but not encrypted," that avoid now encrypting queries rising ..
The research http connection remains blocked for several minutes, then an error message indicating that the server did not respond (timeout) appears.
-Check The URL. -Try With and without www. -Cases Increasingly common: There is a blocking outbound network access by the antivirus ("Protection WEB"). Fairly standard with Avira. Disable web protection of the latter, or better exclude the application of this protection system.
The license check fails after about twenty seconds, and then connect to your server also fails. This indicates either that the PC is no network or the software can not access the network.
-Check Your network connection. -If Possible, switch to wired network (up to 5x faster then) -If Your box or your local network includes a proxy server, configure the "Proxy" of the application with the user and the proxy password tab (see below). -Close And restart the application, but this time as an administrator (right click on the icon and select "Run as administrator")
Fatal error line 35 ...
-Re-Check the name and prefix of the base
Error message "Error: PS Version can not be read" ("Error: PrestaShop version number was not found in the database.)
Possible causes: -Mauvais Entered parameters, such as email and password login to back office. -Mauvaise Installing the connection module (it should add the base number in the table "configuration") -A Firewall server side lights prevents access to the database. -A Classic case, a PS1.5 platform, multi-boutiques: Verify that the alias of the main shop URL, declared in multi-store back office settings, while pointing to the true either field the "site" (same domain name as the back office). Otherwise, when PrestaPricing / PrestaCatégories / AutoPresta try to connect by calling a PHP script sitologapplicationconnect module (formerly MPRApplicationConnect) Prestashop redirects (via the alias) URL and the script is not found. The connection is indicated as successful in the log window, but it fails when reading the table "Configuration". -New Highly technical cases appeared from version 6.0 and above in 6.1.1 and 6.1.3 until the beta included: some servers running PHP badly needed orders mb_ type for unicode decryption requests sent encrypted . In short, it refuses to connect (even in "unencrypted" mode which acted only on downlink data) and it is very difficult to guess what happens.
Solutions: -Check The email and password login to the back office. -Désinstallez, REMOVE THE DIRECTORY sitologapplicationconnect, and reinstall the V4.6.a connection module (or later), configure. Try again. -Check The table configuration of your database does contain a line called "MPR_PS_Version" and whose value is the version of your PrestaShop, 5 digits without "points. Example 14510 for the 184.108.40.206 release. If this parameter n ' is not present, add it manually. -In Particular PS1.5: Add to Facebook or otherwise remove www. to the url provided by the module. This may be necessary if your domain is redirected. -Check As access rights to the files, as explained a little higher. -If It occurs following an update of PrestaShop, uninstall and reinstall the sitologapplicationconnect module. -New Cases from version 6 and the transition to UNICODE. To use the "encrypted data" requires that the PHP module "mbstring" is enabled on the server (see here: http://php.net/manual/fr/mbstring.installation.php) -Go To the beta version 6.1.4 and 4.6.a connection module, choosing the mode "Neither encrypted or compressed" mode or "compressed but not encrypted," now that avoid encrypting rising queries. .
Error message "SQL Error" Check your syntax near SHOW TABLES ... "
Possible cause: encryption or decryption problem queries. Solution: Replace the encryption key with another value (connection module side and side application), carefully observing the instructions provided on the number of allowed characters and characters. Try the default (AABBCC ... HH)
Rare cases: If your server application to identify to access the pages with a user name and a password update, you must specify these parameters PrestaPricing or PrestaCatégories.
Prior versions 5 and 3 respectively, this thus replacing the URL with this string of characters: user: password @ URLsanshttp
Eg if the URL given by the connection module is http://mondomaine.com/boutique/, Toto is my logon and password is monpass, enter: toto: [email protected]/boutique/
In current versions, the login window is enriched with two new fields, to enter the user and password any http. So no need to change the URL.
Internet connection through a proxy server
If your Internet connection is through a proxy server, you can configure our applications to automatically connect. To do this, simply fill out the requested parameters (proxy server address, login name ...) in the Proxy tab of the connection window.
Error on SQL id_tax
This can happen after changing the version of PrestaShop, uninstalled without the prior connection module. Disable, uninstall it, delete it and reinstall it completely.
Server Error 500
-Fixed Access rights to the connection module folder (see above) -disable Safe_mode mode in the administration panel of the server.
Failed to Connect on a local server (eg with EasyPHP)
Depending on the configuration of Easy PHP, it may add the port number in the URL provided by the module. Ex: The sitologapplicationconnect module indicates that you use this URL: www.mondomaine.com/mondossier/ Use instead www.mondomaine.com:8080/mondossier/ (if 8080 is the port used by EasyPHP)
On a PrestaBox server can not install the plug
There is no known workaround (other than through "Modules Manager", other module that is no longer installable either, but was at a time through the themes), PrestaShop has shielded this solution for prevent installation of default modules not included in their offer. No comment. Yet we have been able to verify on a PrestaBox equipped with "Module Manager" PrestaPricing works very well on this platform, once installed.
Error on line 18 of the treatment method URLDecrypte. You called Charact. The specified ASCII code (-83) is invalid. It must be between 0 and 255.
Two known causes: -File Ovhconfig.php, forcing the activation of php 5.5 that plant. Board in PHP 5.4 resolves the issue. -The Error message indicates a problem with the server encrypt / decrypt data. In this case, try at first to simply change the encryption key in the MPR module and in PrestaPricing. Try for example the default AABBCCDDEEFFGGHH.
From the 220.127.116.11 version of PrestaShop, crash the "Modules" in the back office, indicating the name of MPRApplicationConnect module is incorrect.
This is due to the fact that from this version of PS, the names of the modules do not contain uppercase letter. The MPRApplicationConnect module therefore is no longer compatible. I replaced it by sitologapplicationconnect Module be installed instead. To work with this module, I recompiled and uploaded new versions of PrestaPricing (6.0.6), PrestaCatégories (4.0.4) and AutoPresta (2.5.0). Please note that the retro compatibilté could not be retained. Older versions of these modules can not be used with this Prestashop and future following.
Failed to install module or its sitologapplicationconnect MPRApplicationConnect replacing in the back office of PrestaShop CLOUD.
This is normal since these modules are not available on PrestaAddons. But this is not a problem, because since version 4.2 these modules, they no longer need to be installed to function. Read or re-read the installation guide readme.txt included with your application.