Comments for page "21 - Iframe Module"

Re: About Iframe attributes

Sun, 18 Apr 2010 00:33:57 +0000

James is right. I don't see the point of trying to embed this site inside an iframe when a simple link will do the trick.

-Ed.

Re: About Iframe attributes

Sun, 18 Apr 2010 00:30:45 +0000

I see your problem… it can't be fixed with iframes. You are best to provide a link to the website itself, but open it in a new window so that the user doesn't leave your website.

Use this code on your website to open it up in a new window when they click “Choose what is relevant for you”:

++++ Here you will get wedding speeches of all types like: Best Man Speech, Maid of Honor Speech, Father of the Bride Speech etc.... [*http://www.weddingspeechesforall.com/ Choose what is relevant for you].

About Iframe attributes

Sun, 18 Apr 2010 00:09:03 +0000

The problem I am facing is that after embeding another page with an Iframe in wikidot, when I click a link in that page the next upcoming page will be out of range and you have to drag it to see its content simply because the height pixel of the first page and second page is different. Is there a way that we can tell (with a code) Wikidot to take all attributes of all pages within that url to take from the url itself and not from the attributes I fill in the Iframe? Is there any such snippet?
If you did not understand me just check http://relationships.wikidot.com/wedding-speeches
When a customer tries to buy, the payment page will be out of range and I have to drag the page to see it. Here the problem is that I can probably miss the customer.
Any snippet please. THX.

I see that this Iframe module design is closed ...

Sun, 18 Oct 2009 11:10:54 +0000

Was it implemented ?

EDIT: oups, did not see //I'm closing this issue in favour of http://blog.wikidot.com/design:24//

(no title)

Tue, 13 Oct 2009 12:32:30 +0000

I'm closing this issue in favour of http://blog.wikidot.com/design:24.

Re:

Sat, 03 Oct 2009 12:55:03 +0000

I've lost count of the number of times I've said "you can do this with a codeblock/iframe combination" and then demonstrated it. So a module for this is a very good idea.

Rob

Re: Embed vs. Iframe

Sat, 03 Oct 2009 09:47:25 +0000

Oh, I've been doing that because I thought that commenting out code blocks would mean the code block isn't rendered in wdfiles.com.

Ya learn something new every day :D

Re: This page has zero comments?

Sat, 03 Oct 2009 07:56:21 +0000

That's the ListPages cache, I think.

Re: Embed vs. Iframe

Sat, 03 Oct 2009 07:48:34 +0000

James I notice you always do a div style="display:none;" then later the closing /div. Is there any reason you do this? It's quicker to type [!--..code..--] comment tags to wrap the code in which is how I always do it.

Rob

Re: This page has zero comments?

Sat, 03 Oct 2009 06:43:29 +0000

You need to edit—save for it to refresh the number of comments. It's annoying =/

Re: Embbed instead of iframe

Sat, 03 Oct 2009 06:39:15 +0000

I always thought - the reason to do the store of self written ode on wdfiles is a security factor?

Means - embedding a "prooven" code from a "trusted" site we can embbed ( after some seecurity checks..)

embbedding from an unchecked wikidot.page ( not third party wdfiles) would be dangerous ?

Re: pieterh

Sat, 03 Oct 2009 06:23:04 +0000

Agreed.

Re: Embed vs. Iframe

Sat, 03 Oct 2009 04:12:43 +0000

Here is the code for an embedded YouTube Video:

[[=]] [[embed]]  [[/embed]] [[/=]]

Which renders this HTML on the Wikidot page:

<div style="text-align: center;"> <p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/jwbex2eZ98o&hl=en&fs=1&rel=0" /> <param name="allowFullScreen" value="true" /> <param name="allowscriptaccess" value="always" /> <embed src="http://www.youtube.com/v/jwbex2eZ98o&hl=en&fs=1&rel=0" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344" />object>p> div>

Now, instead of embedding the YouTube embed code, we can place it in a hidden code block, and iframe the code block.

Here is the code for iframing a YouTube Video:

[[=]] [[iframe http://blog.wdfiles.com/local--code/design:21 width="435px" height="355px" scrolling="no" frameborder="0"]] [[/=]]

Which renders this HTML on the Wikidot page:

<div style="text-align: center;"> <p><iframe src="http://blog.wdfiles.com/local--code/design:21" align="" frameborder="0" height="355px" scrolling="no" width="435px" class="" style="">iframe>p> div>

This section of this comment did display an iframed version of the same code above. It rendered the YouTube video completely identical to the one above.

Unfortunately, we can't demonstrate this anymore because Pieter removed the [[code]] block from this page.

As you can see, the visual output is similar (well, it's identical in this case), but the coding is different.

Re: Embed vs. Iframe

Sat, 03 Oct 2009 03:18:40 +0000

Oh, I see. Embed puts code on wikidot page, and iframe puts other code of a page on screen.

In that case, this would be highly useful.

This page has zero comments?

Sat, 03 Oct 2009 01:59:27 +0000

Huh? This page has zero comments?

Re: Embed vs. Iframe

Sat, 03 Oct 2009 01:34:47 +0000

The difference between embedding and iframing is quite significant.

Embedding actually injects the code directly into the webpage. Therefore, the embedded code is coming from the domain of the webpage it's embedded in.

Does that make sense?

Embedding poses a risk of code taking over Wikidot, whether iframing does not (the iframed code comes from a different domain).

Embed vs. Iframe

Sat, 03 Oct 2009 01:22:44 +0000

Is this like an embed, or is there a significant difference between the two?

(no title)

Fri, 02 Oct 2009 21:00:33 +0000

Excellent proposal, James. It is true that we see this request over and over and this would save everyone a lot of time.