[Resolved] Call to undefined function get_current_screen() in /classes/class.file.php

[Author]

Posts

[Kristin]

Any time I try to update a post or page I get:
Fatal error: Call to undefined function get_current_screen() in /nas/content/staging/techwomen/wp-content/plugins/types/library/toolset/toolset-common/toolset-forms/classes/class.file.php on line 38

I fixed the issue on my end by adding require_once (ABSPATH . 'wp-admin/includes/screen.php');. Just curious if you guys are aware of this issue or have a fix in mind? Thanks!

[Shane]

Hi Kristin,

Thank you for contacting our support forum.

Actually in doing some searching on this issue the only solution that came up is the one that you provided here.

There is a similar issue with the ACF plugin which was resolved by using this exact method.

Thanks,
Shane

[Kristin]

Hi Shane,

Is there somewhere I can include this fix on my child theme or somewhere comparable that doesn't involve modifying the types plugin files?

[Shane]

Hi Kristin,

Not that i'm aware of however I can report this issue and our development team should be able to provide a more permanent fix in an update.

Thanks,
Shane

[Shane]

Hi Kristin,

It seems that this issue was already reported to the team. Also could you try reinstalling Types and see if the issue still remains because the issue could be due to corrupt files.

Thanks,
Shane

[Beda]

That error is mentioning a Core function of WordPress.
I have one other report of this, but I cannot replicate it.
There must be an edge case where the Core File wp-admin/includes/screen.php cannot be loaded when that code is triggered.

Please send me a Site's Snapshot, so I can analyse this.
I suspect this is a server issue, where the server or the WordPress install is customised in a way that does not allow the file to be read.
https://toolset.com/faq/provide-supporters-copy-site/

Thank you for the cooperation, once I have a site's snapshot I will be able to find the issue.

[Beda]

The issue seems Jetpack.
If removed/disconnected the issue should be gone.

I already escalated it to the Developers to have a look.
It seems to happen only if there is an Image Field in the Post Type and Jetpack is active.

[Beda]

This is solved now:
https://toolset.com/errata/saving-a-post-with-a-file-field-may-produce-an-error-if-jetpack-is-installed/

Thanks.