Migrating from Revolution Slider to ThemeCo's Sliders

[dhunink]

Hi,

I’ve been doing some really nice stuff with the Modern Sliders since it’s released, and I’m now looking to get rid of the last remaining sliders that have previously been build with Revolution Sliders.
I can think of an approach to create ‘galleries’ that can act as Looper Provider: create a separate Custom Posttype ‘galleries’, and add an ACF-field ‘gallery’ to that CPT. Then in Looper Provider select the exact PostID for the CPT-item that holds the ACF Gallery to be used.

But this feels already way too complicated. So I’m wondering what the idea was when Modern Sliders was designed. Let’s keep it simple and say: “The user needs to select and manage (as their updated every now and then) a set of images, and that selection would be displayed using a ThemeCo Modern Slider”.

I’m very curious!

In addition: I know there have been a few remarks over the years regarding ‘lightboxes’. Might this be something to bump up the roadmap? Given the elements that are available right now, it would mean just a small step to enable a Lightbox on image/sliders, which would eliminate even more external plugins.

[ruenel]

Hey @dhunink,

Thanks for posting in!

Have you checked out this Youtube video where it uses the Slider and the Modal element?
https://www.youtube.com/watch?v=ASv_W7z74C4

You might also be interested in this video about how you can trigger the slides in the slider:
https://www.youtube.com/watch?v=do45n9xMUVo

Happy Holidays.

[dhunink]

Hi @ruenel,

These are definitely interesting. Basically they describe kind of the way I have chosen to go right now: an ACF Field for a CPT. I’ve done that before, a few times. What’s different in my current situation is that I don’t want to show a gallery field that’s attached to the current page, but a gallery field that’s linked to another CPT.

Let’s set the ‘modal’ part aside for now; that’s just a feature request.
The more important part of my question is ‘how to create sets of images, often called albums or galleries, to be used on multiple posts/pages, using Modern Sliders’?

Let me illustrate this user case.

Structure:

• Default PT ‘page’
• CPT: Gallery
  • ACF Field: Gallery

In this case:

• Default page ‘accomodation’
  • Child-page ‘apartment’
• Three CPT-items ‘Gallery’, each with a ACF Gallery field

On both the ‘accomodation’ as the ‘apartment’ page I want to show one, two or all three of the Galleries.

This is the ACF-field:

This is an example of a CPT-item with it’s ACF Gallery Field populated:

The ID of this CPT-item is 30253.

So that’s what I used as looper provider: the Gallery field of that specific post ( {{dc:acf:post_field field="gallery" post="30253"}} ):

Then als Looper Consumer, it’s just the current item

Unfortunately, nothing will show up.
So I’m missing something here, and I can’t figure out what. That leads me to a few questions:

• based on all above, what am I missing here?
• is there an easy way to see the output of looper providers in the Console Log or any other place? I’d like to debug issues like this myself
• there are plugins like FooGallery and RevolutionSlider that let you create sets of images, called albums or galeries, and let you use these on multiple pages/posts. Is there a more intuitive method for Pro, then creating CPT with ACF and manually selecting these in the looper provider/consumer?

I’m looking forward to your in-depth answers on all three matters!

[ruenel]

Hey @dhunink,

It has to return something for the looper to consume. You can use {{dc:looper:debug_consumer}} to see if the loop has something to return or it is NULL. We would love to check your layout. Please provide us with your WP details in the secure note below.

At the moment, you can either manually add the images to the slides or use Loopers to load the images into the slides. Regretfully we do not have another feature that allows you create galleries automatically.

Cheers.

[dhunink]

Hi @ruenel,

I’ve added a secure note with credentials. I’m really curious which mistake I made in this case.
Thanks for providing the debug option, that sure is going to help me in the future.
Suggestion: refer to this option in the documentation. That might help several customers!

Could we add to the feature-request list:

• in the image-element, add a native ‘enable/disable’ Lightbox option
• create galleries to be selected as Looper Provider

[ruenel]

Hello @dhunink,

Your feature request was added.

By the way, I checked your single layout, and it seems it is displaying the ACF gallery for that activity item.

Cheer.

[dhunink]

Hi @ruenel,

I’m sorry, I should have been more specific.
I’ve shared a secure note with a direct link to the page concerned.
The issues relates to the following element (which is hidden by default, but should be set so visible to debug):

I tried using the {{dc:looper:debug_consumer}} but that outputs something unexpected:

[ruenel]

Hey @dhunink,

Be advised that you cannot use {{dc:acf:post_field field="gallery" post="30253"}} because this will only apply if you are referring to a post item. Since you are trying to retrieve the gallery of a specific custom post type, you will need to nest a loop that returns the custom post item first, and then you can access the gallery. The structure would be like this:

Looper Provider Query String `post_type="fotoalbum"&id="30253"` / Looper Consumer
    Looper Provide Dynamic Content `{{dc:acf:post_field field="gallery"}}`
        Looper Consumer
             Image `{{ looper.item.url }}`
             Text

You will have to use {{ looper.item.url }} since the loop returns an Image array.

Check out the demo on the page now.

[dhunink]

Hi @ruenel,

Thanks for both explaining and realising this, that does indeed work.
I did notice that the prev/next buttons don’t work. They direct to #verblijf, which is kind of surprising, as they they have #next/#prev as attributes. I’m going to dive into hat, but if you do do spot something in a quick look, that would be much appreciated!

I do think my original post is even more relevant now. The current implementation is complex. A certain share of users, including myself, do understand the structure of LP/LC. But new customers might have a hard time.
Pro has all the code present to go to the next level: default Gallery-element/post-type. Kind of how Portfolio is included as well.
I noticed in recent two/three years development has mainly be focussed on on doing technical great stuff, making the theme more capable and more efficient. But at the same time I’m starting to miss development on less technical interesting stuff. Think things like this, a simple to use gallery interface, but also missing a simple addition of adding light boxes to native elements.
The code is there. Technically it can be done already. But it requires configuration, instead of just enabling settings in an element.

This is in no way feedback to you personally. Im very grateful for your help! But I do wanted to share my reflection, hoping you can share that with the team and discuss it internally. In the end hoping to welcome even more and more fellow customers, and keep your business going!

[ruenel]

Hey @dhunink,

It appears that a link “#” would react and scroll down to the form below. The form script could be causing the issue. Disabling the link in the Next/Prev buttons should resolve the issue.

In my opinion, what you are looking for is not a Slider element feature. It would be a completely new slider post type that you can easily manage and create sliders with, which would then be directly integrated into the builder. I will ask around and chat with our developers about this one.

Cheers.