Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#37 2018-03-09 09:36:10

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,564
Website GitHub Mastodon

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

#38 2018-03-09 09:44:35

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,909
Website

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

#39 2018-03-09 09:46:01

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,564
Website GitHub Mastodon

Re: Feedback to: Textpattern CMS 4.7.0 beta released

Destry wrote #309835:

And the mug agrees. ☕️

Ha ha , OK.

Offline

#40 2018-03-09 10:38:18

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 11,299
Website GitHub

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.

Txp Builders – finely-crafted code, design and Txp

Offline

#41 2018-03-09 10:54:57

philwareham
Core designer
From: Haslemere, Surrey, UK
Registered: 2009-06-11
Posts: 3,564
Website GitHub Mastodon

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

#42 2018-03-09 11:11:53

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 11,299
Website GitHub

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.

Txp Builders – finely-crafted code, design and Txp

Offline

#43 2018-03-09 12:10:09

Destry
Member
From: Haut-Rhin
Registered: 2004-08-04
Posts: 4,909
Website

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

#44 2018-03-09 16:20:47

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 9,037
Website GitHub Mastodon Twitter

Re: Feedback to: Textpattern CMS 4.7.0 beta released

On debug mode I get

Tag error: <b>&lt;txp:php&gt;
if ($_POST[&#039;submit&#039;]) {
$url = $_POST[&#039;site&#039;].$_POST[&#039;terms&#039;];
if ($_POST[&#039;section&#039;] &amp;&amp; ($_POST[&#039;section&#039;] != &#039;null&#039;)) $url = $url.&#039;&amp;s=&#039;.$_POST[&#039;section&#039;];
header(&#039;Location: &#039;.$url);
} else {
header(&#039;content-type: text/html; charset=utf-8&#039;);
}
&lt;/txp:php&gt;</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-&gt;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

#45 2018-03-10 08:35:16

jakob
Admin
From: Germany
Registered: 2005-01-20
Posts: 4,628
Website

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

#46 2018-03-10 08:51:43

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 9,037
Website GitHub Mastodon Twitter

Re: Feedback to: Textpattern CMS 4.7.0 beta released

Thanks so much Julian, I’ll be checking it tomorrow as we are flat out now with guests. The script is here and your solution seems very easy!!!


Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.

Offline

#47 2018-03-11 07:18:47

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 9,037
Website GitHub Mastodon Twitter

Re: Feedback to: Textpattern CMS 4.7.0 beta released

jakob wrote #309870:

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.

That did it!! no errors now


Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.

Offline

#48 2018-03-15 20:06:55

CodeWalker
Member
From: Hampshire, UK
Registered: 2010-01-08
Posts: 110
Website

Re: Feedback to: Textpattern CMS 4.7.0 beta released

Oh man. Totally excited to mess with Textpattern again after some time away. The new features look awesome.

I’m just leaving a message here to say that i’ve just installed the beta on Laravals Valet running on High Sierra with PHP 7. This is basically nginx under the hood with some fancy pants dnsmasq stuff on top. look ma, no server :)

I was expecting some bumps but it went totally without a hitch.

Good job chaps :)

Offline

Board footer

Powered by FluxBB