Jump to content

CrossY

Members
  • Posts

    201
  • Joined

  • Last visited

Profile Information

  • Location
    Netherlands
  • Activity
    User/Merchant

Recent Profile Visitors

6,534,598 profile views

CrossY's Achievements

Newbie

Newbie (1/14)

15

Reputation

6

Community Answers

  1. Solved it, I think. I hooked the review module to the footer, but above the module which actually shows the variable/content.
  2. Hi there, I've recently started using a store review module. I'm displaying some of the variables in my footer, however these variables are only loaded on the homepage. When I view another page, the variables are left blank because they arent loaded. Now, I understand the concept of variables, but i'm not a programmer so I have no idea where to start. Is there a (relatively) easy way to make these local/home variables global, so I can use them throughout the whole shop? Using PS 1.6.11. Thanks in advance!
  3. Bug seems to persist over various Prestashops I manage on entirely different servers. It seems to be fixed on 1.6.1.5, but the file structure is different on 1.6.1.10 which appears to still have this bug in it. Any fix for 1.6.1.10? Would be greatly appreciated!
  4. I've mentioned this before, and i'll do it again: stop pushing development versions of Prestashop to every day consumers. Prestashop 1.7 is still in development, however a regular customer stopping by the front page is already getting 1.7 downloads and demo's. Without even going into the back-end of 1.7, the front end is bugged on multiple places. How can you place a buggy (looking) demo in the attempt to get them to use it? http://fo.demo.prestashop.com/en/stores - Stores images are broken http://fo.demo.prestashop.com/en/3-women - Category image is stretched http://fo.demo.prestashop.com/en/content/4-about-us - Image is broken http://fo.demo.prestashop.com/en/best-sales - Search icon messed up Not to mention the sloppy design work. Low quality images (in lightbox) and page redirects you to homepage if you sub to the newsletter. What year is this? How can anyone OK this for public use? Updating PS is still virtually impossible without rebuilding your shop or breaking half of the features. Simple overwrites or child themes are not available. I can't see myself building another shop in Prestashop, not even solely because of the low quality 1.7 but because you push development products to (unsuspecting) users time and time again.
  5. I've found that it only shows when the product has features/combinations. Is there a way to show this even if the product doesn't have any of those?
  6. Hi there, I've copied a theme from another shop, but on the new shop i'm not getting the "amount selector" in the product page. I can add one item at a time with the "Add to cart" button, but not multiple at a time. Is there a setting for this i'm missing? Attached a screenshot of what i'm not seeing in the new shop. I'm using 1.6.1.7 -- Thanks in advance! Best, D
  7. Hi there, I've been having this issue after moving my Prestashop from one host to another. I couldn't log in to the backoffice even though the password was correct (if it wasnt, I'd get a different error). It simply refreshed the page but didn't get me in to the backoffice. I've seen many people with this problem while Googling. I tried all solutions: - Clear cache - Clear cookies - Change cookie settings in DB - Try different browsers - Create new admin user through DB - Change admin password through DB - etc. etc. Nothing worked. However, changing the PHP version of my webhost solved it. I've never seen this suggestion in any other topic, so I figured it might help some people in the future struggling with this issue. I had this issue on Prestashop 1.5.5.0. My PHP version was at 7.0 for my other websites. Changing it to 'native' worked. 5.6 broke it again, 5.5 solved it again. Try changing your PHP settings to see if this makes any difference for you. Good luck!
  8. People are having very different experiences. I'm still wondering what the security risks/update actually mean and how necessary it is to update. Anyone has a word on that?
  9. That's an odd change of mind, Sathyaseelan133. I think it would be helpful if you don't post such advice unless you are certain about it. Thanks rampage.rado and MacRoy, i'll try to update with a backup and mirror of my site first
  10. Thanks for the reply. How serious should I take the security concerns then?
  11. Hi there, I don't really understand the patch notes for this version. It says security release, how recommended is it to install this one? If it's hard to recommend whether to do it or not, maybe someone can explain what the changes entail? Fixed bugs: * BO : (f19ae86) Solved problem with non-unserialized filters datas Improved/changed features: * CORE : (e12c209) Fix a case where $context->smarty could be undefined We are currently on 1.6.1.5. Thanks in advance! Best,
  12. Hi mdekker, Thanks for your assistance. This did not solve the problem. One of the installations is pretty much brand new and it didnt make a difference there either. Any other suggestions? Edit: Did some futher digging, I found these database fields which seem to be empty, are they supposed to be: I have them filled out in the backoffice, but I can't seem to update them either (after saving the page resets and it shows the old configuration):
  13. Hi there, It appears as though my emails from the shop have stopped working with 1.6.1.5. I 'recently' upgraded two stores and they both share the same problem now, even though it worked fine before. When trying to reset passwords or anything, an error pops up that 'email has been unable to send'. The same happens for adjusting order statuses which have an email attached to it. The same happens when I send out a test-email though the email config page. I've tried with SMTP server as well, it gives an error when sending the test email: Any way to find out whats going on, and fix this? Thanks in advance! Update: configuring emails now also acts weird. It is stuck in some SMTP settings, whatever I try to change it to, after clicking "SAVE" it just refreshes and has the same content as before. It is now sending the test email with these (semi-)correct SMTP settings, but the status emails still give the same error as before. Password recovery through the front-end also returns the same error as before.
×
×
  • Create New...