Feedback to: Textpattern CMS 4.6.0 released

johnstephens · 2016-09-15 20:16:36

Not sure

Bloke wrote #301552:

An unfortunate side-effect of either a) running the update twice (perhaps because of a failed first attempt), or b) running the update on a server that has tight permissions that disallow write access to the core files, or c) having run a beta and then upgrading to the final.

Not sure, but it was probably “a”.

I didn’t use the beta on this site, but I did run into another problem before this came up. I culled and upgraded all the plugins before doing the Texpattern upgrade. Then I copied all the Textpattern 4.6.0 files into my document root and updated .htaccess. When I went back to the CMS and clicked “Log Out” from the 4.5.7 interface, the site threw a PHP error from the new textpattern/index file. After some head-scratching, I checked the server’s PHP version and found it was running 5.2 series! So I bumped it to PHP 5.6 series, ran the upgrade, and then bumped it to the latest stable version of PHP 7.

Last edited by johnstephens (2016-09-15 20:17:15)

Bloke · 2016-09-18 09:18:15

Please would anybody who has a spare ten minutes and any version of MySQL (or MariaDB / Percona at a push) please test this patch. It’s a potential fix for the date upgrade bug that some people encounter, and we’d appreciate some field reports to see if it works under various environments.

If you’re able to help out by performing an upgrade from 4.5.7 to the patched 4.6.0, it would really be of benefit, thank you in advance.

Bloke · 2016-09-18 17:07:17

jstubbs wrote #301317:

Theme classic (classic_theme) failed to load properly from file...... …then nothing happens which isn’t great for new users.

I’ve added a phrase about refreshing the page, as discussed in this GitHub issue. I tried doing an automatic refresh after five seconds, but the problem with that is if your theme goes up the swanny while you (or another user: think someone else tinkering with admin themes) are posting a new article, the auto-refresh doesn’t repost and you lose your edits. If, however, you manually refresh, the browser asks if you want to repost and your article is then stored.

This is one of those situations where we could try and be clever, but it’s bound to backfire at some point so the simplest solution — the lowest common denominator — is actually the best. We may also alter the upgrade instructions to make reference to setting your theme to Hive (if possible) prior to logging out of your previous installation to smooth the upgrade process.

Dragondz · 2016-09-20 09:53:30

Hi

Upgradded a website from 4.5.7 to 4.6, the website was still in early development, i was surprised to not have any message of updating when going to website/textpattern/ i was afraid that the update had not be applyed but checking the backend all seemed ok and no error message in the diagnose tab.

I did some changes on the installed plugins to register their tag but it s ok now.

Thanks for this release guy.

PS: Maybe add a message when the upgrade is done instead to make it silent could be good.

Bloke · 2016-09-20 10:27:14

Dragondz wrote #301630:

Maybe add a message when the upgrade is done instead to make it silent could be good.

Glad the upgrade went well, and thanks for the feedback.

Regarding the ‘installation succeeded’ message, we’re formulating a plan for 4.7 that involves improving the flashy message thing so we can add upgrade info to it on first load. We also plan to drop you onto the Admin->Diagnostics panel by default, instead of the Languages panel, with some extra info to help you get started faster.

hidalgo · 2016-09-24 08:09:41

I appear to have a problem with <txp:if_expires>...</txp:if_expires> returning the contained content even where no expiry is set for that article. It worked correctly in 4.5.7 prior to updating. My PHP version is 5.3.3 if that helps.

Last edited by hidalgo (2016-09-24 08:26:30)

etc · 2016-09-24 09:17:32

My guess would be that you are using <txp:if_expires>...</txp:if_expires> in article list content? If so, then it’s a bug (my bad!) already patched in 4.6.1. You can fix it by wrapping this block in <txp:if_individual_article>...</txp:if_individual_article>. Please check and report back, and sorry for the trouble.

hidalgo · 2016-09-24 10:05:33

Thanks for this confirmation. The problem is also happening on individual article pages, so maybe a different problem?

etc · 2016-09-24 10:20:59

hidalgo wrote #301722:

Thanks for this confirmation. The problem is also happening on individual article pages, so maybe a different problem?

Arghh.. not really, the same silly bug. Sorry, all I can suggest until 4.6.1 is released is to replace textpattern/publish/taghandlers.php file with the patched version.

hidalgo · 2016-09-24 10:43:42

etc wrote #301723:

Arghh.. not really, the same silly bug. Sorry, all I can suggest until 4.6.1 is released is to replace textpattern/publish/taghandlers.php file with the patched version.

Excellent, that has solved it!

NicolasGraph · 2016-09-26 09:03:56

@philwareham; could we have some default styles available for tables in plugin help tabs in the future? There is no border or background and no padding for now. Thanks!

philwareham · 2016-09-26 09:08:38

@NicolasGraph.

You just need to add a class of txp-list to the <table> tag, and preferably an outer div class="txp-listtables" to allow for responsive overflow.

See reference here.

Does that help?

NicolasGraph · 2016-09-26 09:27:12

philwareham wrote #301739:

@NicolasGraph.

You just need to add a class of txp-list to the <table> tag, and preferably an outer div class="txp-listtables" to allow for responsive overflow.

See reference here.

Does that help?

It could, but table(txp-list). as no effect… The class is not set in the source code the plugin help page; probably related to this.

Last edited by NicolasGraph (2016-09-26 09:27:36)

philwareham · 2016-09-26 09:32:52

Hi.

To be honest I’d use HTML for your plugin help files instead of Textile, since I’m reducing the hardcoded core reliance on Textile gradually.

NicolasGraph · 2016-09-26 09:36:54

philwareham wrote #301741:

Hi.

To be honest I’d use HTML for your plugin help files instead of Textile, since I’m reducing the hardcoded core reliance on Textile gradually.

Ok, I’ll do that; thanks Phil.

Textpattern CMS

Textpattern CMS support forum

#46 2016-09-15 20:16:36

Re: Feedback to: Textpattern CMS 4.6.0 released

Bloke wrote #301552:

#47 2016-09-18 09:18:15

Re: Feedback to: Textpattern CMS 4.6.0 released

#48 2016-09-18 17:07:17

Re: Feedback to: Textpattern CMS 4.6.0 released

jstubbs wrote #301317:

#49 2016-09-20 09:53:30

Re: Feedback to: Textpattern CMS 4.6.0 released

#50 2016-09-20 10:27:14

Re: Feedback to: Textpattern CMS 4.6.0 released

Dragondz wrote #301630:

#51 2016-09-24 08:09:41

Re: Feedback to: Textpattern CMS 4.6.0 released

#52 2016-09-24 09:17:32

Re: Feedback to: Textpattern CMS 4.6.0 released

#53 2016-09-24 10:05:33

Re: Feedback to: Textpattern CMS 4.6.0 released

#54 2016-09-24 10:20:59

Re: Feedback to: Textpattern CMS 4.6.0 released

hidalgo wrote #301722:

#55 2016-09-24 10:43:42

Re: Feedback to: Textpattern CMS 4.6.0 released

etc wrote #301723:

#56 2016-09-26 09:03:56

Re: Feedback to: Textpattern CMS 4.6.0 released

#57 2016-09-26 09:08:38

Re: Feedback to: Textpattern CMS 4.6.0 released

#58 2016-09-26 09:27:12

Re: Feedback to: Textpattern CMS 4.6.0 released

philwareham wrote #301739:

#59 2016-09-26 09:32:52

Re: Feedback to: Textpattern CMS 4.6.0 released

#60 2016-09-26 09:36:54

Re: Feedback to: Textpattern CMS 4.6.0 released

philwareham wrote #301741:

Board footer