Auto-update to newest version is working again

[datakick]

I'm happy to announce that the tbupdater module has been fixed, and can be used to update your thirtybees store to the latest version 1.0.6. There's no need for manual update anymore.

To update your store, you will first need to update thirty bees updater module to the 1.3.2 version:

Then you can open the module's configuration page, and migrate to the latest thirtybees version:

[MockoB]

Thanks for supporting the project @datakick it makes me more confident about it's future! You too @Traumflug !

[Tomik]

This was a really needed update :) maybe ill come back as patreon now ;)

[Troy.Roberts]

Getting an error at the last step

All files upgraded. Now upgrading database...

[Ajax / Server Error for action upgradeDb] textStatus: "error " errorThrown:"Service Unavailable " jqXHR: "

How do i confirm that the required database changes went through?

[datakick]

@Troy-Roberts Error code 503:Service Unavailable can be returned by your server / proxy when it's under heavy load. The ajax request to upgrade database probably never made it through to the php layer. Most likely, sql migrates were not processed at all.

What version did you migrate from? There weren't any sql migrates since 1.0.4, so if you have migrated from 1.0.4 or newer, it's safe to ignore this.

[Purity]

Thanks for updating this.

I'm not sure if it matters but the module does tell me TB cache is turned off even when it is turned on in 1.0.4 before updating. I assume I should turn it off anyway, but should I be worried about this or do you think I'm safe to proceed?

[datakick]

@Purity that seems to be a bug, I'll investigate. It's definitely safer to turn off the cache before performing update.

[Troy.Roberts]

@datakick I tested a 1.0.3 store

[Troy.Roberts]

@datakick The update looks like it wasn't successful, so i rolled back to backup. Will investigate more later tonight perhaps

[dosbiner]

thank you so much @datakick & @Traumflug I've tested upgrade 1.0.5 to 1.0.6 works fine ?

[vzex]

THANK YOU SO MUCH! @datakick @Traumflug @lesley @mdekker @wakabayashi and to all the other code wizards!

Just completed successfully with Panda theme 1.5.8

[Purity]

Didn't work for me. Updater times out during backup, which takes an extremely long time. Might be due to me being on shared hosting, but I don't usually have problems. Tried to upgrade from 1.0.4

[hfxracing]

where do you get the latest updater download?

[datakick]

@hfxracing you should see it in your back office. If not, you can download it here

[datakick]

@Purity it's probably the shared hosting thing.

There is a really huge amount of work that updater needs to perform, and it takes considerate amount of server's resources to do so. Updater tries to be smart about it, and splits the work into series of small work items / chunks. The size of work item is determined by the Server performance settings option:

But in the end, your server is expected to complete every chunk atomically - in one request. That means, for example, that your server must be powerful enough to to add 400 files to the backup zip file within once request.

Shared hostings can employ multiple measures to ensure that one site will not consume all the server's resource. It can calculate how much CPU/Disk IO your site used within the last few minutes, and it can start throttling resource allocation to your site if you exceeded some limit. That can include decreasing of max-execution time, lower priority for IO operation, lower priority for PHP process, etc...

This resource throttling is only fair --- your hosting provider have to ensure that other sites hosted on the same server won't be affected by your actions. But it can mean that long-running tasks like updates / data import / export / image regeneration / cache indexing / ... can fail.

This is definitely a red flag, and you should consider different hosting solution.

[W.Kara]

Working as intended on my test, good job.

[x97wehner]

Awesome! I'll use it for the next release

[movieseals]

@datakick I have had that disagreement (re: shared hosting) happen to me several times already. Unfortunately, for most shops, if you want some level of freedom, a dedicated host or at least a VPS is necessary nowadays. Big learning curve but I would never go back!

Thanks for all the hard work fixing the updater guys!!!

[30knees]

1.03 to 1.06 worked flawlessly and quickly! Brilliant job!

[musicmaster]

I took a fresh 1.01 install and upgraded it to 1.06. I compared the result to a fresh 1.06 install. Not every difference may be significant but I hope the overview of the differences is helpful in fixing things. Note that I took fresh installs. I didn't even look at the front:

The results of comparing files: - translations (both nl.php files and files under \translations) are not updated. Maybe this should become an option? - It looks like nothing under the \vendor directory is updated. Changed were ezyang, greenlion,guzzlehttp,jakeasmith,mrclay,pear and swiftmailed. Geoip had disappeared in the fresh 1.06. - I had indicated that the theme should be updated. However, its Modules, Css and Sass subdirectories seem not changed. This also happened to gulpfile.js and package.json. 1.01 had a Stylesheets subdirectory that has disappeared in 1.06. The Tools subdirectory contains three javascript files in 1.06 and one in the updated 1.01. In the root advanced-payment-api.js is missing in the updated 1.01. - the mails directory is not updated. Again: should this be optional? - nothing in the config directory is replaced - the .sass files of the admin theme are not replaced

The modules directory: - Nine not installed modules have all files in the updated 1.01 and only a translations directory in 1.06 - many new modules cannot be found in the updated 1.01. The fresh 1.06 Modules directory has 87 subdirectories. The updated 1.01 only 54. Fixerio is the only modules that was present in the updated 1.01 and not in the fresh 1.06.

The updated 1.01 offers mails in all languages. 1.06 only in those installed.

The result of comparing database structures: - On quite a few places 1.06 has default dates of "1970-01-01" where the upgraded 1.01 has "0000-00-00" - On quite a few fields 1.06 has field length 11 where the upgraded 1.01 has 10. - some of the upgraded 1.01 tables have charset utf8 while 1.06 has utf8mb4 everywhere - the table with the most differences is tbpagecache. The upgraded 1.01 has much more keys. See image.

In the configuration table: - PSVERSIONDB is 1.6.1.999 in the upgraded 1.01 and 1.06 in the fresh 1.06 - PSSHIPPINGHANDLING is 2 in the upgraded 1.01 and 0 in 1.06 - PSSTATSRENDER', 'statsmodule' in 1.06 and graphnvd3 in upgraded 1.01 - PSSTATSGRIDRENDER 'statsmodule' in 1.06 and gridhtml in upgraded 1.01 - The 1.06 configuration table has 11 more entries. Examples that are found in 1.06 and not in the updated 1.01 are BLOCKSOCIALAMAZON and TBUSEWEBP

[Traumflug]

Big thank you for this list, @musicmaster!

[musicmaster]

On top of my wishlist for any upgrader module is to be forced to make a choice whether I want a backup or not. Too often I find myself clicking Upgrade and backupping while I really don't want. And then I have to wait forever... Making no backup the default is not really an option. But you can force the user to make an explicit choice and if he forgets to do so give him a popup "please choose your backup option".

It is rather simple to implement and I can have a look at it when find some time. But what do other people think about this modification?

[Traumflug]

The new upgrader will be just as fast with a backup as without one. Magic? Nope. KISS.

[lesley]

I honestly think the yes / no button is enough. If we start making pop up alerts to ask people things where do we stop? If they are not paying attention when doing a process it is not our fault, why annoy the people who are.

[doclucas]

@musicmaster What an excellent post! Thank you for that thorough check! Hopefully all these issues will be fixed shortly.