Hi @birdmarketing
I have tested this on a staging site with WPML and a properly configured multilingual setup. The llms.txt file generates links for all available language versions.
If you enable the following checkboxes in the settings:
• Include meta information (publish date, author, etc.)
• Include post excerpts / meta descriptions
• Include detailed content
• Include taxonomies (categories, tags, etc.)
…the content is displayed for each language-specific link.
If the issue persists on your site, I may need temporary access to review your WPML configuration and resolve the problem directly.
Best regards,
LLMs Plugin Support Team
Hello!
I also have a problem with WPML.
The file is generated for all language versions, but the urls are duplicated:
https://accta.tools/llms.txt
All of urls have same language code /uk/.
All settings are as in the message above.
Hi @vgaran,
Thanks for reporting this issue.
We’ve identified the bug where llms.txt was generating duplicated URLs with the same language code for all translations when using WPML.
This has now been fixed in version 8.0.9 – each language version will correctly generate its own URLs in the llms.txt file. Please update to the latest release and re-generate the file to apply the fix.
Let us know if the issue persists after updating.
Best regards,
LLMs Plugin Support Team
@samsonovteamwork
While I know you have the best of intentions, forum policy is that you not ask users for admin or server access. Users on the forums are not your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
*Ask the user to install the Health Check plugin and get the data that way.
*Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
*Ask the user to create and post a link to their phpinfo(); output.
*Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
*Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
*Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem.
