I do not see any issues as of yet. The editor buttons all work and everything looks to be formatted correctly. This post is from the quick reply. If it goes though, it works also.
Looks like I got the rss feed bot back online as well.
It might need to still be kicked every once in a while to get it started again, but that's something Stef has been doing an excellent job at doing. I'm checking for a latest update on it which seems to be posted on a github repo instead of on the actual phpbb site.
Skillz wrote: ↑Sat Nov 11, 2023 6:16 am
Upgraded the feed post bot from 1.0.11 to 1.0.14. Hopefully it doesn't get hung up like the older version did.
W00t! As a test, I re-eanbled the LODA feed which does not respond right now, and the bot does indeed make it through the entire list of feeds now, with just a little delay due to the one unresponsive feed.
The feed post bot has been hanging again since yesterday. It didn't make it through the Rosetta feed (but does now). As feeds can fail in multiple ways, perhaps the bot still chokes on some particular failure modes but not all. Or perhaps there is a difference between manual fetch by an admin and automatic fetch in normal user contexts.
From what I can gather the fetch mechanism is simply a cronjob that issues the fetch command. So I think it's using the same function to run the fetch. The only difference being we push a button to start it while the cronjob is just set to run at intervals checking.
Was really hoping the updated version fixed it. I didn't see a change log for the last 3 versions above our previous version on what was "fixed" or added.
I'm reaching out to the author of the extension. See if he has any ideas on what we can do to make this more automated. I was reading around and their is a way to manually set a cronjob on the host to trigger the fetch instead of using the built in PhpBB cron scheduler. I've asked him about it and will wait to see what he says. If that'll fix the problem, then I'll see what the cronjob actually has to do and write one up to issue it.
Edit
He told me what lines to comment out to prevent it from doing that but warned against possible double posts happening. After I get home from work I'm going to give it a test run and see if it does double post.
When it was stuck, and I 'unstuck' it and triggered a run, that run often created several news posts which we already had. (And I used to delete those one by one then.)
