"I.current is null" error

Support
#1

Hi,
With the latest version of the Pro theme (v6.5.5), the cornerstone raises This element could not render due to invalid markup. You may have unclosed HTML tags in your content. error as soon as a new section is added. This also happens when we try to create a new page from scratch. Looking into the console, we see this error:

TypeError: I.current is null
    useRef https://.../wp-includes/js/dist/vendor/react.min.js?ver=18.3.1:2
    anonymous https://.../wp-content/themes/pro/cornerstone/assets/js/app.react18.7.5.5.js?ver=7.5.5 line 117 > Function:3
    i https://.../wp-content/themes/pro/cornerstone/assets/js/app.react18.7.5.5.js?ver=7.5.5:117
    React 10

The same error happens when all plugins but the cornerstone are deactivated. Could you let me know what the issue is and how we can solve it?

#2

Hi Bianca,

Thanks for reaching out.
Please note that a few hours ago we released another version of the theme with some fixes, I would recommend you update Pro to the latest version, i.e. 6.5.6, and check if that resolves your problem or not.
If not, there might be some different reasons behind your reason, I would like to suggest troubleshooting the following common issue to help us recognize the reason.

1.Theme Related Issue
2.Plugin Conflict
3.Theme Update related issue
4.Child Theme Related issue
5.CSS/JS Customization
6.Disabling Cache
7.Disabling CDN

If you discover that an issue is coming from a custom code or 3rd party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins.
If none of the above helps, please provide login credentials for your site in a secure note to examine it further, including:

– WordPress Site URL & Login URL
– WordPress Admin username/password

To create a secure note, click the key icon underneath any of your posts.

secure-note
secure-note1040×250 15.3 KB

Thanks

#3

I couldn’t find the reason. Please see the credentials in the secure note. Thanks!

#4

Hi Bianca,

It will be very difficult for us to tell what the reason behind the issue was. I would suggest you contact the service provider with the problem for more information.

Thanks

#5

Hi @tristup , thanks for your response but the problem is still there and doesn’t seem to be related to the hosting.

#6

Hi Bianca,

I just checked it in the given URL and found that the Cornerstone is working fine. I have tried to check by adding a new section to an existing page and also created a test page with Section, Row, Column, and other elements.

Thanks

#7

@tristup, very strange that it works for you but not for me and my colleagues. When we click on cornerstone -> new blank page -> add section, we get the error message. The same happens when I add a new section to the test page you have created.

Thanks

#8

Hello Bianca,

I was able to replicate the issue on my end. It seems that there might be an issue with CORS and the Access-Control-Allow-Origin. I would suggest you please have a look at this article to get rid of this issue.
https://azdigi.com/blog/en/website-tutorials/wordpress-en/how-to-fix-the-blocked-by-cors-policy-error-on-wordpress/

If the issue still persists after getting rid of the CORS and the Access-Control-Allow-Origin issue please clone your website to the staging server and share the staging server site admin login details and FTP login of the staging server so we can check it on our end without breaking your live site.

Thanks

#9

Hi @prakash_s, thanks for your response. Unfortunately, enabling CORS by adding Access-Control-Allow-Origin: * header didn’t solve the issue. Please see the staging env credentials below.

#10

You’re hosting a JS library (React) from a CDN (https://c0.wp.com), but it’s not being hosted from your site everywhere. Which is causing the conflict you see. It’s usually JetPack that does this. You can try to deactivate that plugin in the mean time, while we release a fix for you. Have a great weekend.

#11

@charlie, thanks for looking into it. Deactivating JetPack is not possible for the websites hosted by wordpress.com. We will wait for the fix.
Wishing you a great week ahead.

1 Like
#12

Hi Bianca,

Glad that we are able to help you.

Thanks

#13

Hi,

Could you please provide an estimated timeframe for when you will release the fix?

Thanks

#14

Hey Bianca,

We don’t have any ETA but rest assured that there will be a fix.

Thank you.

#15

We’ll have a fix released on Monday. Have a great day.

1 Like
#16

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.