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. Well, I think it's time to talk a bit about this next release. Last November, I planned to release it on New Year's Eve. As everybody can see, this didn't work out. How could such an utter mis-planning happen? Well, there was this issue with broken price rounding. A Github issue and the reporter even sent me a patch for correcting the misbehavior. Should be a matter of a day for applying and testing this patch, right? Things turned out to be not that simple. Each look at the code came up with more small issues regarding price rounding, the TODO list grew and grew ... and it took over two month to settle the whole topic. Then thirty bees had much more reliable price rounding, but it was also late February. A similar thing happened a couple of weeks ago. thirty bees 1.1.0 will come with a much nicer, cleaner theme. Switching the default theme on installation should be a matter of flipping a switch, right? Well, as it turned out, not really. Initial theme installation was found to be entirely distinct from a theme installation done in back office. Huge amounts of handcrafted SQL and XML files instead of a procedure installing the actual theme. Which means, since 4 weeks I'm working on separating theme installation from AdminThemesController, into class Theme, to make it available to the installer as well, and to get rid of all the handcrafted SQL and XML, which is hard to adjust to another theme. Also fixing bugs found in this area, of course. I'm not there yet, probably it'll take another two or three weeks. And then I can flip the switch. What does this mean for merchants? Good thing is, they're not lost. During all the time described above, branch 1.0.x wasn't abandoned, but received many many bug fixes, making thirty bees more stable than ever before. The only thing missing thing there is a formal release. Making such a release would throw back the 1.1.0 release by another week or so, so it's not on the TODO list. We have Core Updater, after all, and @datakick regularly runs some voodoo to update its master repository, which allows to update to latest 1.0.x. That's what a merchant should do. It's named "Bleeding edge", actually it's currently more stable than "Stable". Want a return to monthly releases? Yes, me too!
  2. Thinking about this I could imagine making a single-file installer. Just one file index.php, which one had to upload and execute by visiting the site with the browser. Would this be helpful? Technical background: this one file would download the distribution ZIP from Github, unpack it and then proceed as before.
  3. Well, then delete these two modules. They're indeed no longer needed, all the statistics stuff was joined in a single module.
  4. Kommt der Fehler im Front Office (Shop) oder im Back Office (Admin-Bereich)? In beiden Fällen gibt es einen Eintrag in die Datei in log/. Gibt es da keine Datei mit dem aktuellen Datum, bleibt das allgemeine Apache/nginx error-log.
  5. Installing thirty bees is pretty trivial: unpack the ZIP, upload all the files via FTP and direct your browser to your site.
  6. It's line 109 in this file. Change '' to '16.0.1'. Alternative is to apply this commit: https://github.com/thirtybees/thirtybees/commit/be2813efa62a9bdce3f42450cc78632e29fa7e1b
  7. Oh, I didn't want to say that redirecting in general is a bad idea. Just that redirecting from one URL to the same, identical URL is a bad idea. Perhaps most of your trouble goes away if you change the URL a bit. Old URL: https://naildots.com/items/, new URL just https://naildots.com/ . And then without a category items/, to avoid having identical URLs again.
  8. Editing the database directly is verrrry tricky. Can't recommend to do this. For most stuff, editing a single table isn't sufficient. There are tables for categories, tables to map these to shops, tables to map them to languages, and so on. Grabbing a bag of patience and a cup of coffee for doing it manually is a much safer way.
  9. This is the problem. Such a redirect shouldn't be there. And all HTTPS, please 🙂
  10. I'm getting redirects as well: At back office -> Preferences -> General, did you turn on Enable SSL as well as Enable SSL on all pages ? IIRC this is the secret. The latter switch is on the list of getting removed, having sites with mixed security made sense 10 years back for performance reasons, but these days are gone.
  11. Forgot a fourth round: images properly connected in the database, but the original image on disk missing. These report an error on thumbnails regeneration and should get removed from the corresponding product, along with a message to the merchant.
  12. This should happen already. At least with discounts set in back office -> Customers -> Groups -> (edit). One can look up back office -> Customers -> Customers -> (click), in one of the panels is a list of groups a customer belongs to.
  13. Also turn off the adblocker for the back office page. Can't do any good there.
  14. Sounds like a universal hook module. All these triggers (should) have a hook already, the module apparently provides some simple way to connect some kind of code on them. I'd expect success of such a module to raise and fall with the way this "code" gets generated. Is it selecting from a list of predefined snippets? Is it moving some control boxes? Is it an actual code editor?
  15. I fear it's not that simple. Each image has a database entry and each image in the database is connected to a product. A first round of cleaning would be to delete all images in the database not connected to a product. A second round of cleaning would delete all image directories on disk which have no corresponding database entry. A third round would delete image types not needed, as you do already. And I hope I didn't forget something with this description. Cleaning the database should be done not with handcrafted SQL, but by using the PHP class as far as possible. Database storage might change a bit in the future, using the class keeps code future-proof. Your idea of scheduling is fine. It's the simple part anyways, as long as code can execute in 3-second-chunks.
  16. Maintenance tasks obviously require server resources, that's true. That's why ShopMaintenance runs these tasks only once a day and why they should get split into many small tasks. Not running these automatically means, however, most merchants never do this. I've seen a client shop (migrated from PS) with no less than 1.2 million stale image directories; just the directory and index.php inside, but no JPEG. For saving query results between requests one can store the result in a cache file, using PHP's var_export() for saving and require or require_once for restoring. Like done e.g. here: https://github.com/thirtybees/coreupdater/blob/master/classes/GitUpdate.php#L146-L173 . This isn't always faster, though, reading a file with 50.000 lines also takes a noticeable fraction of a second. For being less resource hungry, limiting requests to chunks of 100 or 1000 might be an option: http://www.mysqltutorial.org/mysql-limit.aspx
  17. While there isn't much to see on Core Updater's configuration page, this doesn't look right either. There should be a message hinting to the new menu item. Filed here, hints on how to reproduce this always welcome! https://github.com/thirtybees/coreupdater/issues/4
  18. Nice work! Did you notice class ShopMaintenance yet? It's method run() gets executed periodically (triggered by Ajax requests) and is designed to do exactly such cleaning jobs. Removing obsolete images would be a nice fit there. One problem not solved yet: how to search huge file trees in time-limited chunks. No matter how big the tree is, the search should return after three seconds and pick up next time where it left on the previous run. If you could form your code to make it fit into ShopMaintenance I'd happily add this to thirty bees core.
  19. Field for the VAT number should appear as soon as a company name gets entered. That's done by JavaScript and as such, part of the theme. For B2B shops it might be a good idea to always show this field. The idea of hiding it is to reduce the visual complexity of the page, because most B2C customers don't have a company.
  20. In all shops using Page Cache I migrated to far, performance was considerably better than before, without this module and without turning on full page cache. This is my current release test installation in Chromium, with just Smarty cache and CCC turned on on an old Core2Duo server for a full reload of a product page: With a load time of just 0.35 seconds for the base document (that's where full page cache kicks in) it's hard to imagine this can get substantially better. Remaining load time is loading pictures, CSS, JS and processing that in the browser.
  21. If you'd give us a list of the steps required to reproduce this, we could try. As if one would try to explain it to a child: - Click here - Enter this value in that field - Click there - ...
  22. Thanks for the report. I just released an update, should also appear in your back office: https://github.com/thirtybees/donationminer/releases/tag/1.1.0 Which means: BIG thank you to all those merchants trying to increase thirty bees' income, but this module didn't work out (still it was worth trying). It generated less than $1 income/month for all users together, IIRC.
  23. A backslash? That's Windows, isn't it? The solution is to run thirty bees on a supported operating system, like Linux, *BSD or MacOS. Alternative is to debug and fix this yourself. I'm not aware of a thirty bees developer using Windows, so you're predestined to do this.
  24. Just found a regression, or at least a behavior distinct to PS. If there are two (or more) multishops where one shop URL is contained in the URL of another shop, like https://shop.com/ https://shop.com/centre thirty bees would find the first one, while PS found the second, longer one. Not sure whether this applies to the case here, nevertheless thirty bees behavior now matches PS behavior again. This change will go into the next release.
  • Create New...