Release 1.0.7 is there!



  • @violinparts In my case it seems to work (I use stackpath CDN)



  • I just tested as well, it is working here too, https://cdntest.thirtybees.com/coffee-and-tea/Coffee/coffee-beans



  • Hi TB Forum

    I did an upgrade from 1.0.3 to 1.0.7 two months ago, and I got an error (see further down) I never got an answer to this error, but the shop did however work fine, and I couln’t find any issues, so I did not think too much about it. But today when I was going to install the cookiebot and cookie consent modules, I got this error:

    [PrestaShop] Fatal error in module file :/customers/3/f/a/norwegianrat.no/httpd.www/vendor/pear/archive_tar/Archive/Tar.php:
    Cannot use result of built-in function in write context

    Is this somehow related to the error I got two months ago?

    Thanx in advance,

    02.10.18

    The updater did download and extract files as I mentioned in an earlier post. Trying to avoid the error, I cleaned up all the files in the “download” and “latest” folder to be sure I was starting with clean slates. I then did as follows:

    Disabled and uninstalled the updater.
    Uploaded the updater @Traumflug provided the link to (even though it was the same version number)
    Downgraded PHP from 7.1.19 to 7.0.30
    One of these steps got it to work. At least partially. It gave me an error after a while, but so far the BO is working and says 1.0.7, and the front office sees to be working. What worries me a little is the error I got:

    All files upgraded. Now upgrading database…
    [Ajax / Server Error for action upgradeDb] textStatus: “error " errorThrown:” " jqXHR: " "

    Do we now have a broken database somewhere?



  • [Ajax / Server Error for action upgradeDb] textStatus: “error " errorThrown:” " jqXHR: " "

    These are surprisingly hard to avoid, the occurrences I’ve seen so far were simple timeouts of the Ajax script … in this case for an operation which should be done in 0.1 seconds.

    Do we now have a broken database somewhere?

    No. Database either got upgraded or it did not, but nothing in between. It should work to simply run the upgrade again. Replacing files and upgrading the database twice doesn’t harm.



  • Ah!

    Thank you for the information @Traumflug ! Appreciate it. Will have a go at it and tell you how it went.

    All the best



  • @Norwegian_Rat If you want to manually check your database to see if it has been upgraded, you can look at the _referrer table and see if the passwd column is set to varchar 60, https://github.com/thirtybees/thirtybees/blob/1.0.x/install-dev/upgrade/sql/1.0.4.sql



  • @lesley : The passwd cloumn is set to varchar 60, so I guess this one is OK then?

    @Traumflug : Maybe a stupid question, but how do I run the upgrade again when the updater settings says I’m running the latest version, and nothing happens when I select “Stable” from the dropdown option? (I know that we can do rollback and do it over again, but I’m not quite sure if this is what you ment?)

    I’m not even sure if the module issue is related to the upgrade? Every module I have tried installing throws this error.



  • Maybe a stupid question, but how do I run the upgrade again when the updater settings says I’m running the latest version

    Version number gets updated as (almost) the last step. Which means, if there is some failure in the update process, one is still on the old version number and can restart the process.

    This also means that being on the new version number is an indication that the update process was completed successfully. Just ignore that error message from the last step.



  • Ah! Great to hear @Traumflug .

    Still got the issue with the modules, though. How do I solve this?



  • Mkai…so it looks like it was a php 7.2 issue. Downgraded and now everything seems to be working. (I know tb is not quite ready for 7.2 yet, but I’m pretty certain we ran under 7.2 during the 0.3 era though…)

    But to the others facing strange issues: CHECK YOUR PHP VERSION BEFORE GOING HAYWIRE ON YOUR SHOP 🙂


 

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