Jump to content
thirty bees forum

lesley

Trusted Members
  • Posts

    2,197
  • Joined

  • Last visited

  • Days Won

    36

Everything posted by lesley

  1. Do you use anything to delete carts? Does disabling overrides do anything to help fix the issue?
  2. Hmm interesting. We will get it looked into. I just created a new issue on the bug tracker about it, https://github.com/thirtybees/thirtybees/issues/609
  3. What fails about this? Is the paypal not displayed, or is it returning an error message?
  4. We are proud to welcome our newest partner agency @innercode to the thirty bees partner program. You can read more about our newest partner here, https://thirtybees.com/blog/partner-agency-innercode/
  5. You can uninstall the tb updater and it will disable it.
  6. On the performance page in the back office can you try both the disable overrides and disable non native modules options and see if that helps it.
  7. Is that file on your server?
  8. Been waiting a long time for some of the enhancements to come to fruition, especially a one page checkout that isn’t outdated like the current one and a modern theme. This is something I actually talked about on slack yesterday with @wakabayashi There is a cost associated with every change we make. Not a monetary cost, but a real world functionality cost. The feature we were talking about is the multiple features values per feature in a product. There is a cost associated with adding that to the core. Does it work with the layered navigation properly? I am not sure it does. If we added that and broke the layered nav, we would then have to fix that. But then we would run into a problem. Most themes actually ship with layered nav overrides. @wakabayashi theme did. Our default theme does. But us making changes would leave people using 3rd party themes with broken functionality. The same goes with the checkout. Adding that functionality in will break all existing themes, giving users no real option to use it other than to use it with our default theme. Our plan is to keep 1.0.x compatible with 1.6.x of prestashop. Then at the beginning of the year start focusing on a 1.1.x branch with a set of changes. At that time we will have to figure out what all we will be breaking and what we are going to try to maintain compatibility with.
  9. If you notice in the default prestashop installation they do not use the same urls for anything. They use __ and _ that is what we require as well. http://i.imgur.com/fJQKpCx.png
  10. Turn on debug mode and see what error you are getting.
  11. Oh, what is the error message you are seeing?
  12. I have no clue who it is. I get a notification for every post and every spam post on the forum. I try to go through them all, sometimes I skim them and miss things. Like that post, I totally did not see it or I would have answered in the thread and sent the user a message. We do want more users and developers, I have been working with another one I am about to announce tomorrow that is making compatible modules.
  13. Me personally? Most of what I do is behind the scenes.
  14. We always try to reply, as the project grows we are getting inundated with replies. But, yes, this was caught in our spam filter.
  15. Oh, dang, it looks like it was caught in our spam filter. We use a hosted email system from rackspace, sometimes things get caught in it.
  16. I am not seeing what it is doing wrong, can you send a link over or try to explain it better.
  17. A 403 error is generally a mod_security error. Check with your host to see if you are setting it off.
  18. How many products do you have? What size are you considering huge?
  19. In the next couple of weeks likely.
  20. Whats the contents of the emails that are sent on purchase?
  21. Can you all try installing the stats module.
  22. @gonssal My thoughts exactly. If you use an edge version of PHP that is not officially supported, don't be surprised to see notices and deprecations. Its getting harder and harder to support 5.6 and the latest versions without having these.
  23. No problem, easy fix.
  24. Click on the menu in chrome, go to more tools, extensions. From there you can disable them.
  25. You have an extension that is creating problems, or are having a cache problem. I would clear the cache and start disabling extensions until it works, then you can see what is breaking it.
×
×
  • Create New...