Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#21 2016-10-06 10:30:50
- Bloke
- Developer
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 8,524
- Website
Re: Feedback to: Textpattern CMS 4.6.1 released
NicolasGraph wrote #301995:
Same; I thought it was my fault because I had the problem on only one install; but as far as I understand it is because of a different production status…
Hehe, that’s the downside of having clever beta testers: you’re all too resourceful!
I think what also didn’t help was that txp_using_svn
(i.e. our “is in dev” flag) wasn’t reset to true
in the 4.6.1 branch, for some reason. At least, I can’t find where I did it in the commit history. So any beta testers may have been testing as if the release was ‘final’.
Note to self: be more thorough next time.
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
#22 2016-10-06 18:40:50
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,168
Re: Feedback to: Textpattern CMS 4.6.1 released
I just updated a 4.6.0-dev (i.e. a pre-beta, from April) to 4.6.1. All went well, I could visit all tabs. Thank you, guys!
Small “but” as I didn’t expect the following:
On visiting the Diagnostics window I’ve now a v4.6.1 (text area message) and the pre-flight note “New Textpattern version 4.6.1 available for download” (probably caused by my unorthodox version combo).
smd_prognostics, though, doesn’t have the update reminder in its “Advice” section any longer.
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
#23 2016-10-06 19:05:34
- Bloke
- Developer
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 8,524
- Website
Re: Feedback to: Textpattern CMS 4.6.1 released
uli wrote #302005:
“New Textpattern version 4.6.1 available for download” (probably caused by my unorthodox version combo).
Yep, thanks for the report. The pre-flight check uses the DB version, which will still erroneously be reported as 4.6.0, but the Diagnostics panel itself uses the one from the index.php
file, which is correctly identified as 4.6.1. *sigh*
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
#24 2016-10-06 23:48:10
- bici
- Member
- From: vancouver
- Registered: 2004-02-24
- Posts: 1,383
- Website
Re: Feedback to: Textpattern CMS 4.6.1 released
ok. so bottom line. Is it now full proof to upgrade to 4.6.1?
…. texted postive
Offline
#25 2016-10-07 10:28:10
- Bloke
- Developer
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 8,524
- Website
Re: Feedback to: Textpattern CMS 4.6.1 released
bici wrote #302007:
Is it now full proof to upgrade to 4.6.1?
Depends on your setup. If you’re running in Live mode, you can do it without issue, the only “problems” you’ll likely spot are:
- your version string in the database won’t be set correctly (you can fix it by hand if you like).
- your Diagnostics will say there’s a new version available (because of the version issue: will go away if you edit the version string).
- custom upgrade scripts may not run.
So, by all means do it, or wait a few days for 4.6.2 to fix these niggles.
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
#26 2016-10-07 12:40:00
- Sunfoot
- Member
- From: Felanitx
- Registered: 2009-02-07
- Posts: 14
- Website
Re: Feedback to: Textpattern CMS 4.6.1 released
It works for me! I really appreciate all your efforts and works to maintain this project!
Offline
#27 2016-10-07 12:44:05
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,168
Re: Feedback to: Textpattern CMS 4.6.1 released
Bloke wrote #302013:
will go away if you edit the version string
In case it makes a difference for the 4.6.2 code: It remains here after editing the prefs string.
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
#28 2016-10-07 13:14:26
- Bloke
- Developer
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 8,524
- Website
Re: Feedback to: Textpattern CMS 4.6.1 released
uli wrote #302016:
In case it makes a difference for the 4.6.2 code: It remains here after editing the prefs string.
Thanks for the report. I’ll check the update notification code too, as it may need to change now we’ve refactored the update system.
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
#29 2016-10-07 13:28:01
- gaekwad
- Member
- From: People's Republic of Cornwall
- Registered: 2005-11-19
- Posts: 2,403
Re: Feedback to: Textpattern CMS 4.6.1 released
Bloke wrote #302013:
So, by all means do it, or wait a few days for 4.6.2 to fix these niggles.
Should we expect a beta, Stef?
Offline
#30 2016-10-07 13:39:55
- Bloke
- Developer
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 8,524
- Website
Re: Feedback to: Textpattern CMS 4.6.1 released
@Uli: just wait :-) The update message will disappear within 24 hours. It only checks once a day maximum to avoid hammering the server. In the meantime it’ll keep reading the old message from cache.
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