Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Traumflug

  1. If a customer can log in as another customer s/he can order as that other customer, of course. Adding and address is possible, of course, customers can have many addresses.
  2. Somebody asked where thirty bee stores URLs in the database. It's table shop_url. Location of code files are evaluated on the fly, see https://github.com/thirtybees/thirtybees/blob/1.0.x/config/defines.inc.php#L70-L72 And there might be a file config/defines_custom.inc.php overriding this. This file neither comes with the distribution nor does it get created by thirty bees, but it gets read if it's there.
  3. 4 hours ago, Havouza said: But can I do the same search using only Grep via ssh? How? Much easier than with some GUI tool: grep -rn jv74.se
  4. Simply running the installer gives more reliable information about this. It does all required tests as well.
  5. A known issue: https://github.com/thirtybees/thirtybees/issues/776
  6. This can happen, yes. Some back office pages also list uninstalled modules, so they obviously have to load the main code file of uninstalled modules as well. If this main code file of a module is broken enough to interrupt PHP, this back office page doesn't load. All this doesn't apply to your situation, though. You can list these modules already, so all the module main code files load fine. Removing some of them can't make the situation worse.
  7. Pretty much, yes. Modules not installed get listed in the module list, but not called when displaying other pages. Impolite code can load and call a module directly, of course. But for this to happen, this code has to be aware of the module and deal with the case of it being absent. thirty bees core code doesn't do this (if you find code doing this, it's a bug). With this in mind, cleaning modules is a simple (and boring) procedure: Make sure the module is not only disabled, but also uninstalled. Remove it from the modules directory. Easy way is to use Delete in the provided menu. Slightly safer way is to move the module folder into a different directory (e.g. modules.off).
  8. thirty bees wants allow_url_fopen to be enabled. That's the PHP default, but apparently somebody turned it off on your server. See https://www.php.net/manual/en/filesystem.configuration.php
  9. Thanks for reporting! Filed in the issue tracker to not forget this: https://github.com/thirtybees/thirtybees/issues/914
  10. Impressive efforts. I wish I could get people into giving a migration to thirty bees at least a try. There one gets all this, and is safe for the coming future.
  11. Traumflug

    Update 1.0.3

    Yes, updating also upgrades the database.
  12. @datakick probably means an update not to 1.0.8, but to Bleeding Edge / 1.0.x. That's currently pretty stable.
  13. Like this one? https://store.thirtybees.com/
  14. Traumflug

    Update 1.0.3

    You mean this page https://store.thirtybees.com/shop-modules/administration/core-updater ? That's plain wrong 🙂 It also says "PHP 5.5", which is wrong as well; it requires at least PHP 5.6. One can find Core Updater in the module list in back office. There should be no such issues.
  15. Here we go: https://github.com/thirtybees/thirtybees/commit/1818e2aca9b90dbee0553272e45956b275fda334
  16. You mean forward slashes as part of the name? Yes, they were disallowed to avoid names like "cat /etc/passwd". Looks like there's another commit needed. Dealing with names is a tricky matter, see https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/
  17. Traumflug

    Update 1.0.3

    True. Core Updater takes care of all these extra steps for updating beyond 1.0.3.
  18. Standard migration method is to upgrade this shop to PrestaShop 1.6.1 using PrestaShop updates, then migrating it to thirty bees. If this doesn't work out, there are modules and services which don't migrate the shop software, but copy products, customers, orders and all this stuff from an old to a new shop. For example these: https://store.thirtybees.com/shop-modules/administration/migrationpro-migrate-from-prestashop-to-thirty-bees-migration-tool http://www.shopping-cart-migration.com/#a_aid=thirtybees
  19. Not really. thirty bees works entirely fine without any caching. Caching shouldn't change shop behavior other than making it faster. Also, some caching methods have benefits on one system, but not on another. When enabling caches one should always test whether there's actually a performance benefit. If there is no such benefit, I'd keep it off. Adding complexity without a gain is rarely a good idea.
  20. Wow. This appears to happen quite often. Three such questions in the last two days. Anyway, here's the solution:
  21. The thirty bees solution for this kind of spam is here: https://github.com/thirtybees/thirtybees/commit/c733d5360d5292c12bb6a899748d9094bc608e05 https://github.com/thirtybees/thirtybees/commit/7ad147d991861e498e586f4dfc8ad1ff3cc114c0 https://github.com/thirtybees/thirtybees/commit/f04f1ded917b702465b2da6adfb7d573fdb974ad Three commits, because it's based on this solution in the PS forum, but also more complete. For example, it also updates JavaScript validation to avoid fields turning red on valid names.
  22. Fixed. See https://github.com/thirtybees/thirtybees/commit/dc562ddd0534a21c707741f9a5c52b2256ffd53c
  23. I just tried to reproduce this, but no matter how often I change order status or resend a status email, I can't produce a 500 error. Did this on 1.0.8 as well as on latest 1.0.x. It looks like a more detailed step-by-step procedure to reproduce this issue is required. Where exactly to click in front office, where in back office, which payment method, status change from which status to which other status.
  • Create New...