Log In
Home
(0 votes) 11:38 pm
December 30, 2024
Offline
Login to see this linkLogin to see this link5:17 am
July 2, 2009
Offline
It's not clear from your screenshots what you're trying to do and how. I can see that you have character encoding issues, but you haven't provided a link to the source of the content you're trying to import.
Also, what method exactly do you plan on using to translate the content - Google Translate, DeepL, Yandex, or some AI language model?
Please always include your Syndicator log.
8:36 am
December 30, 2024
Offline
1. Login to see this link
I use my recordings. There are problems in the preview, but there are no problems with encoding on the site.
2. Login to see this link
Here I try to make a translation through AI, but it does not translate anything, publishing the original text as a translation. The logs do not write anything about these actions
9:20 am
July 2, 2009
Offline
Your screenshot shows that you are having problems displaying the encoding, and this is most likely due to your server settings or incorrect plugin settings. Here's what the preview of your feed looks like on the test site with default settings:
Your feed is UTF-8 encoded, and this is clearly stated in the feed header (<?xml version="1.0" encoding="UTF-8"?>). The content displays correctly on the test site, so the issue is likely with how your server or WordPress handles the feed during the preview stage.
Please make sure your server is configured to handle UTF-8 encoding correctly. If you are using Apache, check your .htaccess file for the AddDefaultCharset UTF-8 directive and add it if necessary. For Nginx, make sure your configuration file includes the charset utf-8; and restart the server after making changes.
Also make sure your PHP settings are correct. Open your php.ini file and make sure default_charset = UTF-8 is set. This is critical for PHP to properly process and output content in UTF-8.
If you have any plugins or custom configurations in WordPress that may affect how the feed is fetched and displayed, temporarily disable them to see if the issue is resolved. This includes any caching or content filtering plugins.
Finally, please provide the Syndicator log for detailed analysis. This will help to identify any specific errors or conflicts during feed processing.
9:25 am
December 30, 2024
Offline
Ok, will check! And what about second question ?
9:30 am
July 2, 2009
Offline
The answer to your second question should be visible in your Syndicator log. However, if your WordPress sees imported Cyrillic characters as gibberish, the AI model won't be able to understand the text, so it won't be translated. So the first thing you need to do is fix the encoding problem.
10:37 am
December 30, 2024
Offline
CyberSEO said
The answer to your second question should be visible in your Syndicator log. However, if your WordPress sees imported Cyrillic characters as gibberish, the AI model won't be able to understand the text, so it won't be translated. So the first thing you need to do is fix the encoding problem.
Post content has problems Login to see this link
Full text is correct Login to see this link
Is this still a server issue? Thanks
10:58 am
July 2, 2009
Offline
Yes, it still looks like a server configuration issue. The full article is imported from an HTML page, while the post content preview uses XML (RSS feed) as its source. Those are two different URLs in two different formats.
Can I see your Syndicator log?
12:47 pm
December 30, 2024
Offline
CyberSEO said
Yes, it still looks like a server configuration issue. The full article is imported from an HTML page, while the post content preview uses XML (RSS feed) as its source. Those are two different URLs in two different formats.Can I see your Syndicator log?
Login to see this link
I wrote to hosting support and waiting for the fix
But everything is translated correctly from the feed. The problem is if you do a mass translation through the WordPress admin panel
Thanks
12:52 pm
July 2, 2009
Offline
Please do not post screenshots. Simply copy the complete log and paste it into your next post.
1:00 pm
December 30, 2024
Offline
Login to see the quote
1:09 pm
July 2, 2009
Offline
According to the log, the article was successfully translated into English, and here is the content of the generated post:
Login to see the quote
I don't see a problem here. However, it seems that the generated post ID 10412 has been deleted. What was wrong with it?
1:28 pm
December 30, 2024
Offline
For some reason it created a duplicate.
1:34 pm
December 30, 2024
Offline
And text in Ukrainian but link in Russain
Login to see this link
Login to see this link
Login to see this link
1:42 pm
July 2, 2009
Offline
evgeniyzhdanyuk said
For some reason it created a duplicate.
This happens when the feed is manually pulled twice without waiting for the previous process to finish, or if the duplicate post checking rules are incorrectly configured (in your case, the "link only" rule should be selected).
But now we try to solve the problem described in your first post. You say that the plugin doesn't translate articles, although your log shows that the article was translated into English.
As for translation from Russian to Ukrainian or vice versa, please always attach your Syndicator log, because screenshots don't contain any information at all.
Each time you describe a situation, below your description should be a complete plugin-generated log for that case. There should be no links to screenshots below your description. - Just the log and nothing else.
In case you are using the Polylang or WPML plugin, be sure to watch this tutorial video:
8:04 pm
December 30, 2024
Offline
Don't understand, why it publish to EN version if in my setting
Polylang language - English
AI translation - Poland, but it publish to English version and I have to transfer it to Polish version and link pages to the language version again
Also same with another languages, EN to Norwegian Login to see this link
Login to see the quote
12:47 pm
December 30, 2024
Offline
Also hosting support said
I couldn't find such a text with scribbles anywhere, neither on the site nor in the database, if this text is pulled from the database, then it is correctly displayed both on the site and in the database in the wp_posts table
Regarding the display in this plugin, maybe it should be like this? This could be the display of text without decoding, which is sent in raw form via the web. In the browser, the text is decoded and already on the site it is displayed correctly.
I see that this text is correctly displayed on the site.
If I switch to the FullText article mode, then the text is also displayed correctly, I am attaching screenshots.
If this should not be the case, then try clearing all the caches that you use on the site and in plugins or try reinstalling this cyberseo pro plugin, perhaps some data was cached by the plugin even before the encoding was changed on the server.
4:53 am
July 2, 2009
Offline
evgeniyzhdanyuk said
Don't understand, why it publish to EN version if in my settingPolylang language - English
AI translation - Poland, but it publish to English version and I have to transfer it to Polish version and link pages to the language version againAlso same with another languages, EN to Norwegian
The plugin publishes translated articles to the Polylang language group whose language is selected Login to see this link (must be set to the translation Polish, Norwegian etc). If you select English, this will be the language selected for the post. You write above that you selected English. What result do you expect with these settings?
Find more information here: Login to see this link
5:03 am
July 2, 2009
Offline
evgeniyzhdanyuk said
Also hosting support saidI couldn't find such a text with scribbles anywhere, neither on the site nor in the database, if this text is pulled from the database, then it is correctly displayed both on the site and in the database in the wp_posts table
No. What you see in the preview is not taken from the WordPress database. The plugin simply downloads the feed content using either cURL or file_get_contents(), depending on the settings. The text encoding is not changed, decoded, or modified in any way during this process. Since the source RSS feed is explicitly in UTF-8 format, the server should process it as UTF-8. However, in your case, this does not happen.
The plugin simply retrieves the RSS feed and directly displays the content in the preview - exactly as it is received from the server. This means that the text shown in the preview is neither saved to the database nor altered by the plugin. It is simply an echo of the raw data as received by your server.
In your specific case, it seems that the UTF-8 encoding from the feed is being ignored by your server. This is not normal behavior and indicates that there might be an issue with the server's handling of text encodings.
11:58 am
December 30, 2024
Offline
The Yaost plugin shows only 10 entries in the RSS but your plugin for filling meta tags works with it. AllinoneSeopak displays many entries in the RSS but does not work with your plugin for filling meta tags. How can I fix the situation with the Yaost plugin so that it shows all the entries or how can I do this with your plugin?
All RSSMost Users Ever Online: 541
Currently Online:
2 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 85
s.baryshev.aoasp: 68
Freedom: 61
harboot: 56
Pandermos: 54
MediFormatica: 49
Member Stats:
Guest Posters: 337
Members: 2887
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1666
Posts: 8502
Newest Members:
mexwebmx, dennis10191977, taylorhucker, cesarserna, electroday, keeplossadAdministrators: CyberSEO: 4013