<iframe not accepted in prefix/suffix variable

rottenberg
Topic Author
Offline
Platinum Member

11 years 2 months ago #39624 by rottenberg

<iframe not accepted in prefix/suffix variable was created by rottenberg

Hello

I have added a field to run YOutube player list. FOr Html5 compatibility the parameter is an iframe.

When I write <iframe in the prefix/suffix I get <i-frame
So it doesn't work.

I have temporally solved the problem using 'Nonumber sourcerer plugin' in the prefix/suffix value.

I write {source 0}iframe..../iframe{/source}

With that I don't have anymore problem. But is there another solution to accept iframe in the field

best regards

Michel

Please Log in or Create an account to join the conversation.

suge1w
Offline
Junior Member

11 years 2 months ago #39631 by suge1w

Replied by suge1w on topic <iframe not accepted in prefix/suffix variable

One workaround I can think of with the Modules Anywhere plugin is create a wrapper module, in prefix value of your field load that module and go from there?

Not a solution to your question but just another bypass.

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

11 years 2 months ago #39633 by ggppdk

Replied by ggppdk on topic <iframe not accepted in prefix/suffix variable

Hello

you can place your HTML code in a custom template and triggering content plugins inside the template file (e.g. item.php) :

Triggering Contents Plugins to create a customized layout of your fields

-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

rottenberg
Topic Author
Offline
Platinum Member

11 years 2 months ago #39639 by rottenberg

Replied by rottenberg on topic <iframe not accepted in prefix/suffix variable

thank you,

I prefer my present method (using sourcerer plugin), if it doesn't bring problems as I prefer avoiding multiply the number of templates and as FC allow it using the prefix/suffix parameters of the fields

presently I have put in the prefix :

Code:

{source 0}[[iframe width="100%" height="270" src="//www.youtube-nocookie.com/embed/{{yt_list_video##0}}?list={{yt_list##0}}&autoplay=1&rel=0&modestbranding=1" frameborder="0" allowfullscreen]][[/iframe]]{/source}

Can you confirm me that is not a problem for FC (for the moment it's working great).

best regards
Michel

Please Log in or Create an account to join the conversation.