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. Perhaps you were waiting just as long as me, now it's done: thirty bees v1.1.0 (ZIP package) Packed with hundreds of bug fixes, awesome new default theme, two new modules. Release notes: Core Updater is now the tool to update thirty bees core. A lot faster, a substantially more reliable update strategy. It can update all versions beginning with thirty bees 1.0.1. And it can downgrade / roll back just as easily in case a new release doesn't work for your shop. Module tbupdater should be kept installed, it's needed for updating modules for the time being. Big refactoring of error reporting and exception handling by @getdatakick. A new exception page and more important for merchants: reports no longer go into the rendered shop page, but get reported in the JavaScript console. PHP errors messing up shop pages are a thing of the past. Another big audit of price rounding. Prices in the cart get now rounded properly according to the configured rounding strategy (by item / by line / by total). And invoices, credit slips, all now do as well. This audit also brought a lot of detail improvements in displayed prices. For details, see https://thirtybees.com/blog/prices-done-right/. In multishop environments, one no longer sees duplicate entries for currencies. Editing translations no longer requires to raise the max_vars PHP setting. Thanks to @ziyaindia. When checking for module updates, not only the module name, but also the module author has to match. This should solve a class of issues with thirty party modules named like official modules. It also means that one can exclude a (edited) module from updates by simply changing the module author, e.g. from $this->author = 'thirty bees' to $this->author = 'thirty bees tweaked'. Coupons/vouchers with taxes get now taken into account as well, thanks to @Zengraph. With multishop, lists of customer groups now list only groups available in the currently selected shop context, thanks to @chitmann. Also thank you to Emanuel Schiendorfer, David Gasperoni, Mark, Yaniv Mirel and Geo for their contributions. Much appreciated! There is a new section in the statistics module: Stats by Groups. Written and contributed by @Zengraph. Considerable chunks of theme installation were re-written. It should work now simpler and no longer mess with back office modules. This added support for different image sizes in distinct themes. Developers would call this a per-theme namespace for image types. Theme configuration XMLs in config/xml/themes/ disappeared. As they never got edited, they were always identical to config.xml in the theme folder. This also removed config/xml/themes/default.xml, which was used for community-theme-default, so no more surprises when installing a shop and re-installing the default theme. Initial theme settings in the installer were aligned with those of the actual default theme. Before, (re-)installing the default theme later had quite distinct results from what one had right after installation. Theme metas (where one turns left and right columns on and off on particular pages) now allow to configure not only pages known by the theme, but all pages available. CSV import now supports custom date formats in CSV data. This should allow e.g. U.S. merchants to import CSV data from a European manufacturer. Thanks to @ksimunovic! A new, awesome looking default theme, Niara. Previous theme is still there. Now one can switch back and forth between both themes coming with thirty bees. Support for the "back" step with third party themes is forthcoming, one can still install them, of course. Module beesblog is now a default module. Two new modules, thememanager and tbhtmlblock. Already in use by theme Niara, they get disabled when installing theme community-theme-default. Modules & Themes Catalog can now actually list modules and themes. Notes to developers: Price rounding audit contained the following steps: Get the cart into rounding properly. When creating an order, take these rounded prices from the cart unchanged. This ensures all downstream calculations use these rounded values rather than the current product price. This also allowed to remove duplicated rounding in classes like HTMLTemplateInvoice or HTMLTemplateOrderSlip. As a metaphor, consider rounding to be like a discount: price in the order is what the shop customer saw, not what the merchant started with. Reviewed all classes dealing with prices to always round to database precision. As if PHP couldn't do better. For strategies, see Dealing with Prices at Traumflug's. Replaced a whole lot of (hopefully all) hardcoded rounding precision values with constant _TB_PRICE_DATABASE_PRECISION_ or Configuration::get('PS_PRICE_DISPLAY_PRECISION') as appropriate. Controllers rendering option fields ($this->fields_options[]) containing prices should use field type 'price', validation 'isPrice' and, new, a cast 'priceval'. The latter converts to a float, then rounds to database precision. AdminController was changed to apply the cast for option fields ($this->fields_options[]) before validation, not after. This allows to implement a cast which shapes the value (like priceval() does). There is a new field type for a class' storage field, type TYPE_PRICE. It's a float like TYPE_FLOAT, but also rounds the value to database precision, to get precisely predictable price and tax calculations. Started to remove outdated code. Retrocompatibility code for PS 1.4 and before or PHP 5.5 and before. Removed AdminRangePriceController and AdminRangeWeightController. Introduced in 2011, they were never available in back office. Classes RangePrice and RangeWeight are kept, of course. Themes now support only one variation. Not sure whether multiple variations every worked before, code had quite a number of discrepancies. Attempting to install a theme with multiple variations now reports an error. To get the path of the config file of a theme before and after 1.1.0, use Theme::getConfigFilePath(). Image type names are now enforced to contain the theme name. Recommended standard is to let the system do this, it prefixes the theme name. For getting links to product images, use Link->getImageLink(), for getting product image sizes, use Smarty getWidthSize and getHeightSize, see e.g. in _productlist-item.tpl in both thirty bees themes. For getting just the appropriate type, use ImageType::getFormatedName(). Other variations are allowed as well, see ImageType::getFormatedName(). And yes, fallbacks for hardcoded image types were implemented. They come with a small performance penalty, though. To see how to fix a theme with hardcoded image types, see commits like https://github.com/thirtybees/niara/commit/1047053d4829ecaf7e5bbdbad891bba286863b07 or https://github.com/thirtybees/niara/commit/7f682df10940170593bbe6d21ea99dd74ebe77ae. There are a whole lot of new hooks, see New Hooks in 1.1.x in our forum. And yes, we're aware this has taken waaay to long. thirty bees should release more often. This release also appears in Core Updater in you back office.
  2. Turn on debug mode in back office -> Advanced Parameters -> Performance and try again. It should be much more verbose about what's going wrong, then.
  3. Pretty much all of them work, incompatibilities with PS modules and themes are considered to be a bug. Exceptions are modules with functionality implemented natively in thirty bees, like pretty URL or updater modules. They'd be pointless even if they'd work. While thirty bees enhances a lot of details, it also maintains backwards compatibility. And yes, welcome to thirty bees. For a definite answer to your question, just install and try. There's also module psonesixmigrator, which migrates PS shops to thirty bees with all its settings, categories and products: https://thirtybees.com/migrate-from-prestashop/ https://github.com/thirtybees/psonesixmigrator/releases/latest
  4. Let's not forget this: https://github.com/thirtybees/thirtybees/issues/998
  5. This extra page on theme installation was removed recently, that's true. But not with 1.0.8, it's 1.1.x and later only. Modules don't get uninstalled, they get disabled. Which means, they keep their settings. They can get re-enabled in Modules and Services any time. Simple point of this intermediate page removal is, themes should appear as the theme developer designed them, not appear depending on what modules were installed or not installed before. If a merchant has a different idea about how the theme should look, s/he can change this with the theme already installed. Another thing changed with 1.1.x: many modules are no longer considered to be theme related, like updater modules, like dashboard modules, like statistics and payment modules. These are left untouched on theme changes. It was a bit odd to see statistics modules in back office disabled or newly installed just because the front office theme changed.
  6. That's probably a Yes. Changing _TB_VERSION_ in config/settings.inc.php should be sufficient. It can get restored after the installation.
  7. Here's the last chunk for the time being: beesblog Changed default image sizes. Removed Google+ support, this community vanished. Added support for updateFriendlyURL(). Code maintenance. blockbestsellers Actually two releases, 2.2.0 and 2.2.1. The latter restores compatibility with community-theme-default and themes derived from this. Support for the new hook displayHome. Shows just 4 products by default to appear more pleasing on theme Niara. Code maintenance. blockcontactinfos Preserve newlines in the contact address. Before one could enter them on the configuration page, but front office would show all in one line. blocknewproducts: same as with module blockbestsellers. blocksocial Pre-fill some fields on installation. Code maintenance. blockstore Code maintenance. blocksupplier Code maintenance. coreupdater (yet another release) Fix configuration page display on wide screens. homeslider (yet another release) Explain image sizes on the configuration page. statsmodule Additional section Stats for Groups. Fixed uninstallation. Code maintenance. And last, not least, a new module: HTML Block.
  8. Updating with Core Updater shouldn't touch third party themes or settings of their custom modules at all. It changes thirty bees distribution files and default theme files, only. The latter can get turned off. To find out what an update changes, do a comparison with Core Updater. This lists all the files going to get changed by the update. Files listed and marked with an M may need some care, but usually there are no such files.
  9. If you could elaborate a bit more about what "disaster" means, we'd have a chance to fix it. Bonus points for filing a Github issue with sample CSV import files (bug fixing is all about reproducing issues).
  10. Thanks. This means it's not an image type issue. In the previous post image type home_default is listed and the theme looks for something with home_default (not Panda_home_default or whatever). For finding the problem, see @musicmasters last post, that's the right strategy.
  11. Please look up two things: 1. In back office -> Preferences -> Images, look at the topmost panel. This lists image types. Depending on the theme, some 5 to 15 types. If you can, copy them into here, so we can see it. 2. Find out the URL of the images your browser tries to load. With Firefox that's right click -> copy image address, then pasting that address elsewhere, e.g. into here. While all these placeholder images look the same, they all have a distinct URL. Copying one or two of them should be sufficient to find the problem. thirty bees recently received support for distinct image types in distinct themes. Along with a fallback to the old mechanism, of course. Maybe it doesn't always work as well as expected.
  12. thirty bees resizes product pictures automatically as needed, of course. Just upload the image and it'll get resized to all sizes needed. If the theme happens to change its mind about required sizes, there's a batch processor built in, which recalculates all of them again.
  13. Delete cache/class_index.php, it might be outdated. It'll get recreated automatically.
  14. All these releases should appear in 1.0.7 and earlier as well, except for tbupdater.
  15. Aaaand ... yet another chunk. These are all just code maintenance releases: ctconfiguration blocklanguages blockmyaccount blockmyaccountfooter blockpaymentlogo blockpermanentlinks blockreinsurance blockspecials blocktopmenu blockuserinfo tbupdater themeconfigurator blocklayered These have additional fixes: blocklayered: Fixed a retrocompatibility bug, settings from earlier versions should work now. Thanks to @Captain-FLAM! blocktopmenu: New feature to limit the menu level depth. It defaults to 2. Thanks to @pauld-codes! tbupdater: Disable the configuration page. Merchants should (and can) no longer update thirty bees core with this module. There is now Core Updater. Nevertheless, tbupdater should stay installed, it's still needed for module updates. tbupdater: Upgrade to the new version on thirty bees 1.0.8 or later, only. To allow merchants to still update to thirty bees 1.0.8 using the previous version. Cheers!
  16. It's probably not too complex. For each CSV line do: Try to find a matching product in the database. With a match found, load it: $myProduct = new Product($idProduct); If there is no match, create a new product: $myProduct = new Product(); Copy CSV data into this found/new product. $product->save(); For getting rid of products no longer in the CSV, one has to go through all products in the database and try to find a match for each in the CSV. In chunks of 10 or 100, of course.
  17. These are all code maintenance releases: homeslider homefeatured vatnumber trackingfront producttooltip productscategory productpaymentlogos blocknewsletter blockmanufacturer blocklink blocksearch blocksharefb blocktags blockviewed ecbexchange crossselling dashgoals dashactivity dashproducts dashtrends socialsharing statsdata sendtoafriend These have additional fixes/changes: homeslider: new images for thirty bees 1.1.0. homefeatured: A distinct template for the tab on the home page, views/templates/hook/homefeatured_home.tpl. Default is compatible with theme community-theme-default. As with all templates, this can get overridden by the theme, but doesn't have to. Most of the releases in the list above were actually done by @datakick, big THANK YOU to him!
  18. Looking at the code ... https://github.com/thirtybees/thirtybees/blob/1.0.x/classes/ObjectModel.php#L538 ... save() makes always sense. It does an update() for existing objects and an add() for not yet existing ones.
  19. This isn't much of a surprise. With a user being logged in, additional data, like its address, is available, which can give reasons for not having a carrier, of course.
  20. If it's just about syntax, there are HTML validators, like https://validator.w3.org/nu/?doc=https%3A%2F%2Ffront.thirtybees.com%2F Even the default theme isn't entirely free of warnings, still you can look up whether your theme shows more glitches.
  21. The camera image is --you guessed it-- a placeholder image. Nice thing is, it gets delivered for the original URL. Which means, one can look up the URL of each camera image (they likely have distinct URLs) to find out what's missing.
  22. Obviously this didn't happen. The day after the 1.1.0 preview publication some 20-30 commits appeared in the repo. If I build a distribution package with this, I get this for the shop front page ... ... so I'm kind of back to square one. Building a distribution package for previews and testing this goes like this: ./build.sh --no-validate HEAD
  23. This text is embedded in the image, here's the sample banner: https://github.com/thirtybees/blockbanner/blob/master/img/sale70.png (also in modules/blockbanner/img/ in your shop installation). Accordingly, to create a different text, it needs a different image, made by GIMP or PhotoShop.
  24. It's just a lack of a default message, nothing serious. To not forget it: https://github.com/thirtybees/thirtybees/issues/982
  25. Not really. Three times more Debian/Ubuntu installations than CentOS: https://w3techs.com/technologies/details/os-linux/all/all
  • Create New...