This is a test version of Biostars. For the public version, visit https://www.biostars.org.
Forum: Missing content in old posts?

Hello all,

So I have been searching for some information on Chip-seq data analysis. As a result found a 4 year old post in which the content is missing. Here it is Forum: Chip-Seq Data Analysis.

Am I confused with something or is there any problem with that old thread? I can solve my problem with other useful threads or from other sources. But I thought it is useful to bring this up to avoid similar cases in future.

Thank you

meta

1 answer

Eek - it's a bug introduced due to the new markdown syntax - Biostars probably no longer supports html iframe tags (probably a good thing..) and so the content of that post, which was just three youtube videos each in an iframe, isn't visible.

Here are the videos by the way:

http://www.youtube.com/embed/9l5avbFLlxw

http://www.youtube.com/embed/pwslWrzHiXQ

http://www.youtube.com/embed/Ly5LO9ynuOY

I also can't edit the post to have the new syntax because I get this error:

This post is not editable because of an iframe! Contact if you must edit it

Thats when deleting the iframes, so this is probably a minor bug. Teething troubles like this are to be expected when changing the formatting of a site, but hopefully this will be a quick fix :)

If Istvan or another BioStars dev can fix the above error, i'll be happy to go through all the posts with iframes and convert them to regular links.

Whilst we're on the topic of minor formatting bugs:

comments

dont

support

all

<h5>heading</h5> <h6>sizes</h6>

This is just an eager html cleanser where only a subset of HTML tags are allowed through. Not sure if should be classified as a bug or a feature ...

Firs of all thank you for providing the links from that post. And it would be useful for other users as well if these kind of posts were edited to normal.

I missed this post originally, the answer is as you suspect with the insertion of iframes to embed content.

Since we switched back and forth between Markdown -> HTML -> CommonMark there is a type of content that is not supported in the new version anymore.

The question was wether it is worth writing code to do this automatically or whether it is best to fix these manually for the few cases that occur. I went with this second option and today I try to fix these bypassing the main editor.

Log in to answer this question.