Jump to content

jsherk

Members
  • Posts

    52
  • Joined

  • Last visited

jsherk's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. Okay so I was advised that possibly the issue is related to me using PHP v7.3.8 since v1.7.6 of Prestashop is only compatible up to PHP v7.2. v1.7.7 of Prestashop will be compatible with PHP 7.3
  2. Okay so I was advised that possibly the issue is related to me using PHP v7.3.8 since v1.7.6 of Prestashop is only compatible up to PHP v7.2. v1.7.7 of Prestashop will be compatible with PHP 7.3
  3. Okay so I was advised that possibly the issue is related to me using PHP v7.3.8 since v1.7.6 of Prestashop is only compatible up to PHP v7.2. v1.7.7 of Prestashop will be compatible with PHP 7.3
  4. Where do I report BUGs in prestashop? I created a login on forge.prestshop.com however when I try to CREATE a new issue for Prestshop 1.7 it says it is for DOCUMENTATION issues only and there is no way to select anything else. Thanks
  5. And (for the third time), the installation went well as far as unpacking and creating database and connecting to the database (pretty standard for any php installation), and was able to login to the admin backend. This was the third installation issue that I came across: PROBLEM: The next issue I have is that, even with the Enable SSL on all page set to yes, the backend Admin area will still allow you to login using plain HTTP. It does show you a warning at the top of the login screen, but this again seems to be a bug. It should just automatically redirect to HTTPS. SOLUTION: I have not yet found the solution to force HTTPS on the backend admin login or to force SSL use on all backend admin pages. I have the bookmarked link to admin backend with https which should prevent me from accidentally using HTTP but there should be an option to ENABLE SSL ON ALL BACKEND ADMIN PAGES.
  6. So again, the installation went well as far as unpacking and creating database and connecting to the database (pretty standard for any php installation), and was able to login to the admin backend. This was the second installation issue that I came across: PROBLEM: The next issue I had was that when I tried to access the frontend store, I got a PAGE NOT REDIRECTING error. This took some googling and figured out that it was because I was trying to access the frontend with HTTPS instead of HTTP. This would seem to me to be a bug as you should either be able to access one or the other, or https should at least rediect to http, or at a minimum show a page that says "please use http and not https to access front end". It seems that prestashop could handle this scenario better. SOLUTION: One solution is to obviously just use HTTP all the time, however this would not eliminate the error if somebody tries to access the frontend via HTTPS. So the only other solution is to force the site to always use HTTPS. Go to CONFIGURE > SHOP PARAMETER > GENERAL and then set ENABLE SSL ON ALL PAGES = YES. This will force all frontend http requests to redirect to https. As a side note, this option should probably be renamed to ENABLE SSL ON ALL FRONTEND PAGES because it does not force SSL on the back admin pages.
  7. So the installation went well as far as unpacking and creating database and connecting to the database (pretty standard for any php installation), and was able to login to the admin backend. However this was the first problem I came across: PROBLEM: The issue is the "Launch your shop" helper thing that popped up. I clicked on LATER, but the problem with this is that it puts a block down in the bottom left corner (with the percent you are at and a RESUME button) and this block covers the Shop Parameters and Advanced Parameters so you can can not access those settings while it is there. I then clicked on RESUME and it asks me to add a product (which I did) and I saved the product, but it just keeps coming back to the ADD A PRODUCT screen and I can not seem to figure out what it wants me to do, so you are forever stuck on the ADD A PRODUCT screen. SOLUTION: It turns out that this is the WELCOME MODULE forcing you to do this, so the only thing I came up with was to disable that module. Go to IMPROVE > MODULES > MODULE MANAGER and then type WELCOME in the serach box and then click on DISABLE to shut it off. Click on DASHBOARD or refresh your screen and the RESUME BLOCK in the bottom left corner will disappear.
  8. I have a custom module I am developing and it is almost done and I have it working pretty good on v1.4. On v1.5, when I go the modules tab, it works fine, but as soon as I put my module into the modules folder, when I try the modules tab, I get a completely blank screen. When I remove my module from the folder, the modules tab works fine again. I use FireBUG on Firefox and it shows no errors. I also have @ini_set('display_errors', 'on'); and define('_PS_DEBUG_SQL_', true); as well in config.inc.php. And also there is no error_log file generated. Any ideas what else I can check? Thanks
  9. I posted bug report here: http://forge.prestas...owse/PSCFI-4488 TAGS: email address duplicate email
  10. I have noticed that in the Back Office > Customers > Add New that you can add a new customer and use an email address that already exists in the system. So I wonder if these are bugs or designed this way on purpose?
  11. I think I read somewhere that v1.5 is scheduled for January sometime... can anybody else confirm this?
  12. @Aldeag- I think you are saying that the current POS you use is NOT incorporated into Prestashop, so you have two different systems that do not talk to each other? Is that correct? What POS are you currently using?
  13. @Aldeag- I think you are saying that the current POS you use is NOT incorporated into Prestashop, so you have two different systems that do not talk to each other? Is that correct? What POS are you currently using?
  14. Yes, 1.4 is more consistent (stable). If you need a shop up and running soon (before the end of January) then use 1.4. If you can wait until February then you could wait for 1.5 to be released.
×
×
  • Create New...