Textpattern Support Forum

stephan wrote:

I do not wish to type the entire thing in each time

I think this was covered earlier in the thread. Although it seemed that masa couldn’t get upm_quicktags going in the latest Txp (and I couldn’t figure it out, though admittedly I didn’t put much effort into it) I’d wager Quick Tags are your best bet for offering this kind of functionality.

I need some jump-start: The plugin is activated, smd_macro is compatible with my TXP version, I copied the tag name from the macro tab, but my tag is displayed literally in the source code. What might be the reason?

This is my tag:

<txp:bildzoom Beschreibung="Wallachei 1" Gruppenname="wallachei" Grosses-Bild-ID="149" Kleines-Bild-ID="54" />

I also tried all lowercase attributes, but no luck.

Hi Stef,

this is the file contents:

[bildzoom2]
description = "Lightbox"
attributes[] = "Beschreibung||text"
attributes[] = "Gruppenname|wallachei|gruppe"
attributes[] = "Grosses-Bild-ID||groß"
attributes[] = "Kleines-Bild-ID||klein"
definition = "PGEgdGl0bGU9Int0ZXh0fSIgY2xhc3M9ImZjeWJ4IiByZWw9IntncnVwcGV9IiBocmVmPSJodHRwOi8vbWFyaW5hLWJydW5vcmkuZGUvaW1hZ2VzL3tncm/Dn30uanBnIj48dHhwOmltYWdlIGNsYXNzPSJmbG9hdC1yIiBpZD0ie2tsZWlufSIgLz48L2E+"

Thanks for taking the time to look into it!
Uli

Uli

A few things. All of them to do with the plugin being too limited:

1. At present, using dashes is not a good idea in attribute names. Switching to underscores made the tag work for me. I think this might be a PHP restriction as I don’t think variable/attribute names can contain dashes (not sure). I should probably outlaw their use in the plugin if that’s the case. Will fix either way.
2. Your attributes should probably be defined in all lower case. I’m not sure how much difference it actually makes — probably not a lot — but it may be that the plugin assumes you’ll be using them lower case so it could be getting confused
3. Using groß as a replacement is likely to confuse things because the column names aren’t defined as UTF-8. When I import the macro, for example, the replacement text is gro?? on my server. That needs fixing in the next release.

To summarize, swap dashes for underscores and stick to ASCII attribute names/replacements. Using lower case is a last resort if the previous two workarounds don’t have any impact.

A more international-friendly version of the plugin will be available when I get a chance. Sorry for the headaches and short-sightedness of the code.

uli wrote:

The hyphens were inserted by the plugin itself

Oh lordy me, I’ll have to tend to that: it’s embarrassing. Thanks for letting me know.