Skip Navigation

[Resolved] Conflict between toolset types and font awesome plugins

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 0 reply, has 1 voice.

Last updated by Minesh 3 months, 1 week ago.

Assisted by: Minesh.

Author
Posts
#2799352
Screenshot 2025-03-04 at 7.25.56 AM.png

I am trying to update the font awesome plugin to 5.0.1

We have custom fields that are applied to the page post type to create accordions. When I updated the font awesome plugin the default text editor for the page and the text editor for our custom accordion content field were set to hidden.

I read that one reason this could happen is there are conflicting versions of font awesome being loaded. Is there any change that Toolset would be updating their font awesome version to 6?

It doesn't affect the display of the page: hidden link, you just can't edit the content that is inside of the accordion panels. The errors are in the attached image.

#2799674

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

When you say you can't able to edit the content inside the accordion panels - do you mean you cant able to edit content in backend with accordion panels?

Can you please share exact steps that I will have to follow that should help me to see the issue as well as admin access details.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#2800140

Hello, I'm sorry it took me sol long to get back to you. Do you have an email that I could use to create an account for you? We use LDAP but we have it set to allow LDAP or user account but I don't see a way to add a password for you so I will have to send a reset link. Thanks!

#2800260

I'm sorry, I forgot to tell you in the last message, if you remove the custom tab container fields from the page post type the default text editor will work. Thanks!

#2800610

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Thank you I setup a password but I could not able to access the wp-admin as it asks me to setup two factor authentication.

Can you please disable two-factore authenticatin.

#2800614

I'm sorry, I have disabled DUO and cleared the cache.

#2800965

Christopher Amirian
Supporter

Languages: English (English )

Hi,

This is Christopher chiming in. Thank you for deactivating the 2-factor authentication. Minesh will be available tomorrow to take a look into the details.

Thank you for your patience.

#2801220

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

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:
=> hidden link

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.

#2801307

Hello, thank you for your response. I contacted the developers from the Font Awesome plugin and they asked me to try with the dev version of the plugin, it still doesn't work for me. Can you see a new error message? This is from them:

mlwilkerson wrote:

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 ( hidden link ). 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.

Post Link: https://wordpress.org/support/topic/conflict-between-font-awesome-5-0-1-and-toolset-types-3-5-2/#post-18368226
-----------
You are receiving this email because you subscribed to a forum topic.

Log in and visit the topic to reply to the topic or unsubscribe from these emails. Note that replying to this email has no effect.

#2801345

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

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.

#2801394

I sent your message to the font awesome people. I did try deactivating wp bakery but it didn't make a difference that I could see. I see a 404 error for this: hidden link. Could that have anything to do with it? Thanks!

#2801466

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Well - what if you try to disable the Toolset plugins?
- Do you see if working? if no: This is certainly not the Toolset issue.

#2801509
Screenshot 2025-03-20 at 7.15.30 AM.png

If you edit a post you can see the toolbar on the editor and both the visual and text tabs work. Posts don't have any toolset fields associated with them. I tried disabling toolset types but the page just displayed a critical error. Thanks for your help!

#2801530

Minesh
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Sorry but I need proof that I can share and escalate that the issue is from Toolset. I do not see or locate anything that its due to Toolset.