Feedback to: Textpattern CMS 4.7.0 beta 2 released

philwareham · 2018-03-22 09:59:13

Please provide any feedback here related to Textpattern 4.7.0 beta 2 released.

We appreciate all feedback. Please check this opening post and the Issue queue before raising a problem. We will endeavour to list all fixes that have been applied below, but sometimes it’s not possible to capture everything in a timely fashion. Thanks.

Issues fixed so far since first beta:

More consistent URL title when duplicating articles.
Staff Writer/Freelancer/Designer saving as Live/Sticky gives misleading notification feedback.
Sub-Copy Editor-level users cannot modify an article immediately after initial save
Categories: can no longer reassign the parent of a child element to its children! Avoids infinite tree loops.
Fixes and UX improvements for lower privilege level users.
Margin tweaks for UI elements across devices.
Checkbox and radio button visual tweaks.
Make ‘new’ links consistent throughout the interface.
Only show ‘new’ links when on saved Pages, Forms and Styles (thanks, Adi).
Hide list options for empty tables.
Add Textpack preview and tidied plugin preview step.
Improve panel layout across all privilege levels (thanks, Pete Cooper).
Permit all users to edit per-user prefs.
Fix syntax errors on PHP <5.6 (thanks, makss).
Alter working theme when saving section asset assignments (thanks, ruud).
Permit direct manipulation of $textarray as an interim fallback for legacy plugins.
Fix installation of language textpacks from plugins (thanks, Adi and jools-r).
Add pagination and search to Plugins panel.
Fix Save/Publish button interaction when changing status.
Move more panels to Ajax saves.
Add debug info to article preview step.
Only show article preview option if privileged.
Permit custom field content to be omitted in <txp:article_custom> based on the exclude attribute.
Fix pagination message when searching boolean values.
Make search impossible if no fields are chosen.
Add <+> syntax for prepend/append in wraptag attribute.
<txp:yield> fixes to permit unset attributes.
<txp:output_form> uses yield by default.
Tag builder link only appears for authors with sufficient privileges.
Fix Textile use-string-as-array bug (thanks, Pat64).
Added sync param to theme callbacks.
Only show truly active plugins in Diagnostics, and strikethrough plugin status if prefs indicate certain types are inactive (thanks, Uli).
Use correct txp. prefix for API calls, instead of api..

Last edited by Bloke (2018-04-06 08:39:21)

etc · 2018-03-23 16:40:25

We can never say enough большое спасибо, vielen Dank, muchas gracias, grazie mille, merci beaucoup and other thank you to all beta testers. Please continue testing, we could hardly find and smash all these bugs without your help!

colak · 2018-03-23 17:46:29

This seems to be minor and plugin specific. I use rvm_css and the spf_js plugins. In txp v4.6.2, in preferences>Admin, their corresponding titles are Style directory and JavaScript directory whereas in 4.7.0 beta2 their titles are parsed as rvm_css_dir and spf_js_dir.

I will of course post the above in the plugin threads as well.

Bloke · 2018-03-23 17:54:02

colak wrote #310290:

in 4.7.0 beta2 their titles are parsed as rvm_css_dir and spf_js_dir.

Those strings will need to ultimately be moved to the Textpack [prefs] group so they show up on the prefs panel. That said, I thought I’d made sure that plugins loaded their strings everywhere for backwards compatibility. Maybe it’s not working as intended.

colak · 2018-03-23 18:17:40

Bloke wrote #310292:

Maybe it’s not working as intended.

Hmmm you maybe right. I’m on a hopelessly low speed public wifi connection at the moment and my initial test with rvm_css revealed that the static file was not updated, but seems to have been updated in the db… I’ll check again properly when I go home later.

colak · 2018-03-23 18:38:59

Confirming that rvm_css does not update the static file. spf_js works as intended except the title string, mentioned above.

Last edited by colak (2018-03-23 19:05:31)

colak · 2018-03-24 06:44:35

I get a plugin related error in debug mode:

<pre dir="auto">A problem occurred while loading the plugin: <b>smd_lib</b> -> <b>8192: Methods with the same name as their class will not be constructors in a future version of PHP; smd_MLP has a deprecated constructor on line 4</b></pre>
<pre class="backtrace" dir="ltr"><code>textpattern/lib/txplib_misc.php:1397 eval()
textpattern/lib/txplib_misc.php:1419 load_plugin()
textpattern/lib/txplib_misc.php(1826) : eval()&#039;d code:1 require_plugin()
textpattern/lib/txplib_misc.php:1826 eval()
textpattern/publish.php:196 load_plugins()
index.php:107 include()</code></pre>

The smd_lib I have installed is v0.36.

etc · 2018-03-24 11:03:55

Bloke wrote #310292:

Those strings will need to ultimately be moved to the Textpack [prefs] group so they show up on the prefs panel. That said, I thought I’d made sure that plugins loaded their strings everywhere for backwards compatibility. Maybe it’s not working as intended.

In the case of rvm_css the strings are added directly to $textarray which is not used anymore. Other plugins do the same, probably.

jakob · 2018-03-24 11:49:00

etc wrote #310307:

In the case of rvm_css the strings are added directly to $textarray which is not used anymore. Other plugins do the same, probably.

I’ve noticed that in one of gocom’s too. What’s the best way to do that now? Is that written down anywhere (maybe in the plugin changes for 4.7 thread?). Or is this just a matter of using textpacks and the gTxt() function?

Bloke · 2018-03-24 20:49:32

jakob wrote #310308:

is this just a matter of using textpacks and the gTxt() function?

Yes. Shouldn’t be necessary to write to the global any more. All this stuff needs documenting more thoroughly. However, see your other question where I’ll provide a fuller answer.

etc · 2018-03-24 21:51:33

jakob wrote #310308:

is this just a matter of using textpacks and the gTxt() function?

Bloke wrote #310319:

Shouldn’t be necessary to write to the global any more.

In the case of rvm_css the only language related stuff is a string added on the fly:

  $textarray['rvm_css_dir'] = 'Style directory';

No textpack, no db record. I guess some other plugins do it too. It would be nice if we could find a way to append missing strings from $textarray for one or two dev cycles, until the authors provide proper textpacks. Switching to raw strings after update is a bit disappointing.

Bloke · 2018-03-24 22:09:05

etc wrote #310321:

It would be nice if we could find a way to append missing strings from $textarray for one or two dev cycles

I concur. I’m looking into the stuff from the other thread I mentioned above, with a view to making sure it works once and for all under those circumstances.

I’ve no current idea how (a.k.a. the best place in code) to patch it as you suggest here though. Suggestions welcome!

Last edited by Bloke (2018-03-24 22:10:05)

Textpattern CMS

Textpattern CMS support forum

#1 2018-03-22 09:59:13