Textpattern Support Forum

paulyoung wrote:

Help file example #4 should be changed.

What should it be changed to? It demonstrates the first version of rloaderro’s slideshow plugin; perhaps I should add an example for slideshow2 but the help is already too big and is in danger of stopping the plugin installing (there’s a size limit). If I can compress the help any more I’ll see if I can squeeze in another example, but both versions of slideshow are very similar in approach.

I have been using the following to show the first image in my slideshow: <img src="{imagepath#1}{imagecap#1}" alt="{title#1}" />

Uli is right, that looks odd. There is no built-in replacement tag called {imagecap} so unless you made it yourself as a combo that will fail. In fact in debugging/testing modes it will probably issue a horrible warning, which I will have to fix in the next release. You should probably be using code similar to example 4:

<img src="{imagepath#1}{imagedef#1}" alt="{alt#1}" title="{title#1}" />

fwiw, the reason it works with js on is because slideshow automatically shows the first image of the slideshow, effectively overriding your incorrect “starting image”. Look again at the HTML source and you’ll probably see a bogus src url with your code.

Is it possible with your plugin and slideshow2 to rotate images of different sizes and use fade effect?
Thanks!

Thanks. What about category_title and MLP? I have 2 languages and it only shows default one.
Here is my form code:

<div class=“gallery”>
<a href=”/gallery/?c={category}”>
<txp:
{object}
</a>
{onchange:category_title}
</div>

Hi BLoke,
probably you already read it, anyway these are Steve’s suggestions for building mlp compatibles plugins.

fuls wrote:

how would you suggest to use combo with onchange?

Any combo can be used with onchange so every time it’s different it will trigger.

But honestly, I’m not sure how to do it. It was just a thought off the top of my head. It depends how many categories you have because it could be a little labour intensive. All I wondered was whether you might be able to do this:

<txp:smd_gallery combo="mycat:##cat_title_{category}##" other="" options="" here="" />

And then in your form use onchange:mycat. You’d have to manually set up snippets called cat_title_lions, cat_title_tigers and so on — where the last part matched your categories — which is not ideal and why I suggested it only as a temporary measure. But that (or something similar, perhaps generate the snippet name in the form?) might work and get you going until I have time to work out how to make smd_gallery work with MLP properly.

redbot

Yeah I know about the mechanism for doing it, but thanks for the link. In fact, it’s even easier than that now both me and Steve have MLP wrappers in our libraries. The problems I have are:

1. My MLP wrapper is in smd_lib but I don’t really want to have smd_gallery reliant on smd_lib; although there’s a lot of duplication in the two anyway so perhaps I should
2. Ideally I’d like to make the plugin detect if smd_lib or Steve’s wrapper is enabled and only offer MLP support if so. I haven’t figured out how to do that yet so it gracefully falls back to “no MLP”
3. I don’t know which of the replacement variables to put through MLP. Potentially it could be all of them, which is a lot of extra code. And what do I do if you define your own combos? I don’t know how to put those through the MLP machine because I need to supply “default” values in the plugin but I can’t supply defaults if I don’t know what your combos are going to be called :-)

That’s the main reason why smd_slimbox has MLP support but smd_gallery doesn’t (yet); slimbox has defined output but gallery does not. Any ideas from anyone gladly welcomed.

Last edited by Bloke (2008-07-10 10:48:35)