Control MediaWiki generated html - mediawiki

I would like to control the html generated by the application. In other words: When an user saves an article the html article generated would have some aditional html tags. For example the first section of the article would be within a div, with a specific ID. BUt this shouldn't change the text when editing the article, only the "article view" panel would have that div. Was I clear enough?
Is there any extension that can help me?
If no, should I develop my own extension? If so can you give some advises about the flow? I never develop an extension, and any highlights and insights you can give would probably save lots of research time.
Thanks in advance

The article already has its own individual div when created. It is how the div#header, MediaWiki:(anon|site)notice, MediaWiki:Sidebar, and the div#content are separated.. I would first suggest try using your browser's View Source feature on a few parsed pages to see what the output looks like. div#content can be used in your skins or css to make adjustments to it accordingly.. I hope this helps, or prompts you for move information appropriately. :D

Related

How can I use a file or text with footer-html? I'm using wkhtmltopdf

I'm using wkhtmltopdf to convert an html template into a pdf, and I want to use some html as a footer, but as far as I can tell I have to make the html a webpage, which means it would be visible to the public. So I have two questions:
Is there any way to use a string or a file with footer-html?
If not, is there any way to prevent the footer webpage from being visible to the public? I'm using flask to make my website.
Why do you not want anyone to see the footer tag?
A <footer> element typically contains:
authorship information
copyright information
contact information
sitemap
back to top links
related documents
Also, no one can see your html unless you publish it.
If this does not answer your question, consider to edit it with a more clear question.
If you really want to hide it you can go to the link below ^^
W3schools Example

Simple blog in CSS and HTML only

I have a simple html/css-only static website on which I would like to add a blog. Comments and RSS aren't necessary.
Now, how do I do that, without having to write all my entries in pure html?
My website consists of a vertical menu and an area to the right of it, where all the content goes on each page. I would like a blog inside that area on the blog page, so a blog on a separate page with its own layout is not what I'm looking for.
Googling this doesn't really help me much since the majority of the hits are on sites offering blog services.
Thanks in advance, I hope I'm not being too difficult. Please leave some feedback on my question if you think there are things I should have tried out before asking.
If i understand what you want the answer is that ist is not possible in pure html and css. With only Html and css you can not make a blog (if you dont want to edit the source everytime you write an entry and have to make a new file for each entry and so on).
You need some code (php or so) that is able to store and load the entrys into your site.
Html and css are not meant to make things working. With Html you define the elements so that they are structed and then with css you "style" your work. But for the task of a blog (i think you want an editor for the text on the site, the ability to edit, delete, more than one site and so on) you need something like php or aps.net that is able to "interact".

HTML WYSIWYG edtor: why is the editable content moved in an iFrame

Why is the editable html moved into an iFrame? I analysed different editors (TinyMce, CKEditor, etc) and all move the editable content into a separate iFrame which they lay over the original text.
What is the technical reason for this. I experimented with the contenteditable="true", which is the base of all this editors too, and didn't find a reason yet to do this.
I'm CKEditor core developer. Not for a long time - just for last half of the year, but I've learnt a lot about why we use iframed editable :)
Styling - content of the iframed editor doesn't inherit styles of the page. This is extremely important, because we cannot reset styles (sic! CSS really sucks). What's more - in iframe we can freely add our own styles which is helpful too.
Only in iframed editable we can work on entire page with head, metas, body styles, title, etc. Some of our users need this.
Browsers have very buggy (and incomplete) impls of contenteditable. E.g. guess what will happen when you paste list into the editable which is a <h1> element on Firefox (you can check that in this editor - http://createjs.org/demo/hallo/)? It will leak out of editable area and become a non-editable element. We have to handle these cases manually in the editor and this is really hard work :).
I'm not sure about this but I believe that designMode wich allows to switch entire document into the editable area had been first and contenteditable came later. So the reason may be historical too - it's hard to switch from one approach to another.
Probably there're more reasons why we use an iframed editable. I'll update my answer when I'll learn them :)
From the tinymce froum
Hi Zappino!
It is the very nature of editors like TinyMCE to use an IFrame because
in a frame you can modify any part of an HTML document to suit your
needs without breaking anything in the main page's document.
Especially if you want to edit a complete HTML document including the
parts between and you won't be able to do so without an
IFrame.
Cross Domain Skripting will occur if you store TinyMCE's files on a
different (sub-)domain than the page from which you embed the editor.
Show us a test scenario of your installation with which you are having
trouble and someone might be able to help you out!
Greetings from Germany (back to Germany )
Felix Riesterer.

WYSIWYG editor override page css?

I have a web application that allows the creation of HTML emails that can then be dispatched. Because of how fiddly HTML email display can be, I have an open-source WYSIWYG editor embedded.
The editor itself works fantastically, but with one problem that you may already be thinking. Basically, the page CSS is conflicting with the inline CSS generated by the text editor, which caused issues for things like tables.
Currently I am solving this on the "preview" page by placing the preview in an iframe but I am not entirely sure the best way to do this for the actual editor page. If I do it in an iframe, I would either have to put it into a separate page and alter the process slightly, or write some Javascript to strip the HTML out of the iframe on form submit.
It seems like there should be an easier way - has anyone solved this problem before?
Thanks.
I would switch to a different editor like CKEditor or TinyMCE that allows you to edit the whole HTML by using themselves an iframe for the edited contents. That way you can edit exactly what you will send.
One example: http://nightly.ckeditor.com/latest/ckeditor/_samples/fullpage.html
Change how you are targeting your selectors. If you have conflicts, then your CSS is not written efficiently.
Maybe use a root div with a specific ID and have everything cascade off of that.

FCKEditor breaking HTML forms

I'm in the process of reproducing some standalone HTML forms as pages in a CMS that uses FCKEditor by simply copying and pasting the relevant code into the editor.
But when I save and view the page, the HTML has been changed and the tag has been moved up to just below the open tag -- and not at the bottom of the form. This obviously renders all of the fields in the form, including the submit button, useless.
Is there a way to tell FCKEditor that I know what I'm doing and I don't need it to validate the HTML output?
Unfortunately this is a hosted CMS service (actually part of an email blast tool) so making changes to the configuration will mean I need to go through the company's support system, which is fine -- but they haven't been able to solve it for me yet, so I'm hoping to get the answers for them.
Thanks!
This is a bit of a difficult thing because as far as I know, it's not necessarily the WYSIWYG editors that "fix" "broken" HTML, it's the browsers' HTML editing engines themselves, and it's often near impossible to talk them out of doing this.
You'd have to show your exact source to get detailed feedback, but check out whether protectedSource is something for you. It's supposed to protect code that is covered by the regular expression you specify.
I'm not sure about FCKEditor, but you might want to consider switching to TinyMCE. TinyMCE allows you to both edit a list of allowed tags, and to turn off HTML validation off completely if you like.