JoelSQ_, dovedozen[d] and [tonz] joined the channel
#GWGWhile waiting to write the next webmention PR went back to bookmarks....added a bulk action that allows you to select several bookmarks to turn into a digest post.
#[pfefferle][dshanske] I re-added a simple error handling
#[pfefferle]Can you have a look and fix the WP-handler (and add the tests) in the simple request branch? Or do you prefer a dedicated PR for your change?
jamietanna and [KevinMarks] joined the channel
#GWG[pfefferle]: I will have a look, I might fix but do a separate PR for tests as I originally intended.
pepper joined the channel
#GWG[pfefferle]: The SonarCloud tester found a bug with WP that should be fixed.
[manton], [snarfed], edburns[d], [tw2113_Slack_], angelo, asteria, capjamesg1 and [metbril] joined the channel
#[metbril]I switched hosting providers and since notice that syndication links plugin is not working as expected. When I post a note and publish to twitter with bridgy, nothing happens. When I paste another note without publishing, the earlier note is sent to bridgy, and the backfeed sends a web mention to that post. What could be wrong / out of sync and how to fix this?
jacky joined the channel
#GWGI could ask you to try some troubleshooting techniques
#[metbril][snarfed] correct. I was testing and deleted posts and tweets.
#[metbril]Thing is, that the syndication links plugin sends to bridgy at the next post, and not at immediately when publishing the post. This was working yesterday with my previous host. I copied the database and files to the other host and experiencing issues since. Everything else looks good to me.
[metbril], [James_Van_Dyne], [snarfed], [manton], [tw2113_Slack_] and [jeremycherfas] joined the channel
#GWGIt does it about 5 seconds later, because it uses the publish do_pings hook
#[metbril]@GWG it doesn't unfortunately. I explicitly need to publish another post to trigger bridgy for the previous one.
#[metbril]Yesterday, when I published a post, I could immediately see the syndication link after publishing and then opening the new post from the admin panel.
#[metbril]There's definitely something wrong with the database. I tried with the old copy of the installation on a different domain and a spare twitter account.
#[metbril]I deleted all tables and imported the sql from the backup again. Same issue.
angelo joined the channel
#[metbril]The old environment shows a 5 sec delay as GWG mentioned but the new one has the issue mentioned. Weird. Is there any way I can debug this?
#GWGFew choices...I can add a way to manually trigger it...the only reason publishing wouldn't trigger is a wp-cron issue, I suppose
#GWGA manual check wouldn't help figure out the automatic issue though
#GWGThe way the feature works is...when you click the button, it adds the syndicate-to property to the post meta.
#GWGThen when the do_pings function is triggered, which is on publish, it goes through all posts that have that property and sends the syndication
#GWGThere was a time in the past I switched it to send on publish directly, but it created a problem because of things triggered on publish needing a second to finish first. Webmentions also triggers the same way
#[metbril]Would extending the delay from 5 to 20 seconds help debugging? If you point me to the source line, I could try that myself, first.
#GWGNot really. We had similar problems sometimes with webmentions triggering in the same way. I suppose I could register a cleanup function that ran periodically, but it wouldn't run every few seconds.
#[metbril]I tried changing this line from 5 to 15:
#[metbril]The first post didn't do anything, the second triggered publishing the first immediately (I feel in less than 5 seconds).
#[metbril]I've also tried deleting and re-installing both the Webmention and Syndication Links plugin, no effect.
#GWGIt wouldn't do anything...that line only gets triggered on a retry
#[metbril]I'm still wondering if an export/import from a sql file could have caused this or if this has to do with my new webhoster and/or php settings.
#[metbril]I'm out of options atm. But would gladly receive any suggestions.
#GWGI'll have to think on it. I will put in a manual refresh at the least, but not a long term solution