Auto-updates

[magical46]

Not working for me all plugins and blocks on the install/settings page show which version is installed but show latest version as 0.0

[wx_jon]

OK for me as well. Suggestion: provide both update AND download buttons so that those who make minor tweaks to the blocks/plugins can still have a direct download link.

[Kristi]

It works ok for me, both plugins and blocks.

[Reinhard]

OK for me as well. Suggestion: provide both update AND download buttons so that those who make minor tweaks to the blocks/plugins can still have a direct download link.

Thumbs up.

[WouterK]

Working for block updates.
Did not have an update for a plugin yet.

[meteocaldas]

Auto update/install is a fantastic feature and worked OK for me too, with all blocks and plugins.
I only noticed a minor issue when I made a clean install of MT16: some of the blocks didn't install their icons folder.
http://www.meteocaldas.com/mtp

[Lespius]

Not working for me all plugins and blocks on the install/settings page show which version is installed but show latest version as 0.0

Hi Magical,
I had the same and was ok once I cleared all the temporary files and the history in my browser.
Cheers,
Alain

[hcorrin]

Hi
just tried to update the extremes block but it failed so auto update not working for me

[John B]

Right, now I'm sorted out.

The El Nino plug-in is the first to require attention.

OK

[i_fiorentino]

No auto update about El Nino plugin and Extremes block.
I've old versions yet.
Regards,



Alessandro

[Jachym]

No auto update about El Nino plugin and Extremes block.
I've old versions yet.
Regards,



Alessandro

Not sure what you mean, did the update not work or did you not try it?

[jmcafee]

OK for blocks; no plugins needed updating so I could not test.

BUT, I had to enable "zip" in the PHP options for the updates to work.

Great job on the v15->16 update and auto-update feature. Please do not deprecate the auto-update function if the configuration can get worked out (like enabling PHP zip).

[staccermaccer]

Hi, Jachym

Updates working like a charm here! Just have to click on the update icon, new tab appears, screen with plugin or block updated and refresh of browser...

El Nino update BTW worked also!

Marc, Antwerp

[Jachym]

Hmm.... going through this thread... I dont think Im any more decided than I was before

HTTPS could help, but not to all. In the meantime I want to make the decision soon because there are other bugs which need to be fixed (in fact I fixed them already, but I want to release just one bug fix package and that one already has to somehow deal with this update problem)

[i_fiorentino]

Not sure what you mean, did the update not work or did you not try it?

All work as it should now.
Thanks Jachym.

[majora]

Jachym

Have successfully updated my template to v16.0 Physalis and performed several outstanding block and plugin updates.

All worked well without any problems. Thank you.

Alan Major
www.thecorner.me.uk/template (Self hosted on Raspberry Pi3 running Raspbian 9 Stretch)

[Honestjohn]

All updates have performed ok without any issues to date.

Regards

John

[marc@geissmann.org]

Auto-update OK

[Jeffm5690]

Not working for me all plugins and blocks on the install/settings page show which version is installed but show latest version as 0.0

I’m one of the users with this issue and it sucks.

[Jachym]

OK, going through the emails, posts on the forum and being in touch with several users for testing, here is the outcome of the feedback:

The number of users for whom the updates do not work is approximately 15%.

The issue is caused by:
- my site not https
- user´s provider blocking mine
- my provider blocking user´s

It is hard to tell the percentage of the problem causes, I would say maybe 1:1:1.

This unfortunately is not acceptable for me, 15% is too high to ignore. I know you could argue - what about the 85% for whom this works. Well yes, but show me a software where you have features "only working for some". Whatever is available should work and if it doesnt, it shouldnt be there.

It is a problem for new users, because they would be confused by this if it didnt work.

I was also worried about server load, but given I upgraded my hosting plan, this seems to be ok.

If it was maybe 5-10%, that might still be ok, but 15-20% is too high if you consider the overall number of users. It will not be easy to again remove everything but as it stands now, it is the only way I see to continue. It was something I had in my head for quite some time, but was worried about how and if it would work. I then decided to try - and it turned out my worries were justified.

[calypso]

OK.

[heersje]

fantastic feature, really eases page management (keeping up with your tornado of updates)

[heersje]

OK, going through the emails, posts on the forum and being in touch with several users for testing, here is the outcome of the feedback:

The number of users for whom the updates do not work is approximately 15%.

Jachym do you take into account that people with no problems will most likely not send emails or post on the forum (most often you go to a forum to look for solutions for a problem). So that the success rate may be higher and in fact could well be in the 5-10% range you said to find acceptable. You would have to ask a random list of v16 users on their experience with this feature to really have a good view on the problem rate.
It works great for me but for those where it does not they can still use the old ways right?

best JP

[John B]

heersje has a valid point, Jáchym.

There are 255 members on the forum as I type. That's what - 30% of your known users?
You can bet that every single known user having problems has been in touch with you one way or another. If you are using just the OK v Not Working responses on this site as your benchmark then that gives a false impression. If you are using all the "No" contacts here and elsewhere then that must be tested against the total of users (700 - 800?)

Have you really had over a hundred customers with problems?

I am not worried either way your final decision goes, Jáchym; It's not an arduous task to do it the recent 'old' way, but for many it's a boon. For the sake of those people I would suggest that a comment on the Wiki which mentions the potential problems and includes the download/FTP method should suffice - whilst for the rest, they benefit from your rather clever 'new' way.

Oh, yes: There are plenty of programs around which require particular minimum requirements to run. If a user doesn't meet those requirements that that's it. In your case you already have an available method, one that will run as an alternative to the 'one click' one. In other words you are not disadvantaging some users you are supplying a solution for those people by keeping available the recently-current system for applying block/plug-in changes.

That's my two-bob's worth.

[wx_jon]

Jachym, if I may make a suggestion... As I noted above, it would be nice to have both download and update buttons for blocks and plugins. From what I gather, those with https problems can't even do the version checking, so for them, even the download seems like a broken feature. For others, if the downloads worked, but not the updates, you could include the option to disable updates (or block it by default). Now that this feature is out there, I think more might be disappointed to see it go than are currently disappointed not to have it.

Having said all that, for the majority of blocks I make tweaks and wouldn't use the update feature, but I still like to have it.