Rating: 5 stars

This is the file as I upload it to WordPress – note the two hypens after the <! At the front of the file (to make them invisible to HTML – the are comments now) and the correct closing italic sign </i> after the book of poetry’s title Poena Damni:

<!– FILENAME: 7578-lyacos-essay-zaller.htm / TITLE: A Column of Cloud and a Column of Fire: Dimitris Lyacos’ <i>Poena Damni</i> by Robert Zaller / EXCERPT: the text offers us a shifting series of scenes and perspectives, somewhere between a journey and a travail. § / URL: a-column-of-cloud-and-a-column-of-fire-dimitris-lyacos-poena-damni-by-robert-zaller –><link rel=”stylesheet” href=”stylesheet.css” type=”text/css” charset=”utf-8″ />
<div style=”margin-top : 1em; margin-left : 3%; margin-right : 5%;”>

This is the same file after I press the “Update” button. Gee, thanks, guys! As follows:

<!— FILENAME: 7578-lyacos-essay-zaller.htm / TITLE: A Column of Cloud and a Column of Fire: Dimitris Lyacos’ <i>Poena Damni by Robert Zaller / EXCERPT: the text offers us a shifting series of scenes and perspectives, somewhere between a journey and a travail. § / URL: a-column-of-cloud-and-a-column-of-fire-dimitris-lyacos-poena-damni-by-robert-zaller –>

Notice that the correct closing italic sign </i> is now missing (which does fun things like turning most of the file into italics). If I try and re-insert it, the Comment marker usually goes wrong, too, amounting to just an em dash following that <!— As this shows.

Can you do something about these faults, grave as they are?
That would prevent me trying out a different CMS. I like WordPress… Help me to continue to like it.

Rating: 1 star

Hallo,

unfortunately after update tinyMCE was broken. While looking for solution, I found out, TinyMCE and TinyMCE Advanced Professsional Formats and Styles was creating an JS-error:
tinymce.min.js?ver=4310-20160418:12 Uncaught TypeError: Cannot create property 'name' on string 'f'
After deaktiviation, TinyMCE works again. Would be great to get an update.

Thanks
Martin

Rating: 1 star

+ obviously it is not compatible with the “tiny mce advanced” plugin
+ In the settings I cannot delete styles
+ the editor-style-shared.css is only embeded in the frontend and has no effect in the admin area

Rating: 5 stars

Friggin’ awesome! Works beautifully.

Rating: 5 stars

Works every time! For the most part, clients have no idea what troubles they are missing because I incorporate this with every child theme I use. I always customize the CSS classes for them to access in the editor’s pull down, before I give them access to use the editor.

Rating: 5 stars

Quite easy to use.
Don’t forget to clear your browser’s cache.
Thanks to the developer.

Rating: 4 stars

This plugin requires already knowledge in css, therefore it is more targeted to advanced users. It also save time to web developpers, providing a nice GUI to create custom styles.

Rating: 5 stars

Can’t remove old styles from menu. Theme editor doesn’t answer questions.

Rating: 5 stars

Any problem to use it. I feel much more comfortable edit the files editor-style.css and editor-style-shared.css directly for building up the all the styles. Much faster than use the visual interface.
Cool plugin.

Rating: 5 stars

I wanted to be able to present styles to my clients, yet still use my child theme’s css sheet. This does exactly that!

You setup what element you want to code, and the class name, and do all the css in the child style sheet and you end up with clean code. Even if I uninstall the plugin, or it goes away for some strange reason, my code will still be intact.

Perfect & beautiful!!!!

Rating: 2 stars

Works…ish.

There seems to be too many flaws at present.

1. Using current theme path method and adding css does not reflect changes in backend or front end.

2. Custom css path not working properly. prepends final directory to css files into previous directory.

3. Using the GUI does work, but updating a style does not flow through automatically, many attempts to select text and then style seem to be required, or many refreshes of browser. It is not possible to remove style from selected text in Visual editor, you must go into text/html mode to remove tags.

Look forward to a more stable version.

Rating: 4 stars

It just needs to properly supported child themes, and it would be a 5-star plugin.

-mpm