BB Code Media - Source

ManagerJosh

Well-known member
Is there a source or some sort of rebuild/update function for BB Code Media?

I noticed some YouTube links were not working for me and after doing an HTML comparison between xenforo.com and my site, I noticed that my BBCode was not the same as the ones here. Updated a bit of HTML and now it works.
 
Do you mean the BB Code tags themselves?

You can run SQL queries to update them if necessary.
For example:
Code:
UPDATE xf_post SET message = REPLACE(message, '[vimeo]', '[media=vimeo]');

That will update any old BB Code tags from [vimeo] to [media=vimeo].
 
Do you mean the BB Code tags themselves?

You can run SQL queries to update them if necessary.

Not really Brogan, I mean the BB Code itself. Like what we edit inside the AdminCP that transposes certain URLs, Links, and their variables into HTML when we click the media tab and then hit post reply.

ie.... yourxenforoinstall.com/admin.php?bb-code-media-sites/youtube/edit
 
That code can be edited to suit.
This is mine for example:
Code:
<object width="640" height="385" data="http://www.youtube.com/v/{$id}&amp;fs=1">
 <param name="movie" value="http://www.youtube.com/v/{$id}&amp;fs=1" />
 <param name="allowFullScreen" value="true" />
 <param name="wmode" value="opaque" />
 <embed src="http://www.youtube.com/v/{$id}&amp;fs=1" type="application/x-shockwave-flash" allowfullscreen="true" wmode="opaque" width="640" height="385" />
</object>

What did you change yours from and to, to get things working properly?
 
Did you import? How were they different?

I am not aware of any caches that need rebuilding with regard to BB Code Media Sites. Changes to BB Code Media Sites are reflected immediately in existing posts.
 
There's no cache that's relevant. Chrome can be finicky about when it works and when it doesn't; refreshing can fix it for me.

Tthey simply aren't easy for us to programmatically update, so it might be something to come back to. The additional bit here (type="application/x-shockwave-flash" in the <object> tag) is just to fix a WebKit layering bug.
 
There's no cache that's relevant. Chrome can be finicky about when it works and when it doesn't; refreshing can fix it for me.

Tthey simply aren't easy for us to programmatically update, so it might be something to come back to. The additional bit here (type="application/x-shockwave-flash" in the <object> tag) is just to fix a WebKit layering bug.

Ahh.. I see. Perfect Mike thanks. I figured it was either a browser bug or some sort of bug on my end.

What Mike posted was what I added to the <object> tag.
 
Top Bottom