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.

Traumflug

Administrators
  • Content Count

    1,148
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by Traumflug

  1. Traumflug

    Sold statistics button on product page missing?

    Fixed. See https://github.com/thirtybees/thirtybees/commit/dc562ddd0534a21c707741f9a5c52b2256ffd53c
  2. Traumflug

    Sending order Statuses

    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.
  3. Traumflug

    GitUpdater preview

    No need to apologize. Looks like I overreacted a bit. You mean this error happens when trying to install the module already? Then there's obviously something wrong with the code installing modules. In back office -> Advanced Preferences -> Configuration Information is a list of changed files at the bottom of the page. Does this list any changes?
  4. The flawed update mechanism Perhaps you remember the 1.0.8 update a couple of weeks ago. While it certainly solved bugs and misalignments for many, it also resulted in quite a number of reports about messed up shops after the update. That's not tolerable, of course. Thinking about this problem I compared to what we developers do to switch between versions, and why we pretty much never mess up a shop installation by doing so, despite switching back and forth all the time. Developers do a git checkout 1.0.7 to switch to version 1.0.7, git checkout 1.0.5 to switch to version 1.0.5, git checkout 1.0.x to switch to the latest development, and so on. And there's the fundamental distinction: doing such a checkout doesn't apply a patchset or a set of changed files, like the current updater module does. When checking out a version, Git compares files currently on disk with kind of a master set of files (stored in the .git directory), then changes files on disk to make them match this master set. The current update module, which is a refined version of Prestashops 1-click updater, has a fundamental flaw: it doesn't check whether files on disk are right, but blindly applies a set of changed files. Who creates this set of changed files? Right: thirty bees developers, which have never seen your shop installation. This set of changed files gets created not on knowledge, but on assumptions. The assumption that your shop installation matches a clean shop installation. Which is often not true, as we unfortunately experience over and over again. Meet GitUpdater Having the fundamental flaw detected, a new updater module started to evolve. Prepared sets of file changes are gone. Instead, the module compares the shop installation to a clean master installation, which gets served by api.thirtybees.com. This always works, and after an update, a shop will always be in a clean, sane state. A recipe for reliability. Advantages This works from any release to any release. Select the wanted version, click Compare and see which files changed since then. Which means, one can downgrade or rollback just a easily as update. Another use case is to compare the current installation to the master installation. Updating from e.g. 1.0.8 to 1.0.8 is perfectly possible, to restore a broken shop. Before too long, this will also support updating to development branches. E.g. to test bug fixes provided on Github. Or even single commits. Manual changes get detected. During comparison, the module detects files which don't match the original version, so the merchant can deal with his manual edits. Smooth operations. All operations taking place got split into small chunks, so one can virtually never run into maximum processing time limits. The preview Here it is: gitupdater-2019-01-05.zip Install it by unpacking in the modules folder or using Add a new module (top right corner) in back office -> Modules & Services -> Modules & Services. Having the module installed, a new menu item, Updater, appears in menu Preferences. That's where this module gets controlled. Yet To Do Actual updates. Currently the module does comparisons only, not actually change files. Which is why playing with this module preview is safe. File filtering. Some files should get ignored. For example, an update shouldn't reinstall the install/ folder despite this folder being present in a clean installation. It also shouldn't remove product images or translations, despite them being not present in releases. User interface. Currently, this module shows a list of all changed/created/removed files. This can be a huge list with up to 10,000 lines. Ideas to display this list in a less scary way are welcome. And for those not installing the module immediately, here's a screenshot:
  5. Traumflug

    GitUpdater preview

    Where? thirty bees officially supports PHP 7.2. Also, module GitUpdater is abandoned in favor of Core Updater. Not only a rename, but also latest fixes. It should appear in the module list in back office.
  6. Traumflug

    WebP image format

    There is some support for it, but not yet ready for consumption. Too many other, more crucial bugs.
  7. Traumflug

    Collapsible text block for CMS (FAQs)

    This is how Core Updater does it: https://github.com/thirtybees/coreupdater/blob/master/views/js/controller.js#L289 It's JavaScript only (using Bootstrap features), no template, CSS or HTML changes needed. To get this working elsewhere, adjusting usage of the field parameter should be sufficient.
  8. Traumflug

    Moving From Sub Domain to Main Website

    Back office should work right after the move. To get front office working as well, adjust Shop Domain, SSL Domain and Base URI in back office -> Preferences -> SEO & URLs.
  9. Traumflug

    Delivery Calendar

    Pretty much all PrestaShop 1.6 modules work on thirty bees as well, so the obvious idea is to look there.
  10. Traumflug

    Installation with non-English language issue

    This should be solved, the PHP Mbstring extension is a requirement now. Thanks for reporting!
  11. Traumflug

    Image format does nothing

    ... except that it hurts to see such suffix abuse 🙂 But you're right, even PNGs get a .jpg suffix and it works.
  12. Traumflug

    Multiple currency handling

    It's the Block Currencies module. It appears as soon as a second currency is installed.
  13. Traumflug

    Cross-platform identity management

    This would require substantial changes to customer and employee handling. Especially if it had to fit a random "some other system". AFAIK there is no gold standard for user handling, each web software uses a custom solution.
  14. Nice catch, and excellent bug report! Let's not forget this: https://github.com/thirtybees/thirtybees/issues/893
  15. Traumflug

    htaccess regenerates by cron or something?

    There's at least a large number of reasons why .htaccess needs regeneration. One can still add custom code, though. Code above the line with ~~start~~ and below the line with ~~end~~ is left untouched on regeneration.
  16. Traumflug

    Migrating from subfolder

    Unless you removed Joomla in this process, this obviously mixes Joomla and thirty bees files, which is pretty much like asking for trouble. There's no drawback in running thirty bees in a subfolder. Many merchants do this.
  17. Traumflug

    Full page cache with different devices

    I see, thanks.
  18. Great! Never hesitate to report stuff not working 🙂
  19. Traumflug

    Question about store phone number

    One can call such a customer with phone number and advertise even more, of course. Advertisers, and accordingly most merchants, looove personal data. That said, one can remove the mandatority of this field in back office -> Preferences -> Customers. Some even remove the entire field from the front office template.
  20. Traumflug

    Full page cache with different devices

    There should be no such thing like a "desktop module" or a "desktop view" or a "mobile view". That's all the same HTML, the same CSS, the same JavaScript. thirty bees should reflect this, as it uses Bootstrap. Desktop users can even change their window width without reloading the page, pages happily switch between phone-type, tablet-type and desktop-type as the window gets dragged wider or more narrow. Here's a nice video demonstrating this: https://developers.google.com/web/fundamentals/design-and-ux/responsive/videos/resize.webm Which leads to the question: what's actually the problem? Some rendering issue?
  21. Also handled here https://github.com/thirtybees/thirtybees/issues/888
  22. Traumflug

    Update stock, tags, and weight from csv

    Actually it's fixed already: https://github.com/thirtybees/thirtybees/issues/833 Thanks to @datakick for doing this.
  23. Traumflug

    Full page cache with different devices

    All devices should receive the same page. The way this page gets rendered is decided by CSS, in the browser. Distinction between "mobile" devices and other devices is blurring and will blur more in the future. What matters is screen/window width. Somewhere on my TODO list is actually removal of this device type property. Not with high priority, though.
  24. Traumflug

    Post Missing

    It's clearly a bug. Whatever a merchant does, misalignments should return an informative error message rather than triggering an exception. In the previous thread I already asked what you're doing. Which controller, which input file, such stuff. Developers can only fix what they can reproduce.
  25. Traumflug

    Performance considerations ??

    Probably it's a good idea to make a clone of your existing shop, then migrating this to thirty bees. This removes the guessing and replaces it by hard numbers. For tuning, there are two key things: a) turn caching on. Full page cache is still tricky, but everything else reliable. And b) remove what the shop doesn't need. Slow shops are typically a result of many many modules added, each bites a bit into performance. Here's @wakabayashi great video showing how to do it:
×