Skip Navigation

[Resolved] when activating wpml string translations, getting fatal error

This thread is resolved. Here is a description of the problem and solution.

Problem: When I activate WPML String Translation with Forms active, I see a Fatal Error.

Fatal error: require_once(): Failed opening required 'WPTOOLSET_FORMS_ABSPATH/classes/class.conditional.php' in /wp-content/plugins/types/vendor/toolset/types/embedded/includes/conditional-display.php on line 35

Solution:
Open \wp-content\plugins\types\vendor\toolset\types\embedded\includes\usermeta-post.php
Comment out line #12 like so:

// require_once WPCF_EMBEDDED_ABSPATH . '/includes/conditional-display.php';

Update the file on the server.
Reactivate the conflicting plugins. You may see some PHP Warnings generated during this step, but that's okay.
Revert the comment you added in usermeta-post.php

This support ticket is created 5 years, 6 months ago. 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.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 8 replies, has 3 voices.

Last updated by Christian Cox 5 years, 6 months ago.

Assisted by: Christian Cox.

Author
Posts
#1249903

hey,
this is the error:

Warning: require_once(WPTOOLSET_FORMS_ABSPATH/classes/class.conditional.php): failed to open stream: No such file or directory in /home/istolar0/clients/com-unity/wp-content/plugins/types/vendor/toolset/types/embedded/includes/conditional-display.php on line 35

Fatal error: require_once(): Failed opening required 'WPTOOLSET_FORMS_ABSPATH/classes/class.conditional.php' (include_path='.:/usr/local/php71/pear') in /home/istolar0/clients/com-unity/wp-content/plugins/types/vendor/toolset/types/embedded/includes/conditional-display.php on line 35
The site is experiencing technical difficulties

any ideas?
thx!

#1250007

The conflict is between wpml string translation and toolset access. The error is generated when these two are activated together.

#1250275

May I log in and create a site clone so I can try to debug this? Private reply fields are available here.

#1251321

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Ido,

Christian is currently on holiday today but will be here tomorrow to continue investigating this one for you.

Thanks,
Shane

#1251327

Thx Shane!

#1252127

Okay thanks, I'm not able to replicate this error on a fresh site installation but I will escalate the copy of your site to my 2nd tier support team for further investigation. I'll let you know what I find out.

#1254431

Okay my 2nd tier support team provided a workaround that seems to resolve the problem on my local copy. Can you please try these steps on your site?
Open \wp-content\plugins\types\vendor\toolset\types\embedded\includes\usermeta-post.php
Comment out line #12 like so:

// require_once WPCF_EMBEDDED_ABSPATH . '/includes/conditional-display.php';

Update the file on the server.
Reactivate the conflicting plugins. You may see some PHP Warnings generated during this step, but that's okay.
Revert the comment you added in usermeta-post.php
Test the site and let me know if the problem is not resolved.

#1254473

Perfect, thx!
I see there's an update to "types" today - is the fix included in the new version?

#1254587

From what I understand there will be no permanent changes in the software to address this problem. You will comment out the offending code just long enough to get String Translation, Access and other Toolset reactivated, then immediately revert the change. Once reactivated, the errors should stop occurring. You may perform the workaround tasks before or after updating to version 3.3.1, it's irrelevant.

Feel free to reopen here if needed.