Textpattern Support Forum

The idea behind the ZRC_lang plugin is that anyone can easily modify the plugin to his own language (and it’s really easy to do that), using error messages in a way they like best (people tend to disagree on what the right translation is).

Where is the most appropriate place for me to file an update for the plugin?

Case: With Textpattern 4.4.0 (?) split() was deprecated and explode() is to be used instead (Here is an example in classTextile.php where it was updated) and currently the the plugin has one line which uses split() throwing an error—I have just fixed this on my own though when searching about this problem I found a few sites that currently have the same problem (And I plan on emailing them soon too to let them know):

http://skywatchersmusic.com/contact
http://brownhilltreeco.com/request-info

I fixed this by simply editing line 538 in the plugin from:
$list = array_map('trim', split($delimiter, preg_replace('/[\r\n\t\s]+/', '
To..
$list = array_map('trim', explode($delimiter, preg_replace('/[\r\n\t\s]+/', '

Last edited by Dorian Graph (2011-07-01 01:26:05)

Side: The in-thread search function is a game changer! – thanks Ruud.

To topic…

ruud wrote:

Christian, edit the plugin code or use javascript (a variation on this script could easily do it. Instead of filling the value attribute with the placeholder attribute, you can do it the other way around. Same effect)

There’s no chance the HTML 5 placeholder attribute will ever be added?

It’s something that can be used more and more frequently to improve design possibilities as well form usability. For example, I’m fond of this idea used by Insite, where required fields are not marked, rather the optional fields are by using an “Optional” placeholder to clearly show the distinction without need for silly asterisks or whatever on labels.

To be clear, plugin mods are not a problem for me with my own sites. But for clients sites, which I rarely maintain after hand-over (it’s a losing money game against time), I don’t want to have to add that level of detail (plugin modifications) to client documentation. Just the idea of having to update Txp’s install, let alone plugins in relation, is a bit of a space bender for some clients who don’t have web staff on hand.

Just a thought.

Sounds good. Thanks.

jakob wrote:

I have made an own modded version of zcr with the placeholder attribute and a few other things, although it doesn’t yet have full support for all html5 form elements. I’ll send you both a copy…

Hi Jakob, could I ask for a copy too, please.