Jump to content

RobbieBlokeToys

Members
  • Posts

    80
  • Joined

  • Last visited

Profile Information

  • First Name
    Robbie
  • Last Name
    Wallis

Recent Profile Visitors

456 profile views

RobbieBlokeToys's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare

Recent Badges

15

Reputation

  1. Just being a good citizen and explaining what happened with me regarding this problem. While testing a new theme and going back to the original one while I fix images etc everything was knocked out of whack. I thought i was just hook positions but Prestashop Checkout module was also affected. There is no way to know this from the back end. Everything looks normal. Customers couldn't place orders at all. This problem was solved by resetting the module and logging back into PayPal. I would recommend people try this first before moving other things around that might cause more problems. This is quite a stupid bug for an e-commerce platform to have. The priority should always be that customers are able to purchase. Everything else should be secondary to that. Prestashop should be hardened against the possibility any new module, theme, or minor change could simply close off all payment capability without warning. This should be added to the (already long) list of things PS needs to fix.
  2. Having the same issue. Trying to click to the next page of blog posts leads to 404. Don't suppose you've worked out a solution?
  3. I would love to know this also. I've been trying to work this out for the last 2 months and I cannot find any information about how to implement this. Neither Prestashop nor MaxMind seems to have any basic instructions for how to use their service and it's quite bizarre.
  4. More than a year later and we're experiencing the same thing, dozens of these fake accounts being created per day. Just because you only see three people reporting it here doesn't mean it's not a problem, it just means most people experiencing this aren't here reporting it on an English speaking forum, and if they do come here looking for help they're finding nothing of use (but snarky comments) so there's no reason for them to participate. And to clarify: 1. Adding captcha to forms reduces sales. It just does, it's a fact. Which is why people don't want to do it. 2. I have only 2 modules from a trusted developer, this problem existed before I added both. 3. Everything is up-to-date on my install.
  5. I figured it was being very generous in assessing online visitors, but it's disappointing they haven't rectified this over the many iterations of PS. We're currently enjoying a free trial of a live chat bot and I think we're going to go with the paid version. This shows us who is online and allows us to communicate with them in real time. I was skeptical, but we have actually seen a good increase in sales because of it. It's already paid for itself. I would recommend those who can try a live chat solution. That allows you to actually make use of online data.
  6. We've just installed a live chat module and it flags whenever there is a visitor on the site. Chat module: 5 visitors on site. Google Analytics: 10 visitors on site. Prestashop: 126 visitors on site. Even if we average it out over the "in the last 30 minutes" it doesn't match any other source of information. There's nothing you can really do with this statistic anyway, apart from assess usage, but if it's wrong (and it clearly is) that makes it completely worthless as a data point.
  7. Our store currently has two languages, EN and FR. When creating standard FEATURES (such as colour, length, material) and adding presets for those in both EN and FR, when adding a product and switching to FR to fill out all the translations none of the drop downs for the added FEATURES offer any of the RF translations we added when inputting. For example, when we created all the options under length, we added both the EN and FR (5 Inches, 5 Pouces) in the appropriate fields. Only EN options are available on the product creation pages. Does anyone have a fix for this? It's incredibly tiresome to have to manually add all these for every product, and it causes an error conflict in the Features section when saving.
  8. Thank you for the quick reply Daresh. I have send you a message.
  9. Hi, We previously had an automatic stock control module from our supplier which referenced a supplied XML feed every hour and updated our stock levels to match. They ceased to update this module for PS 1.7, so when we upgraded we lost the ability for stock levels to be automated. This is a problem, because it means we either have to manually check the stock levels of hundreds of items every day, or risk customers ordering items which are out of stock. We have an XML feed we can reference for current stock levels, but we need a module to routinely reference this feed and auto update our stock levels accordingly. I have been searching all the modules and I cannot find one which does this simple task, I'm also shocked that PS still doesn't have this feature as a core function, considering it's a primary need for almost all online retail where stock isn't held. I just need a module that lets me add the XML feed to reference, when to reference it, and what to change on the corresponding product (stock level). Anyone have any ideas? Thanks
  10. PrestaShop 8.0.1 PayPal v5.7.6 by 202 ecommerce Been happily using PayPal to accept payments for years, on Oct 1st it simply ceased to function. Testing checkout led to no progress beyond cart and the following message: "Error in PayPal An unexpected error occurred. Please contact shop administrator TRY TO PAY AGAIN" Went through numerous attempts with my hosting provider but nothing has worked. We deactivate the module which then led to numerous other issues which took 12 hours to get through. We're finally back to having the module there and working, but whenever a customer attempts to pay the pop-up box vanishes without loading and the "Error in PayPal" message appears. I have been trying to research this issue for 24 hours now and there is no information I can find to fix this. Any help/advice would be greatly appreciated!
  11. Unfortunately, creating a new store from scratch is going to mean losing all the links you had before, visitors will start going to a 404 error and you'll lose any ranking you had with search engines. It's basically like ending your business and starting all over again. We have been trying to find a way to upgrade the install to 1.7 while keeping all the data the way it is and just connecting the new PS to the existing database, but Prestashop has offered absolutely no information that I can find explaining how we can do this. Our hosting (hosting.co.uk) is being entirely unhelpful and seems completely disinterested. We would pay someone to come and fix this and get us up and running again if we could find someone. It basically looks to me as though we have to all start again from scratch if we want to continue using PS at all. Pretty soon nothing is going to work with 1.6 and if you want to add a new theme you'll be forced to start over with 1.7 anyway. This is all a mess, and it doesn't bode well for PS's future.
  12. I would really love to see a good explanation of how to upgrade from 1.6 to 1.7. I have been trying to do this after our previous active shop began to fail (by attempting the 1-click upgrade?) There doesn't seem to be any proper guide to follow. What I have seen appears to be out of date, with various discrepancies about what needs to be done. No one seems to know what to do. We have hundreds of products, hundreds of customers, and we need to connect any new installation with the existing database otherwise we might as well just close down completely and start an entirely new business, losing 9 years of work. We can't afford to lose all the links we have into our existing store. This is a ridiculous situation and it feels like Prestashop has just abandoned everyone to try and work everything out for themselves. I'm extremely disappointed. We need some guidance here!
  13. The only problem with that you've just written is that they don't provide any opportunity to agree to their terms and conditions prior to payment. I have just gone through the process again and at no point did it ask me to confirm any terms. The terms we agree to as consumers are standard, and these include NOT being charged for goods or services and then the agreement (one which PS DID NOT require me to agree to) being changed AFTER payment. Go ahead and go through the buying process yourself, you can do so as a guest and pay using PayPal, at no point are you required to confirm terms and conditions - therefore, you are agreeing to standard terms. In the UK (and most of Europe) you are required by law to explain any unusual terms to a consumer before they pay you. When goods are purchased you are forming a contract between customer and seller, this is a standard agreement we all agree to with reasonable expectations of service. If any aspect of the process is OUTSIDE of that expectation, the seller HAS to make it clear to the consumer and HAS to have their agreement to that non-standard contract BEFORE accepting payment.
  14. Retailers cannot accept payment for items without making you aware of the process. When a retailer accepts payment for a product or service they are signing an agreement with the consumer - that agreement cannot then be changed after the customer has paid for that product or service. No one is suggesting that Prestashop has no right to mitigate risk, but that has to be done according to law, and according to the contract they are creating with the customer. They did not do that in this instance, because they accepted the payment and THEN changed the terms. AFTER already taking payment for the purchase, and almost 24 hours later have STILL not refunded that purchase. No, what they did wrong here was accept payment through a Prestashop account and then refuse to provide that purchased item unless further criteria are met, criteria that the buyer was NOT made aware of prior to purchase. You cannot accept payment for a product, then change the terms the customer agreed to arbitrarily, it's really as simple as that. If you are running a shop, you cannot create an agreement and accept payment for a product and then start demanding more from the customer before supplying that product.
×
×
  • Create New...