Revo: How do you setup your slideshows?

I’ve been trying to figure out the best way to setup a slideshow/carousel in Revo.

The slideshow would ideally need to have an overlaying caption, links to the next items, and clicking the whole slide would take the visitor to a different page; (with maybe another smaller caption underneath the title), something like this:




I’ve come up with a few ideas but I’m not sure which is best:

• Setup some TVs, [[*slideshow.image]], [[*slideshow.caption]], [[*slideshow.link]], [[*slideshow.description]], etc and on the front-end powered it by an external jQuery plugin - but then I’d have to duplicate these to the Resource for every slide needed in the slideshow, and it wouldn’t be easy to add more slides later.


• Make a "slideshow" template and create sub-Resources inside the parent page. Then on the front-end use getResrouces and also powered it by jQuery - then each Slideshow Resource is a slide itself, adding some TVs for the image, etc - this idea seems a bit counterintuitive, Resources are supposed to be actual webpages and not elements of the website; using this method could also confuse the client.


• I was also playing around with this plugin: https://github.com/Bruno17/multiItemsTv - but at the moment it’s not in the Package Management updater, so it breaks every time you upgrade the CMS - and it doesn’t support images and text fields together.


• I also tried Galleriffic with the Gallery plugin, but there didn’t seem to be a way to make the images link to a Resources instead of just clicking to the next image - and it was tricky to add captions.

So how do you guys setup this sort of thing up in Revo?

Quote from: Adam at Dec 10, 2010, 08:55 AM

Resources are supposed to be actual webpages and not elements of the website; using this method could also confuse the client.

I see that a bit differently. If resources are always supposed to be the same thing as pages, why do we call them "resources" instead of "pages"?

Custom resource types with user-defined fields are a great way, in my opinion, to leverage the existing MODx infrastructure instead of having to develop a whole new admin interface for things like slideshows.

Provided the custom resources are in a separate section (parent resource) I don’t think the clients will be too badly confused. To the contrary, I think they will appreciate being able to edit the slideshow in the same way that they edit their pages, just with different fields.

I’ve had clients that could simply not understand how it could be there.

Custom resource types seems like the solution to differentiate properly to make sure those clients that don’t understand see the connection.



I would probably use a container for a slideshow, and subresources as slides. And then getResources with some solution like jQuery to display it all properly.

Hello Marc,

I also do it with jQuery, but may be not as elegant as you describe your solution with subressources. Could be done with Ditto too, I think, as alternative to getResources (but I’m speaking for Evo, dont know yet if Ditto is a core snippet in Revo, too??).

What I did was defining 6 TVs for the images and 6 TVs for the overlay text, and when there are less than 6 images Phx if statements find out and only show li elements with images for existing ones. But we defined 6 as maximum, with higher image counts I definitely would have chosen subressources retrieving with Ditto and special Ditto template chunks. It’s not the standard jQuery Circle UI, but jQuery Train Slider http://codecanyon.net/item/jquery-train-slider-v10/92074 which I found an interesting alternative.

Interesting topic in any case as JS coded slideshows and image galleries have to replace Flash more and more ... and intersting how to do it in Revo, as this will be the future too ...

Hey Guys,

this is something actually whats holding me back from fully embracing MODx Revo. It’s true that jQuery has already been accepted as a substitute to Flash, if not the main technique to embed images, docs etc. What could be done with maxigallery in Evo is now missing. I’m a designer and I have some basic PHP knowledge. Similar tasks, where you want images embedded in a page/div, can easily be done in WP with the get attachments as images call and even easier in Textpatttern where you just have to type in the ID nr of the image/images in the "Article image" property (a kinda custom field). I too have done it with TVs, but it’s a limited approach after all. What would be a perfect scenario is if one could have the ability to duplicate the TVs associated with the page on the fly. In such case you wouldn’t have to worry about the limit of the images. You would just make as many as you like.
Any PHP gurus?

there is imagelistTV custom-TV-input-type for multiple title/image-pairs and soon multiItemsGridTV

U prolly mean something like this only for REV:
http://www.kunane.com/modx/multi-image-tv.html

I have not used it for EVO yet thow.
Would be great if it’s implemented somehow into the basic cms

Now that is SOMETHING! Thank’s Bruno! Works like a charm!
Looking forward to test the multiItemsGridTV.

see here:
https://github.com/Bruno17/multiItemsGridTV/wiki

I actually prefer to set up an unpublished parent resource (in this case called slideshow images) and a separate static resource for each image that I/client wants to use. This lets me poll the existing resource information (e.g. introtext for the caption) but gives me lots of other advantages too. I can have as many as I want, obviously, but even better I can set publish/unpublish dates for each of these resources too.... so for example, a client can set up a slide show to automatically publish a new "first" image on Christmas Day, without ever having to leave their kids or the celebration, etc.

The multi-items stuff is nice for keeping everything tied to one resource, but I don’t think it touches the flexibility of the many static resources option.