Menno Luitjes

Hey,

Thanks for reporting this issue. For me the video slides work fine, so please send as much information as you can. Hopefully I can find what is wrong.

Could you at least send me the link to your display that shows this slideshow, and your browser including its version, and your operating system including its version?

Menno

Hi there!

Interesting idea. Unfortunately the visitors management is a bit out of scope for my plugin.

But if you could make that page yourself (eg. a WordPress page where you type in the names manually), or use some kind of hosted service to build a page that displays current visitors like you want, .. there is now an easy was to add that page to your Foyer slideshows.

Foyer version 1.3 introduces the External web page slide format. It displays a web page to your liking. This can be any kind of page, as long as it has its own URL.

Would that work for you?

Also, I build WordPress back-ends, so let me know if you are interested in a custom made visitors management back-end for you website with front-end list that could be included in Foyer slideshows.

Menno

Hi Matt,

I’m adding different slide formats at the moment. A ‘post’ slide format is on my list. It would display an image with the title and summary next to it.

With that you could create a slide with one news item, a slide with one event, with any kind of custom post actually.

Is that what you are looking for? Or are you thinking of one slide with a list of upcoming events, and one slide with a list of the latest news items? If you could send me a quick sketch that would be great.

Thanks for the feedback.

Menno

Hi again.

Just wanted to let you know that I was able to avoid/fix this behaviour by moving the Google Tag Manager script to just below the opening body tag. From somewhere near the closing body tag, where the DuracellTomi’s Google Tag Manager plugin inserts it by default.

Now my Google Tag Manager is correctly blocked, and enabled.

Best,
Menno

Hi Gerrit,

I’m not the plugin author, but about the plugin breaking your HTML:

I found that the plugin parses the HTML of each page (using libxml). If your HTML has any unclosed elements (normally accepted by web browsers without problems), this will result in some of the HTML being reformatted or removed to make it valid XML.

You might want to check if your HTML is valid.

Menno