Hi, Thanks for alerting me to this issue.
Do you have this problem when in dark mode? What I mean is, does the problem disappear when you’re in normal mode only to occur when you’re in dark mode?
Also, have you tried deactivating the plugin to be sure the problem comes from there?
-
This reply was modified 5 years, 7 months ago by
Ike Felix.
The problem appears in both dark and non-dark mode. The problem goes away if I disable the plugin and re-appears if I activate it again.
I tried it in a fresh wordpress installation on localhost and I can’t see post categories when the plugin is activated
Hi, sorry for the problems you’re having. I think this is an isolated issue. A future update to this plugin will come with activating the dark mode for the admin dashboard as an option.
However, in order to disable the dark mode in the back end, you have to do two things:
- Go to the Blinds plugins directory and open the ‘blinds.php’ file in a text editor.
- Comment-out lines number 48 and 63. That is:
Change this line of code at line 48:
echo $content;
to this:
//echo $content;
And also change this at line 63:
add_filter('in_admin_header', 'osd_blinds_widget');
to this:
//add_filter('in_admin_header', 'osd_blinds_widget');
Let me know if it worked for you.
Apologies for the inconvenience caused.
-
This reply was modified 5 years, 7 months ago by
Ike Felix.
-
This reply was modified 5 years, 7 months ago by
Ike Felix.
Although the icon to switch to Dark Mode doesn’t exist anymore the problem is still there. I cannot add any categories to my posts because they don’t show up.
Getting this error in the console when the plugin is activated and I’m at the Add New Post page (same error on Add New Page):
Uncaught (in promise)
{code: “invalid_json”, message: “The response is not a valid JSON response.”}
I installed the “Classic Editor” plugin to disable Guttenberg and the error disappeared, I can see Categories just fine while the plugin is active.
So there is something going on between Guttenberg and Blinds
Hi, I now perfectly understand your issue. Indeed, the plugin has a conflict with the Gutenberg editor.
You can comment out line 67 as a quick fix for the moment. The next update will solve this issue.
Thanks for bringing this to my notice!
Thank you for the quick responses π
You’re welcome. I’ll let you know when the update containing the fix is out.
Hi, there is an update right now. Let me know if you have further issues.
It all works perfectly now π thanks