Release 1.0.7 is there!



  • Say hello to thirty bees version 1.0.7.

    Release notes:

    • Full page cache should work now again (known bug in 1.0.6), thanks to @getdatakick.
    • Fixed a security flaw where customers could see shopping carts of other users when Full Page Cache was enabled.
    • Fixed date format for Arabic.
    • Fixed a potential time zone misalignment, which led to cron jobs not executing. Thanks to @doclucas and @getdatakick.
    • Fixed the config.xml vs. Config.xml problem on theme installation.
    • More PHP 7.2 compatibility.

    Hundreds of translated strings by @DaoKakao, @toplakd, @yanivmirel, @elund, @m.tomasovsky, @tRACE, @Andreaevangelina, @paintspec, @selwyn, @lutek, @null, @antagony1060, @Khan27, @AmirRzd to German, Russian, Slovenian, Polish, Danish, Hebrew, Czech, Spanish, Afrikaans, British English, Azerbaijani and Persian. Thanks to all of you!

    Notes to developers:

    • register() in config/smarty.config.inc.php changed its signature. We didn’t find a module using it, but if your module does, use smartyRegisterFunktion() instead.

    Upgrade procedure using the release package:

    • Download the ZIP package.
    • Unpack the package.
    • DELETE the install directory from what was unpacked.
    • RENAME the admin directory to the same name as your current admin directory.
    • Perform a FULL BACKUP on your site.
    • TURN OFF all caches on your shop or or set it to force compile.
    • Upload the files that are remaining from the zip archive to your site.
    • Delete file cache/class_index.php
    • Go to the config directory and edit the settings.inc.php file, update _TB_VERSION_ to 1.0.7.
    • Now log in to your back office, the upgrade should be finished. You can turn caches back on.

    That said, a package for the updater module is in the works, so it should appear there before too long.
    The updater module should list the 1.0.7 release now.

    Enjoy!



  • Nice news! Thanks and all the best for the dev team 🙂



  • OMG Is that it … I wish Zencart was this easy to upgrade
    Thanks for the update and hard work



  • Great work @Traumflug, @lesley and @datakick



  • Great news 🎉🎉🎉
    thank you for all contributor 🙂



  • Is there any documentation on how to manually upgrade my installation to this version?
    The update module didn’t work for me, presumably due to shared hosting.
    Currently on 1.0.4



  • You can use this as a general idea, https://thirtybees.com/blog/version-1-0-4-has-been-released/

    DO NOT RUN THE QUERY SCRIPTS this version does not need any database upgrades / changes.



  • Just few impressions about 1.0.7 caching stuff: When I just click enable and all hooks are red the front end gives me 500 and few parts of the page (very strange error, I’ve never seen it like that).
    The following days I will check what could cause this.

    I also had problems logging in in BO but this I imagine was caused by not deleting the cache prior to uploading the files.



  • Just one question.
    As default theme is always up do date, is there any plan to be able to activate left column on all pages?

    Thank you.
    Dejan



  • The update module didn’t work for me, presumably due to shared hosting.

    That’s currently expected, the necessary files aren’t on api.thirtybees.com, yet. I hope I can get this done today.



  • I wish Zencart was this easy to upgrade

    Such a statement makes me curious why one would want Zencart while thirty bees exists.



  • @the-rampage-rado said in Release 1.0.7 is there!:

    Just few impressions about 1.0.7 caching stuff: When I just click enable and all hooks are red the front end gives me 500 and few parts of the page (very strange error, I’ve never seen it like that).
    The following days I will check what could cause this.

    I also had problems logging in in BO but this I imagine was caused by not deleting the cache prior to uploading the files.

    There’s one more step that needs to be done when manually upgrading to newer version of thirtybees. The file cache/class_index.php must be deleted.

    This file contains information about core php files and their overrides. Thirtybees tries to keep this index up to date, it gets rebuild whenever you install/uninstall modules, during system upgrade, etc. But thirtybees will not detect when you add or remove core php files manually, for example using ftp upload.

    When this file is out of sync it almost always results in 500 error code. I think this is the case – there is now core php file PageCacheKey.php, and with outdated class_index this file will not be loaded.

    I’ve modified the first post in this thread, and added this step



  • I have not deleted it manually but deleted the cache in BO when I gained access. I think it deletes this cache also?! Am I right?



  • @the-rampage-rado It should. The error on frontend was still there even after cache cleanup?



  • I surely would delete cache/class_index.php trough FTP. Just to make sure it was newly generated.



  • Just added the 1.0.7 update to the updater module. A test update went flawlessly.



  • @datakick said in Release 1.0.7 is there!:

    @the-rampage-rado It should. The error on frontend was still there even after cache cleanup?

    Nope.

    @wakabayashi - I will do so tonight when I dive into the shop… 🙂



  • @lesley Thanks a lot Lesley.
    I saw that before but wasn’t sure if it was still applicable.
    I got the update installed using that guide.
    Looking good so far.



  • The update works excactly as described in the openingspost. Didn’t use the updater.

    Got the first time i go to a product at the backoffice to watch the price a servererror. Didn’t remind what was in it sorry. Didn’t come back.



  • I editted my post. Watched the product at the backoffice


 

Looks like your connection to thirty bees forum was lost, please wait while we try to reconnect.