[Resolved] Warning message after → WPML → Languages → Default flag format
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing a warning message about an undefined property in the Astra theme's extras.php file while configuring WPML, specifically related to stdClass::$menu_id on lines 508 and 546. Solution: We recommend checking if the menu_id property exists in the $args object using isset() to avoid the error when the property is undefined. You can temporarily update the following lines in the /wp-content/themes/astra/inc/extras.php file:
if (isset($args->menu_id) && in_array($args->menu_id, $astra_menu_locations)) {
This solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.
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.
Here's the error message shown on the website's root:
Warning: include(/redirect.php): Failed to open stream: No such file or directory in /home/httpd/vhosts/***.com/***.com/wp-content/plugins/sitepress-multilingual-cms/classes/request-handling/redirection/wpml-rootpage-redirect-by-subdir.class.php on line 45 Warning: include(/redirect.php): Failed to open stream: No such file or directory in /home/httpd/vhosts/***.com/***.com/wp-content/plugins/sitepress-multilingual-cms/classes/request-handling/redirection/wpml-rootpage-redirect-by-subdir.class.php on line 45 Warning: include(): Failed opening '/redirect.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /home/httpd/vhosts/***.com/***.com/wp-content/plugins/sitepress-multilingual-cms/classes/request-handling/redirection/wpml-rootpage-redirect-by-subdir.class.php on line 45
No worries! It looks like the procedure wasn't quite right, but you can try the following steps:
1) Create a file named "root-page.html" and save it in the root folder of your server (the same location as the redirect.php file). Make sure there are no empty spaces, so the file is starting on line 1.
2) Open the WPML settings and simply enter "root-page.html" without adding a forward slash ("/"). You can see a screenshot of this step hidden link redirect.png">here.
3) Lastly, resave your WordPress permalinks (WPML will prompt you to do this and provide a link).
By the way: we now have a root page, so the front end works properly. But the original issue was still not solved. We still see the error message at > WPML > languages
Warning: Undefined property: stdClass::$menu_id in /home/httpd/vhosts/***.com/***.com/wp-content/themes/astra/inc/extras.php on line 508 Warning: Undefined property: stdClass::$menu_id in /home/httpd/vhosts/***.com/***.com/wp-content/themes/astra/inc/extras.php on line 546 Warning: Undefined property: stdClass::$menu_id in /home/httpd/vhosts/***.com/***.com/wp-content/themes/astra/inc/extras.php on line 508 Warning: Undefined property: stdClass::$menu_id in /home/httpd/vhosts/variaduna.com/***.com/wp-content/themes/astra/inc/extras.php on line 546
Could you please provide a Duplicator copy of your site for further debugging? This will help us investigate why, despite all requirements being met now, the Astra theme is still causing an error on our GUI endpoint.
Thank you! You can go ahead and remove the file now. This was helpful in allowing me to reproduce the issue from scratch and escalate it to our compatibility team, who will contact the theme authors to get it resolved in their code.
In the meantime, I’ve found a temporary workaround you can apply. By checking if the menu_id property exists in the $args object using isset(), we can avoid the error when the property is undefined.
You can temporarily update the following lines in the /wp-content/themes/astra/inc/extras.php file:
Since we know it's treated by you: if there is only the admin user interface issue we'll be fine with it for the moment. Do you see any potential frontend side effects we should catch with the two code lines?
Currently, I haven't noticed any side effects. I’ve tested it locally, but it might be best to wait a few more days until our compatibility team contacts Astra, as they may resolve the issue quickly.
Currently, I haven't noticed any side effects. I’ve tested it locally, but it might be best to wait a few more days until our compatibility team contacts Astra, as they may resolve the issue quickly.
