Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Textpattern CMS 4.6.0 released
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.
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
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.
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
Online
Re: Feedback to: Textpattern CMS 4.6.0 released
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)
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
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.
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
Thanks for this confirmation. The problem is also happening on individual article pages, so maybe a different problem?
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
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.
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
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.phpfile with the patched version.
Excellent, that has solved it!
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
@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!
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
@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.
Does that help?
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
philwareham wrote #301739:
@NicolasGraph.
You just need to add a class of
txp-listto the<table>tag, and preferably an outerdiv class="txp-listtables"to allow for responsive overflow.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)
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
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.
Offline
Re: Feedback to: Textpattern CMS 4.6.0 released
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.
Offline