Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Location
    Jakarta, Indonesia
  • Activity

mnelly's Achievements


Newbie (1/14)



  1. are you sure the minimum requirement of the open SSL is 1.2 ? I have checked with the bluehost technical support, he said to me they have not yet upgraded to 1.2 at this moment. I also checked www.openssl.org, the latest news on 7 Dec 2017 is 07-Dec-2017 OpenSSL 1.0.2n is now available, including bug and security fixes
  2. 1. Cache already cleared for 2 times. I didn't use the 1-click module. Actually, what I did was, i downloaded the newest version 1.7.24 from https://www.prestashop.com/en/download and then setup from scratch. After I finished all the configuration of 1.7, configure the classic theme, the shop parameters, tax, carriers, localizations, translations etc. and then i setup the products category, and the products data (pricing, images, discount, and so on). And then, i did testing on my localhost, and it was proven running perfect including the ordering process. And then, i upload all the files from my local \wamp\www\myfolder to the \public_html from the very beginning. So, there was nothing in the public_html folder (so, there should be no 1.6.x setup in that folder, as it was an empty folder before i upload everything). Regarding the indication wrong screen 1.7, I was curious, and i did google the look and feel of prestashop 1.7. It looks to me that the screen of the production backend screen is similar with my localhost and similar also with those google search results. The menus' name also looks the same, except that the submenus behave strange. I have no idea how should it look like........ If possible, please explain what's wrong with the screen, so that i may be able to recognize it. 2. Debug mode --> i need to learn further what, how and where to start, as I never did this before, as i am not really expert in this area... Just a dummy user, "debug" is something sounds a bit scary for me 3. yes you mentioned the Open SSL should be 1.2 or higher....... i may have to find out in the bluehost cpanel how to upgrade this one. No experience on this. Thanks for your advice, Hope i can get thru all these issues.
  3. i have changed the PHP.ini as advised. The back-end submenus still doesn't work, keep loading and loading. In addition, now the frontend site, all the product images can't show up. If somebody knows how to fix this, please let me know... This is my latest config DATABASE INFORMATION MySQL version: 5.6.32-78.1-log MySQL server: Tables prefix: ps_ MySQL engine: InnoDB MySQL driver: DbPDO STORE INFORMATION PrestaShop version: Current theme in use: classic Languages enabled : English and Indonesian Single Store PHP config PHP version: 5.6.32 memory_limit = 512M max_execution_time = 300 max_input_time = 300 upload_max_filesize = 20M post_max_size = 20M max_input_vars = 10000 allow_url_fopen = on safe_mode = off The below settings by default already enabled on the Bluehost server (I don't configure these) JSON enabled version 1.2.1 CTYPE functions enabled CURL enabled OpenSSL enabled version 1.0
  4. Yes, it is . STORE INFORMATION PrestaShop version: (I didn't type this, but copy paste it from the screen Advanced Parameters. I can still click the menu, but not the sub menu. The first sub menu of Advanced Parameters is "Information". That's the version ) I will try your advice.........
  5. I have migrated my new site using PrestaShop v. (the newest version until this date (Jan 1st,2018). On my localhost, it works well both back-end and front-end. On the server, the back-end sub menus doesn't work. It keeps loading. When you hover to the menu (e.g. Orders or Catalog or Customers or whatever), the submenus doesn't show up. Hope somebody know how to solve this issue. Need help.......... Thanks. This is environment of the server: SERVER INFORMATION Server information: Linux #1 SMP Mon May 22 17:31:11 EDT 2017 x86_64 Server software version: Apache PHP version: 5.6.32 Memory limit: 2048M Max execution time: 1000 Upload Max File size: 64M DATABASE INFORMATION MySQL version: 5.6.32-78.1-log MySQL server: Tables prefix: ps_ MySQL engine: InnoDB MySQL driver: DbPDO STORE INFORMATION PrestaShop version: Current theme in use: classic Languages enabled : English and Indonesian Single Store
  6. Aha... thanks, you're right........ forgot to turn off the Friendly URL. Just updated the ps_configuration PS_REWRITING_SETTINGS to 0 (because i can't access the backend menu Shop Parameters). The site is now WORKING with some broken product images (don't know why). I would like to regenerate the product image, but the backend submenus is not working, it keeps loading (the circle cursor keeps loading). I guess it would be better to post a new topic for the backend submenus issue. Thanks very much !
  7. I have switched the server to Php Version 5.6.32 and already setup the Php.ini file. Thanks for the suggestion, at least it moves forward....... The front office error is different now : "The requested URL /en/ was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request." Do you have any idea, what's wrong with the /en/ ? It's the english page. I set the ps_shop_url without /en/ , only www.domainname.com. Now, the backoffice works with many strange behaviour. The submenu doesn't work at all. So, when you mouse over the menu, the sub menu doesn't show up. When i clicked the menu catalog, Http error 500 pops up. May be somebody can give me some advise. I guess this version, configuration on the business side is easier, but technically so complicated to get it up and running. I am thinking to stay with the 1.6 and wait for the next better, more stable and technically easier to get it up and running Thanks
  8. Localhost PHP version is 5.6.25. On the server side is 5.4.24. Is this a problem ? i have been using this exact PHP version, since the earlier versions of Prestashop 1.5.x and 1.6.x, and it works well.
  9. I have finished with the configuration of the latest version Prestashop v1.7.2.4 in my local and already tested well. I use the default classic theme. I really like the simplicity configuration of the new version 1.7, it's really simple and fast, comparing with the older version 1.5.x and 1.6.x, although there were still bug and workaround required in some areas. But today, i am stuck in the last step to migrate from the local to the server to make it live. So, these were the steps that I have done today : 1. uploaded from my local wamp server to \public_html 2. copy all my data from the local to the server (using the PhpMyAdmin export and import functions) 3. i have set the database name, user and password in the app\config\parameters.php 4. i have also updated the ps_shop_url with my website domain name (e.g. www.domain.com) 5. i have deleted the htaccess file Then, i tried to access the site. The result is this error message in both front office and back office : This page isn’t working, currently unable to handle this request. HTTP ERROR 500 I checked the error log in public_html, It shows : PHP Parse error: syntax error, unexpected ':' in public_html/config/config.inc.php on line 125 The coding of line 125 config.inc.php is : define('_PARENT_THEME_NAME_', $context->shop->theme->get('parent') ?: ''); Can somebody help me to solve this issue ? I am not expert in programming. Need help.......... Thanks.
  10. I had the same problem in version (just download and configure it, the newest version until Dec 2017). I found out this problem can be solved by disabling the "web only" or "online only" of ALL the products (Has to be ALL products). So, in the product catalogue, you can find the "web only" check box in the last tab ("options"). You need to change it all the products one by one. But, if you are using upload mechanism, it is on the column AU in your csv upload template file, just change the value to 0 for all the products, and then upload all the products. Make sure that your csv file has all your latest product information including the pricing, discounts, quantity, etc. It is solved for me and temporarily this workaround is okay for me. Hope it helps.
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More