4:24 am
February 5, 2023
I've observed an issue that when the option to extract full text articles is enabled, syndication continuously fails, which occurs on every feed that I've configured. Below is a brief snippet of the log (the log generally has dozens of similar entries):
[07-02-23 03:02:08] Processing a new post...
[07-02-23 03:02:08] Trying to extract full text article
[07-02-23 03:02:08] Operation failed. Unable to retrieve full-text content.
[07-02-23 03:02:08] The post will not be added.
[07-02-23 03:02:08] Unable to parse https://
[07-02-23 03:02:08] 0 posts were added.
[07-02-23 03:02:08] Feed syndication failed
Disabling this option syndicated the feed but the content is too short and not suitable for posting. Important to note that this was never an issue with CyberSEO lite using the same RSS feeds - this previously worked properly and only started after upgrading to the Pro version.
The only difference now is that I've also configured the OpenAI option. Again, with full text extraction disabled, syndication and OpenAI generation works fine but the content is far too short.
Many thanks in advance.
4:28 am
February 5, 2023
Interesting point, I wasn't aware of this.
It's the same server config as per when using CyberSEO Lite so I'm not sure if there's an added step with Pro that requires installing this script that wasn't required with the Lite version.
Do you have a reference I could look at to understand the process of validating/installing this script?
4:31 am
February 5, 2023
Please read the instruction above. The Full-Text RSS was included into the CyberSEO Lite distributive, because CyberSEO Lite was a GPL project. CyberSEO Pro is a proprietary one. It can not include any GPL scripts, so the Full-Text RSS scrip it being downloaded separately as an add-on and its being used as a 3rd-part service via RSET API only, which is which is fully compliant with the requirements of the GPL.
4:46 am
February 5, 2023
Got it, I can see that the full text extractor URL in the general settings area has been populated and when opening it in the browser directly, it returns a 'No URL specified' response
Now, even with the script in place, I've re-enabled full text extraction and re-syndicated some of the feeds and they still return the same error... Is there something else I'm missing here?
Most Users Ever Online: 541
Currently Online:
5 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 68
Freedom: 61
Pandermos: 54
MediFormatica: 49
B8europe: 48
Member Stats:
Guest Posters: 337
Members: 2853
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1640
Posts: 8352
Newest Members:
wanmarkets, torontomark48, info.ckmedianetwork, contact.mybeautystar, samuelbodde, john.prushAdministrators: CyberSEO: 3947