Hello.
(I translated the text at DeepL, so sorry if it's not clear)
1. language switcher URL does not work correctly
do_action('wpml_add_language_selector');
The URL linked to the language switcher output by the above code shows incorrect URLs.
Example: hidden link
Correct: hidden link
This event occurs only on article pages of custom post types.
Also, the following error message is displayed when accessing the URL that is supposed to be correct.
"There has been a critical error on this website."
2. Translated pages do not appear in the archive
Only translated pages are not displayed in the taxonomy archive of custom post types or in the article list view using WP_Query.
(This may be related to the article page error above.)
If you set "Post Types Translation" to "only show translated items", the articles are not displayed, and if you set "use translation id~", only untranslated pages are displayed.
It would be helpful to know the cause.
Thank you in advance.
I understand the issue you're having. In an attempt to directly observe the issue, I tried accessing your website. However, due to browser login protection, I was unable to proceed with the examination.
Regarding the Fatal error you mentioned when accessing a specific link, could you please activate the WordPress Debug log to see if any errors are being logged as a result? For guidance on enabling the debug log, you might find this tutorial helpful: https://wpml.org/documentation/support/debugging-wpml/.
If you encounter any errors in the log, kindly copy them and provide the details in your next message. This will allow me to conduct a more thorough analysis and advise you on the subsequent steps.
Additionally, the issue with Translated articles not appearing in the Archive may stem from how the WP_Query is being implemented. Would you be able to share the relevant code snippet? Although custom code support falls outside our standard support parameters, I am willing to review the code and offer suggestions on how to ensure translated posts are visible in the archive.
I look forward to your reply and am eager to offer further assistance.
Hi.
We checked the debug log and found that the following information was repeatedly recorded.
---------------------------------------
[07-Mar-2024 21:44:59 UTC] PHP Deprecated: Creation of dynamic property Whip_RequirementsChecker::$configuration is deprecated in /var/www/html/wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/Whip_RequirementsChecker.php on line 37
[07-Mar-2024 21:44:59 UTC] PHP Deprecated: Creation of dynamic property Whip_RequirementsChecker::$messageManager is deprecated in /var/www/html/wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/Whip_RequirementsChecker.php on line 38
>do_action('wpml_add_language_selector');
>The URL linked to the language switcher output by the above code shows incorrect URLs.
>Example: hidden link
>Correct: hidden link
>This event occurs only on article pages of custom post types.
>Also, the following error message is displayed when accessing the URL that is supposed to be correct.
>"There has been a critical error on this website."
The error text when accessing the "Correct URL" above is as follows.
---------------------------------------
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 40
[07-Mar-2024 21:49:46 UTC] PHP Deprecated: nl2br(): Passing null to parameter #1 ($string) of type string is deprecated in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 41
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 42
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 46
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 47
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 48
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 49
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 50
[07-Mar-2024 21:49:46 UTC] PHP Warning: Trying to access array offset on value of type null in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 51
[07-Mar-2024 21:49:46 UTC] PHP Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, null given in /var/www/html/wp-content/themes/kitte-theme/single-shop.php:56
Stack trace:
#0 /var/www/html/wp-content/themes/kitte-theme/single-shop.php(56): array_filter(NULL)
#1 /var/www/html/wp-includes/template-loader.php(106): include('/var/www/html/w...')
#2 /var/www/html/wp-blog-header.php(19): require_once('/var/www/html/w...')
#3 /var/www/html/index.php(17): require('/var/www/html/w...')
#4 {main}
thrown in /var/www/html/wp-content/themes/kitte-theme/single-shop.php on line 56
---------------------------------------
The code in the relevant section was reading the Custom Field data created in ACF.
---------------------------------------
$info = get_field('info');
$info_judge = array_filter($info); // line 56
---------------------------------------
I would be happy to know anything you can tell me with the above information.
Best Regards.
Let's tackle the issues one at a time. Based on the error log you've provided, there doesn't seem to be any critical errors or warnings stemming from the WPML plugin or its extensions. The fatal error you're encountering points to an issue within your theme's PHP code.
Specifically, the error at line 56 in the `single-shop.php` file arises because the `array_filter()` function expects an array, but instead, it's receiving a null value. This discrepancy could be the result of a failed database query, an unexpected function return value, or another operation that didn't produce the expected array.
To resolve this error, it's necessary to trace back and determine why the expected array is turning up as null. This might involve examining earlier segments of your code where this variable is initialized or modified. Please note, that addressing issues related to custom code, themes, or plugins falls outside our standard support scope. Therefore, we suggest consulting with the developer who wrote the code for more direct assistance. They should be able to identify the root cause and help rectify the issue.
For the issue with the Translated posts not appearing in the Archive - Thank you for sharing the WP_Query code. From the code, I noticed that you've defined a meta_key named 'yomigana' and in the meta query, you've defined a key named "coming soon". Could you please ensure that the same Meta that you've defined are also set for the translated post? If you want the same Meta information to appear in the translated posts, please go to "WPML > Setting" and search for both keys in "Custom Field Translation" and "Custom Term Meta Translation" section.
If they appear in the result, set the translation preference for both keys to "Copy", and update the default page and the translation as well.
If the translated posts still not showing in the archive, you can add the following argument right after "'order' => 'ASC'," in the WP_Query code:
'suppress_filters' => true,
I hope the information above helps. Please feel free to let me know if you need further assistance. I'll be happy to help.
I reviewed the Custom Field settings as you suggested and the error is gone. Thanks!
Now I have another problem: the URL for the language switcher.
As shown below, incorrect link URLs are output only on custom post type article pages.
(Base language is Japanese)
What could be the cause of this problem?
*URLs are supposed to be assigned by language, but they are all assigned "en".
Thank you for the update. Glad to hear that the suggestions helped! 🙂
Regarding the problem with links - Could you please check and ensure that the posts you've within the "Shop" post type have been translated into other languages? If not, please translate them and check again.
If they have been translated, then please try the following:
- Please go to WPML > Support > Troubleshooting
- Click on these buttons:
-- Disable cache for language switcher templates
-- Select "Shop" post type from the Dropdown and click on Synchronize posts taxonomies
-- Clear the cache in WPML
-- Assign translation status to duplicated content
-- Set language information
-- Fix post type assignment for translations
Once the troubleshooting is completed, please clear the caches from your site and browser and check the posts in the Shop post type again.
Let me know how it goes. I will be happy to help if you need further assistance in this matter.
Best regards,
Prosenjit
The topic ‘[Closed] Incorrect link URL in selector and 404 when translating custom post type’ is closed to new replies.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
