Skip Navigation

[Resolved] Toolset Types / Classic Editor Causing Problems

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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9: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/Karachi (GMT+05:00)

This topic contains 5 replies, has 2 voices.

Last updated by Waqar 8 months, 2 weeks ago.

Assisted by: Waqar.

Author
Posts
#2647253

Tell us what you are trying to do?
We have a type set up "Documents" that we use for displaying a library of resources we have developed. It was using the classic editor. The text, however, was showing up as white, and the editor's buttons were all missing. When I switched it to the new block editor in toolset types, that fixed the ability to do text, but it broke the custom fields that we use to auto generate links to Google Drive. So I switched it back, and now when I go in to edit or create a new Document I get a blank screen. I turned on debugging and found these errors:

Deprecated: ctype_digit(): Argument of type WP_Post will be interpreted as string in the future in /data/www/live/wp/csu/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/field/group/factory.php on line 134

Warning: Cannot modify header information - headers already sent by (output started at /data/www/live/wp/csu/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/field/group/factory.php:134) in /data/www/live/wp/csu/wp-admin/admin-header.php on line 9

Is there any documentation that you are following?
No.

Is there a similar example that we can see?
You would need to be able to log on to our admin panel

What is the link to your site?
hidden link

#2647827

Hi,

Thank you for contacting us and I'd be happy to assist.

The errors and warnings that you've shared are safe to ignore and seem unrelated to the issue at hand.

I'll recommend testing this with all non-Toolset plugins disabled and with a default theme like Twenty Twenty-One.

If it's fixed, you can start adding the disabled items, one by one, to narrow down to a possible conflicting one.

In case the issue persists, you're welcome to share temporary admin login details, along with the exact steps to see the issue.

Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.

regards,
Waqar

#2649567

Thank you for sharing these details.

Even with the same fields and settings, I couldn't reproduce this issue with the Divi builder on my test website.

This suggests that something specific to your website is involved. Do I have your permission to download a clone/snapshot of your website to test it on a different server?

#2649777

Good Morning,
Yes you may download a copy of the site to test. Let me know if you need me to do anything to enable that. Thanks!

#2650179

Thank you for the permission and I've downloaded the website's clone.

I'll be running some tests on this and will share the findings, as soon as this testing completes.

Thank you for your patience.

#2651081

Thank you for waiting.

During troubleshooting, I was able to narrow down the issue to the use of the '<iframe>' HTML tag, in the description text of the field 'Document Embed Code (Optional)'.
( screenshot: hidden link )

If you only add it as 'iframe' ( i.e. not as the HTML tag ), the Document Post Editor screen will start loading correctly.
( using both the classic or the block editor )

#2651953

Thank you so much; that worked on our side as well. Thank you and have a great evening!

curtisF-2 confirmed that the issue was resolved on 2023-10-12 00:30:01.
This ticket is now closed. If you're a Toolset client and need related help, please open a new support ticket.