Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Textpattern CMS 4.7.0 beta released
Updated a dev site to test 4.7. In the diagnostics I get Missing files: /config-dist.php…
More to come
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
towndock wrote #309742:
What are the relative speed differences between 4.5.7 & 4.6.2 & 4.7?
Since 4.6 the code is more object-oriented, which tends to slow things down. But on the other hand, we have optimized the parser, so:
- 4.5 is faster on “empty” pages, but you’ll hardly see the difference between, say, 0.05s and 0.07s;
- 4.6 is ~15% faster on pages with many tags or loops. 4.7 is a bit slower than 4.6 because of new features, but still 10% faster than 4.5 in this case.
For an average site there should be no noticeable speed difference.
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
Gomedia wrote:
Change “Create new” to “Create new article”
Bloke wrote:
It takes up too much space with the extra word. As I mentioned, I’m all for shortening the others if it doesn’t impact usability.
Sorry to jump in here.
When I first read Adi’s notes, I thought he meant the redundancy was “Create new”, because it is redundant. You need “article” because that’s what the thing is, the noun. You need “create” because that’s the action to take, the verb. But you don’t need “new,” the needless adjective, because its redundant to the fact one is creating something for the first time (thus new). So the shortened string could be “Create article” and it would be orthographically correct.
Says the editor.
Probably helps translators too.
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
colak wrote #309819:
Updated a dev site to test 4.7. In the diagnostics I get
Missing files: /config-dist.php…
Yup, I see the same thing. Probably an overzealous checksums generating script.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
phiw13 wrote #309827:
Yup, I see the same thing. Probably an overzealous checksums generating script.
That has been fixed this morning, thanks. As has some texts to make ‘Create new…’ consistent as discussed earlier in this thread. I’ve also rephrased the ‘force-refresh cache’ message as mentioned by Philippe.
On the subject of primary, secondary and tertiary action buttons. They are based on what I feel the priority of the action is, and I’ve already tried various button combinations in the past before settling on this schema.
Therefore primary actions (such as ‘Save’) use the yellow highlighted buttons, secondary actions (such as ‘Create new…’ on list pages) use greyed buttons, tertiary actions (such as ‘Create new…’ when on a writing page) use link with icon.
I’m also not too keen on peppering the buttons with icons too – the only reason I’ve done that on languages panel is to aid users in the event of them seeing the panel in a language they don’t understand.
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
philwareham wrote #309829:
That has been fixed this morning, thanks. As has some texts to make ‘Create new…’ consistent as discussed earlier in this thread. I’ve also rephrased the ‘force-refresh cache’ message as mentioned by Philippe.
Not sure about “create new author` personally, but OK. Thank you for improving the “force refresh” dialog.
I’m also not too keen on peppering the buttons with icons too – the only reason I’ve done that on languages panel is to aid users in the event of them seeing the panel in a language they don’t understand.
+1 on that. There are already quite a lot of icons. adding more would make the whole thing really cluttered.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
Hmmm, ‘Add new author’ or ‘Create new author’ – I’m still not sure.
Regarding ‘Users’ as opposed to ‘Authors’ – most of the admin texts refer to users as authors currently (and in past releases).
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
There’s a lot of pushback on the term “user” in UX these days. Author is good in my book.
And the mug agrees. ☕️
<txp:author />
The baseline. On top of that you can also be publisher, editor, freelancer, even the designer. ;)
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
phiw13 wrote #309827:
Probably an overzealous checksums generating script.
Yep, mea culpa. I’ll get the script to omit that one, thanks.
Destry wrote #309821:
You need “create” because that’s the action to take, the verb. But you don’t need “new,” the needless adjective, because its redundant to the fact one is creating something
I think I like this. Shorter, leaner and retains the context. Can we? Can we? Please?
philwareham wrote #309829:
I’m also not too keen on peppering the buttons with icons too
No worries. You’re right that could look a bit iconfusing™. The Files panel’s header area is already a bit, well, all over the shop on mobile, with the various form controls for image upload, category assignment, assign missing file dropdown, search box, clear search link, and list options all wrapping. Could probably do with some love one day but I’ve no idea how to present it better right now…
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
Bloke wrote #309846:
I think I like this. Shorter, leaner and retains the context. Can we? Can we? Please?
While I can change the English Textpacks no problem – I am not prepared to delete all the translations of these phrases that are already translated into other languages.
So yes, in part, we can do this. It’s kind of all or nothing on Crowdin: You either keep current translations or you blow them away and force translators to re-translate those strings again. Of course current translators can edit their translations if they wish.
The Files panel’s header area is already a bit, well, all over the shop on mobile, with the various form controls for image upload, category assignment, assign missing file dropdown, search box, clear search link, and list options all wrapping. Could probably do with some love one day but I’ve no idea how to present it better right now…
Files and images panels will be getting a UX makeover in Textpattern 4.8 (along with adding that pesky image grid we’ve always talked about).
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
philwareham wrote #309848:
While I can change the English Textpacks no problem – I am not prepared to delete all the translations of these phrases that are already translated into other languages.
If it’s too much ruckus, it’s fine to leave it. We could always just change the English for now and the rest can follow over time if necessary. It’s an English thing anyway, so may not even affect other languages.
Is there no way for translators to be notified in CrowdIn that a string has changed and may need a tweak, or they can decide the translation is fine as-is so it can be marked as “seen it, no action required”? You have to either let them figure it out or force the issue by deleting it?
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
Bloke wrote #309850:
We could always just change the English for now and the rest can follow over time if necessary.
A short blog post with relevant details and link (Crowdin?), a tweet and forum post to point to it. Let the rest follow.
It’s an English thing anyway, so may not even affect other languages.
Not detrimentally, perhaps, but the refined grammar should help translations be more concise too.
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
On debug mode I get
Tag error: <b><txp:php>
if ($_POST['submit']) {
$url = $_POST['site'].$_POST['terms'];
if ($_POST['section'] && ($_POST['section'] != 'null')) $url = $url.'&s='.$_POST['section'];
header('Location: '.$url);
} else {
header('content-type: text/html; charset=utf-8');
}
</txp:php></b> -> <b> Notice: Undefined index: submit while parsing form <strong>None</strong> on page <strong>default</strong></b></pre>
<pre class="backtrace" dir="ltr"><code>textpattern/publish/taghandlers.php:4214 eval()
php()
textpattern/vendors/Textpattern/Tag/Registry.php:116 call_user_func()
textpattern/lib/txplib_publish.php:596 Textpattern\Tag\Registry->process()
textpattern/lib/txplib_publish.php:520 processTags()
textpattern/lib/txplib_misc.php:4418 parse()
textpattern/publish.php:571 parse_page()
index.php:116 textpattern()On the plus side the following plugins appear to be working just fine
act_if_mobile-0.1.2 (modified)
adi_matrix-2.0
adi_notes-1.3.1
adi_search_db-0.3
fha_time_diff-0.23 (modified)
glx_if-0.7 (modified)
kuo_file_stats-0.1
mdn_count-1.4 (modified)
pap_contact_cleaner-0.1
pat_speeder-0.7.3
rah_external_output-1.0.4
rah_repeat-1.0.1 (modified)
rah_sitemap-1.3.0
rss_admin_db_manager-4.4
rvm_css-1.1
rvm_privileged-0.5
smd_if-0.91
smd_lib-0.36
smd_where_used-0.2
smd_wrap-0.20
spf_js-0.51
stm_javascript-0.1
zem_contact_reborn-4.5.0.0
zem_redirect-1.2.1
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Feedback to: Textpattern CMS 4.7.0 beta released
colak wrote #309862:
On debug mode I get…
Yiannis, I think that is some code of yours that is complaining. If you correct the entities you get:
<txp:php>
if ($_POST['submit']) {
$url = $_POST['site'].$_POST['terms'];
if ($_POST['section'] && ($_POST['section'] != 'null')) $url = $url.'&s='.$_POST['section'];
header('Location: '.$url);
} else {
header('content-type: text/html; charset=utf-8');
}
</txp:php>which gives you
Notice: Undefined index: submit while parsing form 'None' on page 'default'That snippets waits for some incoming form input that is posted from another page. If you’re calling the page on its own (where it’s not receiving input from somewhere else), it doesn’t know about the submit event and says it’s not defined.
Change your first line to: if (isset($_POST['submit'])) { and that should silence the error. Pls double-check that your form processing still works as desired.
TXP Builders – finely-crafted code, design and txp
Offline