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. Let's not forget this: https://github.com/thirtybees/thirtybees/issues/978
  2. In the upcoming days, a whole lot of releases of existing modules are planned. Sometimes just code maintenance, sometimes substantial improvements. I'll post release notes here, so you don't have to look up all of them on Github. Today it's Core Updater: Make the Ignore community themes switch aware of the new community theme, Niara. Substantial performance improvement when scanning large sets of (product) images. Some hosts simply timed out when searching 100,000 product images, making updates impossible. Code maintenance. coreupdater-v1.1.0.zip (also arriving in your back office)
  3. This will happen as part of the release. And I hope I don't forget to copy community-theme-default translations to Niara, because as far as I can see, they're pretty much the same. Niara is about looking good, so mostly Sass/CSS changes.
  4. Let's not forget this: https://github.com/thirtybees/thirtybees/issues/976
  5. Your fix looks good! https://github.com/thirtybees/niara/commit/61440184b371d09ea91069e0b790b01e11b130e4 Maybe the first time we see delivery times for all carriers 🙂
  6. Done: https://github.com/thirtybees/niara
  7. Just in case anybody is interested, here's a preview of thirty bees 1.1.0. It still shows up as version 1.0.8 after installation. thirtybees-v1.1.0-preview.zip
  8. ... and for those who care about email security. Phishers can't hide URLs or do fancy JavaScript tricks in plain text.
  9. Yes, this was the idea. Actually working on improvements turned out that one can pretty much always provide a backwards compatibility path. What's left is removal of old, no longer needed stuff. For example, PHP 5.5 support. Or support for the old (pre PS 1.5) image storage layout. Or support for multiple encryption algorithms. Or support for mixed secure/insecure pages. Lots of performance and reliability improvement opportunities without breaking existing themes and existing installations.
  10. True, the term "Bleeding Edge" is a bit misleading right now. It's no Alpha either, because there are virtually no new features, just many many bug fixes. Actually it's currently more stable than "Stable". I hope we can return to a more expected system before too long. Like making a Stable release from Bleeding Edge about once every month. This is, of course, more work. Once there, making a Stable release will be a matter of only few hours, so it'll happen more often.
  11. As mentioned many times, compatibility with PS 1.6.x won't go away. To take your example, this separation of theme installation code is done already and was of course tested with PS themes. It works better than ever before. thirty bees might well become more PS compatible than PS its self.
  12. Git Based Updater is abandoned / was renamed to Core Updater. It can get removed safely. thirty bees Updater allows to update to 1.0.8, only. It's still needed for updating modules, though. Eventually module updating code will get moved back into thirty bees core, which will make this module obsolete. Core Updater is the name of the Game. There one can update to Bleeding Edge and before too long, to 1.1.0.
  13. To get an idea of what I'm currently wrestling with, see this issue: https://github.com/thirtybees/thirtybees/issues/966 Which means, just swapping the default theme for another theme is not a process of hours, but more like a process of weeks. The data initially installed is all handcrafted, so one has to install over and over again and adjust this initial SQL and XML until the shop comes out the way it needs to be. Incredibly fragile. Did you know that community-theme-default comes out different when installed initially compared to the same theme being installed on an already running shop? This distinction needs to get minimized, ideally to zero.
  14. Themes get applied to a shop, so a need for two themes also means a need for two shops. That said, it's not exactly obvious why a PWA would need a distinct theme. Screen size is about the same, target customer is the same, shop is the same, products are the same, so it might be a good idea to simplify the shop not only for those dragging your site to the desktop, but for everybody.
  15. Could you send me this file, please? My email is markus@thirtybees.com.
  16. Yes, pretty much all of the PS 1.6 documentation is still valid. Changes since then are described in the release notes for each thirty bees release.
  17. Das ist mehr oder weniger kompatibel. Mit thirty bees 1.1.0 wird es dann voll unterstützt, dafür musste ich nur eine Warnung in Ordnung bringen.
  18. URLs typed into text fields have to get changed manually, that's correct. URLs created automatically also change automatically by editing SEO & URLs in Preferences.
  19. Maybe a matter of HTMLPurifier. See back office -> Preferences -> General, 4th switch.
  20. The only way to find out whether a module works is to run it. Code is way too complex to see proper operation by looking at this code.
  21. To restore hooks, uninstall, then re-install the module.
  22. Traumflug

    Shipping Setup

    First, welcome to thirty bees! If there are options you don't need, don't use them 🙂 Shipping costs by price is for those who want to give e.g. free shipping for all purchases above € 75.-. Distinct services of one company, e.g. USPS Parcel vs. USPS First Class, get treated like distinct carriers. Set up both and the customer is allowed to choose what s/he likes.
  23. We had quite a number of cases where uploaded distribution files turned out to be incomplete. So, a first step would be to upload all of them again to find out whether things work better then. If this still doesn't help, I'd appreciate getting access to your webhosting, so I can try myself. Such errors are very rare, don't want to miss the opportunity to catch it.
  24. Yes. It'll come with both themes. There's no point in doing so. Yes, except for PHP 5.5 compatibility. PHP 5.6 will be the oldest PHP version supported, then.
  • Create New...