-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Styles still not displaying in Format dropdown within Unyson wp-editor. #2454
Comments
I've tried fixing this on my own, but I can't really find a solution/workaround.. Anybody else experiencing the same behaviour and found a solution? |
I also have same issue.
It works in default editor: http://prntscr.com/eynkqm I'm using WordPress Version 4.7.3 and Unyson Version 2.6.16 |
Hey @yura-x! I just tried your code snippet and it worked, both for Text Block and for default editor. I'm on Unyson Can someone give proper reproduction steps for that problem? |
4.7.5 does not work anymore , @andreiglingeanu testing why , it worked until latest update |
These dont see the tiny_mce_before_init filter settings modifciations and coming back without anything custom compare this to image above and you will see that 3 keys are missing, so seems like all the attach_filters() fires to early all of a sudden. |
@andreiglingeanu , found the issue , on php 5.6.5 custom styles are not visible , on 7.x they are there |
This problem was previously mentioned in this issue: #1932
I thought my problem was fixed, but the problem is still (or again) occuring.
When I read the comments above, I can't seem to find a 'real solution'. Everything that I've seen above, I've tried and isn't working for me now.
Does it have to do with the location of the code? Mine is in my functions.php file, at the bottom.
I tried debugging this by printing the $init_array, this gives back the array of the TinyMCE editor which does contain the added styles. But for some reason this array doesn't reach the TinyMCE display function or something like that.
Anyone else still having problems with this?
The text was updated successfully, but these errors were encountered: