Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#85 2012-06-13 15:08:59

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,852
Website

Re: r3798, r3809, r3817: Don't Panic

Happy cog… what’s that? A drunk bloke?

Offline

#86 2012-06-13 15:26:55

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 8,908
Website GitHub Twitter

Re: r3798, r3809, r3817: Don't Panic

Destry wrote:

Could that be an auto-message that pops-up, or something?

Unless there was a way of permanently disabling that I would feel that a pop-up message very obtrusive. I nevertheless agree with you that it would be cool if there was a method to alert the “publisher” that a new version is available.


Yiannis
——————————
neme.org | hblack.net | EMAP | A Sea change | NeMe @ github
I do my best editing after I click on the submit button.

Offline

#87 2012-06-13 15:33:09

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,852
Website

Re: r3798, r3809, r3817: Don't Panic

Yeah, pop-up was a poor choice of words. What I mean is just some kind of notification process, and unobtrusive is best. For example, on my mail icon, I get a number for new mail in my inbox. Maybe it could be something low-fi like that, but visible enough to actually be useful as a message.

And we can admit that these would really be targeted to client’s of Txp designers delivering custom sites who are later left to their own for updating, etc. Sites can go a very long time without being updated (security issue) because nobody thinks to do it. This could be helpful in that context, get people thinking abou it.

Last edited by Destry (2012-06-13 15:37:51)

Offline

#88 2012-06-13 15:44:18

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,555
Website GitHub Mastodon

Re: r3798, r3809, r3817: Don't Panic

I’d imagine that would be quite easy to do if/when RPC via JSONP and modals are implemented someday. A notification icon, which when clicked on brings up a modal listing the update and changelog, with a way of directing to the update download.

Anyway, keep the ideas flowing.

Offline

#89 2012-06-13 15:51:42

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 10,795
Website GitHub

Re: r3798, r3809, r3817: Don't Panic

all

In 4.5.0 there is a check for a new version done on the Diagnostics page, delivered as part of the usual pre-flight check messages. While this isn’t ‘visible’ per se unless you visit the panel, it’s more visible than being tucked away on the prefs screen behind a button.

If people want this (cached-for-24-hours-or-so (or more?)) check to be performed somewhere more immediately visible then make some suggestions where it would fit. Or, as Phil says, we could delay it and do it right when we get time.

I would be tempted to do this kind of thing as part of an overall improvement for upgrading. My holy grail at the moment, for example, is Piwik. When a new version is available, a side box appears in the admin panel. If you click the upgrade link you get taken to a page that explains what’s going to happen. You get a chance to download the stuff manually and do it yourself if that’s your poison, or click a button which downloads the latest file, unpacks it for you, then moves onto a step to upgrade the DB tables. Again, it offers you the option to do it automatically and also lists the exact database function calls its going to make in a collapsible textarea so you can copy them out in case the upgrade goes tits up and you need to intervene.

In three years of using it, it’s never broken and I’ve never had to do anything manually, and I’m up-to-date within thirty seconds of clicking the Upgrade Now link. It’s fantastic. If we could ever get a slick operation like that going, I’d love it.

/me puts away his dreaming slippers

Last edited by Bloke (2012-06-13 15:53:40)


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#90 2012-06-13 18:10:43

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 8,908
Website GitHub Twitter

Re: r3798, r3809, r3817: Don't Panic

Bloke wrote:

If people want this (cached-for-24-hours-or-so (or more?)) check to be performed somewhere more immediately visible then make some suggestions where it would fit. Or, as Phil says, we could delay it and do it right when we get time.

It is TEXTpattern and the page we visit most is the write page. Having said that, I think that only publishers and designers should be able to see the message and not anybody else.

I also think that the message should just be a short linked text somewhere near the bottom (something like: Update.4.6 now available)

I’m also open to alternative arguments though:)

Last edited by colak (2012-06-13 18:12:24)


Yiannis
——————————
neme.org | hblack.net | EMAP | A Sea change | NeMe @ github
I do my best editing after I click on the submit button.

Offline

#91 2012-06-13 18:15:13

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 8,908
Website GitHub Twitter

Re: r3798, r3809, r3817: Don't Panic

Bloke wrote:

… Piwik … It’s fantastic. If we could ever get a slick operation like that going, I’d love it

+1 :)


Yiannis
——————————
neme.org | hblack.net | EMAP | A Sea change | NeMe @ github
I do my best editing after I click on the submit button.

Offline

#92 2012-06-13 18:20:16

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,555
Website GitHub Mastodon

Re: r3798, r3809, r3817: Don't Panic

Whatever method is chosen for announcing an update, it’ll need a way to dismiss it.

Offline

#93 2012-06-13 19:09:01

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 8,908
Website GitHub Twitter

Re: r3798, r3809, r3817: Don't Panic

philwareham wrote:

Whatever method is chosen for announcing an update, it’ll need a way to dismiss it.

Cookies maybe?


Yiannis
——————————
neme.org | hblack.net | EMAP | A Sea change | NeMe @ github
I do my best editing after I click on the submit button.

Offline

#94 2012-06-13 19:26:37

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,555
Website GitHub Mastodon

Re: r3798, r3809, r3817: Don't Panic

No. Database record.

Offline

#95 2012-06-13 19:56:11

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 10,795
Website GitHub

Re: r3798, r3809, r3817: Don't Panic

A check-for-updates frequency pref? Options like, I dunno, 1 week, 1month, 6 months? With default of a month. (EDIT: given our release cycle frequency, 1 week might be a bit optimistic! Maybe 1, 3, and 6 months?)

Then I’d go for automatically showing the ‘new version available’ message as a standard Announce message (which under 4.5.0 is a nice green box) when you log in. With a link to .com download area in the message. When you next visit any tab, it’s gone (because that’s the nature of such flash messages). Thereafter it won’t nag again until the update frequency has passed.

Visiting the Diagnostics panel at any time would show the upgrade message, as it does now in SVN.

How’s that?

EDIT2: And like Colak suggests, this’d be a Publisher-level message only. Or maybe Managing Editor too? Not sure. Will take advice on the most appropriate privs to use.

Last edited by Bloke (2012-06-13 20:04:19)


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#96 2012-06-14 07:47:22

wet
Developer Emeritus
From: Schoerfling, Austria
Registered: 2005-06-06
Posts: 3,275
Website

Re: r3798, r3809, r3817: Don't Panic

Bloke wrote:

EDIT2: And like Colak suggests, this’d be a Publisher-level message only. Or maybe Managing Editor too? Not sure. Will take advice on the most appropriate privs to use.

I’d need another option: No one. I don’t want my clients to mess with this, even if they are highly privileged.

Offline

Board footer

Powered by FluxBB