Miriam   sagt:

am 20. Juni 2013 um 06:15 Uhr

You need to fix the links in your plug in. Currently the plugin link goes to http://www.blackbam.at/blog/ and gives a permission error. Cheers Miriam

Blackbam     sagt:

am 20. Juni 2013 um 10:21 Uhr

Hello, thanks a lot you for showing this. I will repair it before the next release.

Andre Klein Kranenbarg     sagt:

am 07. Juli 2013 um 19:39 Uhr

Hi David,
I am trying your plugin at the moment, but I have the same remarks as Miriam, the plugin link gives an error (minor issue) and when I want to go to the settings of the plugin I get an permission error. How to continue? Any idea when you have time to have a look at it?

Kind regards,
Andre

Blackbam     sagt:

am 08. Juli 2013 um 14:56 Uhr

Hello Andre

the link to the Plugin page is broken, I will fix this very soon, its just a little bug.

If you want to change the settings of the Plugin, go to "Settings -> TinyMCE prof. Styles" in your WordPress Backend.

If you do not see this page or if you cannot access it, make sure you are logged in with the role "Administrator" into WordPress (the "manage_options" capability is needed).

Does this help you?

Stu Ducklow     sagt:

am 29. Oktober 2013 um 01:09 Uhr

I like the idea behind your plug-in but half the time it doesn't work and it's very badly explained. If you would tke the trouble to write a complete explanation on how it works I'd donate because it's useful. But otherwise, it's just frustrating. I have to go by trial and error to see what results I'll get as most of the options are not explained and don't make any sense. This is typical of code junkies who don't seem to realize thst other people have lives other than coding and don't really care. They just want a product that can be used with a minimum of hassle. If you don't believe me, look at Apple.

Blackbam     sagt:

am 05. November 2013 um 21:09 Uhr

Hello Stu, can understand your point very well, the problem is that coders usually have to do a lot of work and free WordPress Plugins are kind of donation by the developers because you will not earn a lot of money with these. I mean Apple has the time and ressources, because they have a lot of employees but quite a tiny amount of products, so they can invest a lot of time to make these perfect.

There are three reasons, why the Plugin is that complicated:

1. The structure of how to create styles is bound to the TinyMCE - API, which is a bit crappy
2. The user has to understand CSS - if you understand CSS and know what properties you have to use, you will find most of your aims quite easy to achieve
3. This Plugin was initially intended to be used by other developers selling "perfect" WordPress sites to there customers (which will never touch the code of the Plugin page) and these developers know how to use it

However I WILL take the time to write a better explanation of how to use the Plugin and create a simpler workflow, because I want the WordPress users to like it and find it useful, even if they are not that strong into CSS.

Lucy     sagt:

am 03. März 2014 um 05:34 Uhr

My new class is not recognized - I have added the definition into the editor-style.css file and have created it as a new selector on the TinyMCE Advanced Professional Styles page. The style works when defined as inline with the style and value on the TinyMCE Advanced Professional Styles page, but when I change it to selector, nothing happens.... Am I supposed to declare the class somewhere else???

Blackbam     sagt:

am 03. März 2014 um 17:15 Uhr

Hello Lucy, basically it works like this:

First possibility: Define a class in editor-style.css and the text in the visual editor in the backend can be styled with this class
Second possibility: Define a class in editor-style-shared.css and the class will apply in the visual editor in the backend and in the frontend.
Third possibility: Define inline styles directly at the Plugin options page/ or declare a new class as inline style which you also define in editor-style-shared.css

Does this help?

madnigaz     sagt:

am 09. März 2014 um 18:31 Uhr

Hi Bam
I wanted to use the "editor-style.css" sheet created by this plugin, by putting in already downloaded css files from google search.
This e.g. :

body {
  color: gray;
  background-color: white;
  font-family: verdana, helvetica, arial, sans-serif;
  font-size: 71%;  /* Enables font size scaling in MSIE */
  margin: 0;
  padding: 0;
}

html > body {
  font-size: 8.5pt;
}

