Hi, I have followed every step... and now I am getting this under any "embed" video, top one, or popup:
-------------------------------------------------------------------------------------
data=”http://vimeo.com/moogaloop.swf?clip_id=15382912&fullscreen=1&autoplay=0&color=FFFFFF”
type=”application/x-shockwave-flash”>
-------------------------------------------------------------------------------------
THIS IS HAPPENING UNDER FIREFOX. NOT SAFARI OR CHROME FOR EXAMPLE.
Sample page:
http://fazendodiscip...us/?page_id=814
Help please!
Problem after fixing the Vimeo problem
Started by Roberto Verli Fernandes, Nov 09 2010 11:38 AM
4 replies to this topic
#1
Posted 09 November 2010 - 11:38 AM
#2
Posted 12 November 2010 - 03:35 PM
Looks like your Vimeo template got corrupted somehow - probably accidentally while you were fixing the Vimeo key problem.
I would suggest, and I know this is a bit of a pain, removing your entire wp-content/plugins/tubepress directory. Then install a fresh copy, and finally insert your Vimeo keys as described here: http://tubepress.com...ix...ts-broken/
Give that a whirl and let us know if it fixes your issue. Thanks!
I would suggest, and I know this is a bit of a pain, removing your entire wp-content/plugins/tubepress directory. Then install a fresh copy, and finally insert your Vimeo keys as described here: http://tubepress.com...ix...ts-broken/
Give that a whirl and let us know if it fixes your issue. Thanks!
#3
Posted 12 November 2010 - 04:02 PM
Just did it...
Even bought your "PRO" version... keeps doing the same thing...
Even bought your "PRO" version... keeps doing the same thing...
#4
Posted 12 November 2010 - 04:34 PM
It appears that something is inserting extra "
" tags into the Vimeo object's HTML: http://i.imgur.com/6f6I9.png. Chrome and Safari are OK with ignore the breaks, but Firefox clearly chooses not to render it.
If you have a fresh install of TubePress, the only explanation is that something else is inserting those line breaks. My guess is that it's your theme and/or another plugin that is trying to convert ASCII line breaks (\n) into HTML
tags.
Here's what I would do, roughly in order of easiness
I'm sure that one of these methods will either fix or identify the issue. Keep us posted. Thanks.
" tags into the Vimeo object's HTML: http://i.imgur.com/6f6I9.png. Chrome and Safari are OK with ignore the breaks, but Firefox clearly chooses not to render it.
If you have a fresh install of TubePress, the only explanation is that something else is inserting those line breaks. My guess is that it's your theme and/or another plugin that is trying to convert ASCII line breaks (\n) into HTML
tags.
Here's what I would do, roughly in order of easiness
- Edit ui/embedded_flash/vimeo/html_templates/object.tpl.php and get rid of all the line breaks in that file. e.g. instead of
<object style="width: <span class="syntaxdefault"><?php echo ${org_tubepress_template_Template::EMBEDDED_WIDTH}; ?>px; height:<?php echo ${org_tubepress_template_Template::EMBEDDED_HEIGHT}; ?>px" data="<?php echo ${org_tubepress_template_Template::EMBEDDED_DATA_URL}; ?>" type="application/x-shockwave-flash"> <param name="allowfullscreen" value="<?php echo ${org_tubepress_template_Template::EMBEDDED_FULLSCREEN}; ?>" /> <param name="allowscriptaccess" value="always" /> <param name="movie" value="<?php echo ${org_tubepress_template_Template::EMBEDDED_DATA_URL}; ?>" /></object></span>
you want it to look like this:
<object style="width: <span class="syntaxdefault"><?php echo ${org_tubepress_template_Template::EMBEDDED_WIDTH}; ?>px; height:<?php echo ${org_tubepress_template_Template::EMBEDDED_HEIGHT}; ?>px" data="<?php echo ${org_tubepress_template_Template::EMBEDDED_DATA_URL}; ?>" type="application/x-shockwave-flash"><param name="allowfullscreen" value="<?php echo ${org_tubepress_template_Template::EMBEDDED_FULLSCREEN}; ?>" /><param name="allowscriptaccess" value="always" /><param name="movie" value="<?php echo ${org_tubepress_template_Template::EMBEDDED_DATA_URL}; ?>" /></object></span>
Notice I removed all the line breaks - Try another theme to see if the problem persists. If not, we've narrowed it down to your theme.
- Disable your other WordPress plugins one by one until the problem goes away.
I'm sure that one of these methods will either fix or identify the issue. Keep us posted. Thanks.
#5
Posted 12 November 2010 - 05:51 PM
It worked!
Thanks man!
Thanks man!