This topic has 9 replies, 3 voices, and was last updated 7 years, 10 months ago ago by Eva Kemp
In a recently closed thread, 8Theme support said, “You can write HTML syntax in the category description. It will work, but by default we don’t have html editor there as wordpress editor for posts/pages.”
That’s fine. We’re better at HTML encoding than the client; however, I’m having trouble with this particular item in practice.
I want to format the “Description” field on the “Edit Product Category” page of the admin. I am attempting to use H2, OL, LI, and B tags. So far, the only tags that are preserved are bold (<b></b>) and your [etheme_list] shortcodes. When I save, all of the other intended formatting is gone.
Are there other shortcodes, or do I need to escape the HTML in some fashion to achieve basic intended presentation?
Hello,
Please provide us with FTP and WP Dashboard credentials in Private Content.
Regards,
Eva Kemp.
Thanks, Eva. This is very high priority for us. See below.
It’s easy to test. Just put <h2>MyHeading</h2>, etc., in any category description and save. No need to load the front end.
My apologies: I realized I forgot to give you the wp-admin/ logon address. Below.
It’s early for me. =D
Hello,
I’ve added this code in child functions.php file:
foreach ( array( 'pre_term_description' ) as $filter ) {
remove_filter( $filter, 'wp_filter_kses' );
}
foreach ( array( 'term_description' ) as $filter ) {
remove_filter( $filter, 'wp_kses_data' );
}
Please try to add HTML tags now.
Regards,
Eva Kemp.
That seemed to do the trick. It saves and formats as expected now. Thanks very much.
This question may be unrelated, but do you know if there is an etheme shortcode for an ordered (numbered) list?
Hello,
Sorry, but we have shortcode only for unordered list – [etheme_list style="circle"]
.
Best regards,
Jack Richardson.
Thanks again. That’s fine. CSS works just as well.
Hello,
You’re welcome.
Regards,
Eva Kemp.
The issue related to '‘(Most) HTML Formatting Stripped from Product Category Description’' has been successfully resolved, and the topic is now closed for further responses