acronym, .titleTip {
  border-bottom: 1px dotted gray;
  cursor: help;
  margin: 0;
  padding: 0 0 0.4px 0;
}

acronym:hover, .titleTip:hover {  /* Ignored by MSIE. The nerve! */
  border-bottom: 1px solid rgb(70,130,180);  /* 'steelblue' not recognised here by Opera */
}

.doNotDisplay {
  display: none;
}

.smallCaps {
  font-size: 110%;
  font-variant: small-caps;
}

============== but it is not showing in the styles dropdown menu.

I just want to create dropdown items in Styles menu, by copying and pasting OpenSource css codes available out there.
I wont be using the Provided Table that lets us create "1" css rule at a time.
Neither do I want to change the TINY MCE's "outfit" i.e. its clothes :)
Only creating the Styles dropdown menu's items.

Any guide relating to that?
Will be appreciated.

Tim   sagt:

am 19. März 2014 um 21:02 Uhr

Hi David,

I've just installed your plugin and it works great, the only thing is that the Styles dropdown menu shows all the css styles in the parent theme. I'm using a child theme and I've created my editor-styles.css directory and hooked it up using the advanced custom directory option. This works fine - my styles are in the menu and apply perfectly - but they are at the bottom of a huge list! How do I remove / edit exactly which styles are shown in the dropdown menu?

Many thanks
Tim, London

Blackbam     sagt:

am 21. März 2014 um 15:26 Uhr

@madnigaz: Hey I think the solution for this problem is really easy? You just have to go to the Plugins option page

Settings -> Tinymce Prof. Styles

This is the correct location to create the actual styles for the dropdown. Editor-style.css is just for styling what your TinyMCE looks like.

Blackbam     sagt:

am 21. März 2014 um 15:32 Uhr

@Tim: Hi Tim,

unfortunatly I did not have the time yet to implement extra styling for multisite / child themes in the Plugin properly. You have to wait until I have time to update the Plugin or you implement a solution for adding the styles to the dropdown yourself - the basic code for doing this is shown below:

add_filter('tiny_mce_before_init', 'addCustomTinyMCEStyles', 5);

function addCustomTinyMCEStyles($initialArray) {
$modifiedArray = $initialArray;

$modifiedArray['theme_advanced_styles'] .= ';My Style=mystyle;';
//strip first and last character if it matches ";"
$modifiedArray['theme_advanced_styles'] = trim($modifiedArray['theme_advanced_styles'], ';');
return $modifiedArray;
}

Sean     sagt:

am 06. Mai 2014 um 04:10 Uhr

