I wonder if it is possible to suppress eXist-db betterForms CSS.
I have googled for it, and the solution I have found here was to add the CSS class no-bf-css to the body element the HTML page, but it doesn't seem to work.
To disable betterFORM in eXist:
Comment out or delete all betterFORM's servlets, filters and mapping in
$EXIST_HOME/webapp/WEB_INF/web.xml
Comment out or delete betterFORM's resource-servlet in
$EXIST_HOME/webapp/WEB_INF/controller-config.xml
(Adapted from Evgeny Gazdovsky's post to exist-open on May 4, 2013, archived at http://markmail.org/message/2mbnfzzmhqepc5zz.)
Related
Simple blog in Django (1.11.7 - Python3) in which I have impemented the Markdownx plugin. The plugin works for most of the markdown in preview in my 'edit_article' page, and in the normal view where users can read an article. BUT some of the markup isn't working in either:
Not working:
blockquotes using >
headers using one or more # or _
double-space and carriage return doesn't add a line-break
Links, images, numbered lists, emphasis and bold etc all work.
I posted my markdown in here, but of course it all worked here...
Don't really have any code to post, because most things work, so I'm guessing there isn't any problem with my model/view etc.
Anyone experienced this?
# So, let's try a header
doesn't work, neither does
> this type of blockquote
but they shoud produce
So, lets try a header
and
this type of blockquote
So I found the answer to this myself. I am using a CSS framework that resets the styling on the 'broken' markup tags. Until I add back the framework's CSS classes to the H1-H6 tags for example, the reset makes all headers appear as plain text.
So I have to add some custom CSS to the css framework's styling for those tags that are being overridden, or use html in the textarea in the form which should also work.
I have an ApplicationEventHandler in Umbraco to catch publish events. We want to get the rendered html for some of our PublishedEntities and store them elsewhere ...
What's the easiest way to achieve this?
kind regards
Y.
Just for reference ... Mark's answer is working but it downloads the full html.
Shorter would be to use
UmbracoHelper(UmbracoContext.Current).RenderTemplate(node.id)
We are having a problem with CKEditor (ver 4.1.1.5) stripping out some of our css classes when we are editing in the FULL HTML mode using SOURCE. From looking at some of the other questions posed on this, the Advanced Content Filter is the place we should be going. And, if I read this correctly, we need to edit the config.js file to add: CKEDITOR.config.allowedContent=true;
Am I going in the right direction? I want the WYSIWYG to still work for people with no html experience. However, when we go into source, I want all classes to remain and not be stripped out, no matter what.
You are partially right:
Yes, Advanced Content Filter (ACF) is the mechanism responsible for this.
But no, setting config.allowedContent to true is not a correct solution.
In short, ACF is a useful mechanism that lets you easily control the content that your users add to your site with CKEditor. Instead of disabling it, however, you should extend the filter configuration to accept whatever additional elements, classes, styles, attributes you want to allow.
In your case, if you want to additionally allow all classes for all elements, use this in your editor configuration:
config.extraAllowedContent = '*(*)';
Read more about ACF here:
Content Filtering (ACF) - introduction
Demo of Automatic Mode and Custom Mode
Advanced Content Filter - more advanced
Allowed Content Rules - syntax for ACF rules
Does anyone know if there's some way to stop Magento "fixing" html that's added via static blocks?
For example, if I wanted to have a space within an existing menu for adding static blocks to, I wouldn't want to use a full < ul > list as it already exists, so I'd just want some additional < li > tags within the block.
However, Magento very helpfully decides to always add in the "missing" < ul > tags for you. Rather annoying.
I've tried tracing this back myself but just can't find where it's happening. I think it could be TinyMce related, as the fixing happens if you hide/show the editor, without a page refresh. I tried changing different instances I found of cleanup:1 to cleanup:0 but none of them so far worked.
Any ideas?
It's not magento that is doing this cleanup but the wysiwyg editor : tiny_mce
You can desactivate this behavior by adding :
cleanup : false
in the js config file (js/mage/adminhtml/wysiwyg/tiny_mce/setup.js)
But this is totally not recommended as it can break all of your pages is an HTML bug is injected in a block or page and you don't have any other HTML tidier on your project ...
Have a look at the tinymce configuration parameter valid_elements and valid_children.
You can define li-tags as valid elements there and define that li-tags may be childs to other thml nodes.
You can also add
valid_elements: '*[*]',
to js/mage/adminhtml/wysiwyg/tiny_mce/setup.js to allow everything.
In TinyMCE, I need to add a in-line style attribute on link creation. The reason is that Google Mail doesn't support tags in a newsletter.
One solution can be "advlink". But who would explain to our user...that he must add css code in a new link...bad solution.
There must be a simpler, user-friendly way, but i can't find it. Is there an option that i can tell the plugin to add automatic style-attributes to a link?
//EDIT
Ok, i think another solution can be, if i can add anchor to 'style_formats'. But an anchor is not supported in 'style_formats'...someone has an idea?
You may write an own plugin which adds the inline style element to links.
An easier approch is to put the necessary code into the setup config paramter.