@simonsj Thanks for the report. That does appear to be a bug in this plugin version’s Classic Editor support code. I’ve opened a GitHub issue here to track it.
This bug doesn’t occur in my test environment. So it may well be that the hidden text editors in your environment is the difference.
Unfortunately, I don’t think there’s any viable workaround at this time. Probably your best bet is to downgrade to plugin version 4.5.0 until this is fixed.
Sorry for the trouble!
Thank you so much for looking in to this!
Hi @simonsj , if you’re willing to live on the edge a little, there’s a new pre-release of the plugin available in the GitHub repo here. You’d download the font-awesome.zip file attached that release, and install it in WordPress via “Add New Plugin” and then use “Upload Plugin” to upload that zip file.
If you try it, can you let me know how it goes?
Hello, I had tried the test plugin but it didn’t seem to make any difference so I put back 5.0 on my staging site. I had also contacted the developers at Toolset to see if there was any conflict on their side. This was the response:
Dear Project,
Minesh from Toolset support has added the following message to your support thread: Conflict between toolset types and font awesome plugins
I chekked and I found that indeed the error belongs to the font-awesome plugin.
I see the following error on the browser’s console when I’m on edit page and the error belongs to font-awesome. The error belongs to font-awesome classic editor file:
=> https://stageuthealth.wpengine.com/students-test/wp-content/plugins/font-awesome/classic-editor/build/index.js?ver=5.0.1
Uncaught TypeError: Cannot read properties of null (reading 'parentElement')
at d (index.js?ver=5.0.1:1:1805)
at index.js?ver=5.0.1:1:2089
Can you please check with them and see if they have any fix for this issue.
Hi @simonsj, this part definitely was a bug in our plugin’s version 5.0.1:
Cannot read properties of null (reading ‘parentElement’)
I have no doubt about that. But also, that’s one of the issues that I believe is fixed in the 5.0.2-2 pre-release. If you’re still seeing that exact error message, it’s evidence that you’re still using a previous version of the plugin, rather than the newer 5.0.2-2.
Related, I notice in the error message you posted above that the stack track suggests that it was plugin version 5.0.1 that was running when that error was produced:
at d (index.js?ver=5.0.1:1:1805)
See the 5.0.1 after the = in that message? I don’t think that specific error message could be produced by 5.0.2-2.
It might be worth trying again to install 5.0.2-2 from the link I provided above, making sure that 5.0.2-2 is the one that’s running, and then see what behavior occurs. I don’t think you’ll see that same error message. If it still does not work, then I’d expect that the way in which it doesn’t work will be different from the previous way it failed. Gathering that information would be useful for improving the solution.
Hello, it seems that the error that toolset was seeing was resolved by the updated plugin but the text editor is still set to invisible. They suggested contacting wp bakery but even when I turn that plugin off the editor is still inviisble. Here is their message:
Dear Project,
Minesh from Toolset support has added the following message to your support thread: Conflict between toolset types and font awesome plugins
No – I do not see the error.
In order to miminize the cause of the issue and to ensure there is no conflict with the third-party plugins or theme you use:
Could you please try to resolve your issue by deactivating all third-party plugins as well as the default theme to check for any possible conflicts with any of the plugins or themes?
– Do you see any difference? if no:
At this time I suggest you should get in touch with WP Bakery Page Builder support.
I stopped using the plugin. The last time I tried it my text editor was still set to invisible. Thanks!
plugin version 5.0.2 has been released. I expect it to resolve the problem in the initial error report in this topic. If there are other issues that remain, please open a separate support topics to document them.
HI
Upgrading to 5.0.2 did not solve this issue for ALL our users. It worked for my user in wp-admin and on the front end using Toolset form, but not for my colleague’s user, who is also an admin on our site. If I log on to our website on her computer, it works fine too, so it must be some hidden user option or something. Any idea why it is working for me and not for her?
Thanks and kind regards
Simon