Hi, I know how to use CSS well enough to style text, but what exactly am I supposed to do to get the plugin to work? So far I have put .highlight-yellow {background-color:#FFFF00;} into editor-style.css & editor-style-shared.css I have also gone to the plugin settings and and created one with the title "Highlight Yellow", css class "highlight-yellow", css style "backgroundColor", ad value "#FFFF00". The only thing that has come from all three of those setting combined is that when I click the formats button in tinyMCE Advanced I see the words Highlight Yellow in a box at the upper left of my admin screen, way out of place, no click function, and doesn't scroll with the page. How exactly do we add something to the formats box or wherever in tinyMCE to make this work? and Why has my attempt so far had no effect?

Py   sagt:

am 06. Mai 2014 um 16:52 Uhr

Hey, I'm trying to add custom format and I did not find "TinyMCE Prof. Styles" in Settings? I've only "Tiny MCE Advanced" where i choose buttons to show or not but no options to add formats. Bug? Thanks

Miriam   sagt:

am 12. Juni 2014 um 03:32 Uhr

Hi Bam,
can you confirm have worked this out right:

To get items in the drop down list in TinyMCE, you have to make them in your gui editor (it is not looking at the style sheets to work out what to insert).
You can't put them in that drop down without defining them.
The style definitions are injected into the html as hard coded styles, rather than using the style sheets to display.

Style sheets
I chose to create a folder in wp-content for the style sheets.
I put the folder name in to the settings, but it got added to the css stylesheet name, it would not recognise that there was a folder . It would not allow me to add a final slash either.
Then at some point it stopped letting me edit that "folder" name.
So I deactivated and uninstalled the module to clear the info in the database related to this.

I then reinstalled the module: but the folder name was still there, and still not editable, and the plugin cannot find the folder or the file and gives an error message.
So: the uninstall is not working well, since it did not delete the date form the database.

I am not sure what the purpose of the files are, if you have to define the styles in the GUI and the plugin injects the styles in the html.

I would rather care ate my css in my css file, but can't see how to do that with this plug in.

Any feedback would be welcome.

Cheers
Miriam

jack     sagt:

am 18. September 2014 um 15:02 Uhr

Hi blackbam I love your plugin, but since i update to wordpress 4.0, it stop working... The formats selector in the new tinymce editor is totaly empty. Have you got a quick fix to solve this issue I will donate if you keep updating this plugin. It's very useful. Thanks!!

Blackbam     sagt:

am 25. September 2014 um 00:12 Uhr

Hi Jack

thanks a lot for reporting this issue. Currently I do not have a quick fix, but I will care for this problem and try to release an update asap.

BR David

Blackbam     sagt:

am 03. Oktober 2014 um 17:03 Uhr

@Miriam (late answer): The purpose of the files is to style the editor itself. If you want to provide CSS-Classes to the user, you have to create these in the GUI.

Peter   sagt:

am 10. Oktober 2014 um 12:43 Uhr

Hi Blackbam,

Thanks for the plugin, saves me a lot of time. However, now that I got it working, I created an editor role for someone else to use on my site, and that role does not have permission to the new formats I created for him.

Is there a setting somewhere I am missing?

Thanks in advance,
Peter

Blackbam     sagt:

am 19. Oktober 2014 um 20:43 Uhr

Hello Peter

well I tested the Plugin with an editor role and for mit it works. I usually use it in combination with TinyMCE Advanced, do you do this?

Furthermore I noticed that new users usually have the second row in tinyMCE set to INVISIBLE. May this be the problem?

BR
David

siri lindskrog     sagt:

am 15. Januar 2015 um 01:51 Uhr

Hello, i've tried this plugin before and after making different styles in the settings hey would show up so i can choose them when i write a post, but now it doesnt work like that. Did i do something wrong? Best regards and thank you, Siri

Deelite   sagt:

am 09. Februar 2015 um 23:57 Uhr

How do we go about and setting up our first style through the plugin? I want to have a block of text be a different color than the rest of the paragraph (say make the block of text red) How do set it up? I have: title: Red Text Type: selector type value: p Css Style: color #660000; Save the new stye., but when I go to select text within my editor to make it red, The "Format' shows my option, but its "greyed" out and when I try to select, nothing happens. What am I doing wrong? A good step by step to creating at least 1 type of style in the plugin would be helpful

Michael   sagt:

am 28. Februar 2015 um 23:59 Uhr

Love this plugin, but it seem to be broken with the latest version of TinyMCE advanced, preventing the the TinyMCE toolbars from showing and generally breaking the visual editor. Might there be an update on the way? Thanks, Michael

Michael   sagt:

am 02. März 2015 um 00:10 Uhr

Actually,regarding my previous comment, this seems to just be a configuration issue. If you have the stylesheets in place, it works. Perhaps the plugin can do a better job of not breaking the interface when they are not present, and/or provide a warning message as to what's going on, as installing it without a proper configuration does make it appear broken.

Kike     sagt:

am 23. März 2015 um 17:09 Uhr

Hi, thank you for the plugin, it saves a lot of time and makes things easy. Just one small problem, i cannot delete a style created, checking the X in the delete field and saving, but it doesn't .-) Any idea? Using WP 4.1 and tiny mce advanced 4.1.7 Again, thank you

Blackbam     sagt:

am 11. April 2015 um 21:45 Uhr

Hey the fact that it is greyed out should not be a problem. However I do not know your individual site and editor configuration. Just check if everything works with a plain WordPress installation and go for debugging.

Blackbam     sagt:

am 11. April 2015 um 21:47 Uhr

Hey Michael thanks for the information. I will have a new debugging review soon.