This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Our next available supporter will start replying to tickets in about 11.40 hours from now. Thank you for your understanding.
This thread is resolved. Here is a description of the problem and solution.
Problem: When trying to configure WPML, the third step encountered problems:
Warning: include(*/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/../../lib/twig/src/Cache/FilesystemCache.php): failed to open stream: No such file or directory in */wp-content/plugins/sitepress-multilingual-cms/vendor/composer/ClassLoader.php on line 444 Warning: include(): Failed opening '*/wp-content/plugins/sitepress-multilingual-cms/vendor/composer/../../lib/twig/src/Cache/FilesystemCache.php' for inclusion (include_path='.:/opt/alt/php73/usr/share/pear') in */wp-content/plugins/sitepress-multilingual-cms/vendor/composer/ClassLoader.php on line 444 Fatal error: Uncaught Error: Class 'WPML\Core\Twig\Cache\FilesystemCache' not found in */wp-content/plugins/sitepress-multilingual-cms/lib/twig/src/Environment.php:265 Stack trace: #0 */wp-content/plugins/sitepress-multilingual-cms/lib/twig/src/Environment.php(130): WPML\Core\Twig\Environment->setCache('*') #1 */wp-content/plugins/sitepress-multilingual-cms/classes/wpml-wp/class-wpml-wp-api.php(1240): WPML\Core\Twig\Environment->__construct(Object(WPML\Core\Twig\Loader\FilesystemLoader), Array) #2 */wp-content/plugins/sitepress-multilingual-cms/classes/templating/class-wpml-templates-factory.php(117): WPML_WP_API->get_twig_environment(Object(WPML\Core\Twig\Loader\FilesystemLoader), Array) #3 */wp-content/plugins/sitepress-multilingual-cms/classes/templating/class-wpml-templates-factory.php(67): WPML_Templates_Factory->maybe_init_twig() #4 */wp-content/plugins/sitepress-multilingual-cms/lib/twig/src/Environment.php on line 265
Solution: It seems that the issue was caused because some files were missing from the plugin's folder. I updated the plugin's files and now the issue is solved.