Skip Navigation

[Résolu] Class 'Litespeed_Cache_ESI' not found errors in log

This support ticket is created Il y a 6 années et 4 mois. There's a good chance that you are reading advice that it now obsolete.

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.

Aucun de nos assistants n'est disponible aujourd'hui sur le forum Jeu d'outils. Veuillez créer un ticket, et nous nous le traiterons dès notre prochaine connexion. Merci de votre compréhension.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Ce sujet contient 6 réponses, a 2 voix.

Dernière mise à jour par julieP Il y a 6 années et 4 mois.

Assisté par: Beda.

Auteur
Publications
#1065092

Can you shed any light on these errors (in debug.log) please:-

[19-Jul-2018 15:18:39 UTC] PHP Fatal error:  Class 'LiteSpeed_Cache_ESI' not found in /home/mydomain/public_html/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/templates/metaform.php on line 13
[19-Jul-2018 15:18:39 UTC] PHP Fatal error:  Class 'LiteSpeed_Cache_ESI' not found in /home/mydomain/public_html/wp-content/plugins/types/vendor/toolset/types/embedded/includes/fields.php on line 68

Thanks

#1069107

There is no occurrence of that class at all in Toolset.
The field mentioned in the error as well do not call such a class.

I suggest to delete Toolset and download it from here
https://toolset.com/account/downloads/

Then, upload those to your FTP and activate them

Is the issue still present?

#1069110

Hi Beda

Thanks for swift attention.

This is the way I always install Toolset plugins (and upgrades). I have, however, downloaded all again, deleted files on the server and uploaded/activated from new downloads. No new messages have appeared but I don't know what triggered the error message originally (it was 10 days ago) and there's been none since so it looks a bit random.

Can you suggest any 'actions' I can try performing to reproduce the error?

#1069140

That class does not exist, and is not called within any Toolset Plugin.

It seems due to another Software as other users reported the same error in totally different forums:
https://wordpress.org/support/topic/php-fatal-errors-7/
https://wordpress.org/support/topic/open_basedir-restriction-in-effect-24/

If you still have those files, please tell me what you see at the lines:
...plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/templates/metaform.php on line 13
...plugins/types/vendor/toolset/types/embedded/includes/fields.php on line 68

I see no reference to such class or any function that calls such class.

The code seems from a cache plugin, maybe the error was mixed up with another Toolset Error?

However if its gone with a fresh install I think its fine.

#1069183

Line 68 in fields.php:-

function wpcf_admin_fields_get_group( $group_id, $post_type = TYPES_CUSTOM_FIELD_GROUP_CPT_NAME,

Line 13 in metaform.php:-

$field_additional_classes = apply_filters('toolset_field_additional_classes', '', $cfg);

Really appreciate the links to the wordpress support forum tickets, particularly the first one as it's a recent issue. Unless what I've pasted above is of concern, I think all I can do is monitor, wait for it to happen again then raise a ticket with the Litespeed developers.

I'll close this once I hear back from you.

#1069188

Nope, that is the exact same as I do and you will find as well in the new copies you downloaded.

I honestly do not know why the PHP error mentions Toolset Forms and Types files when we never invoke that class at all (it's not from our code)

The lines in our code are mainly for Fields.
So when you edit fields you may re-produce that error, if it is somehow replicable.
Or in Forms, where you use conditionals.

#1069258

It is a bit weird, isn't it!!

I'll monitor and re-open if needs be (although I doubt it has anything to do with Toolset)

Thanks for your help 🙂