WPIntell

Source evidence

started causing issues

Blog2Social: Social Media Auto Post & Scheduler · support · 2025-06-30T16:14:00+00:00

Blog2Social: Social Media Auto Post & Scheduler plugin evidence original source source API
mixedsentiment
mediumseverity
0.85relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 26 rows with source links

23.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

20 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
extremeleadprogramcom resolved
I’ve been using this for years with no problems. Recently I deleted a TON of posts (I’m not sure if this is related). But recently started having issues. There are lots of database connections and the site was slow. Deactivated this plugin and it’s fixed… nothing else new on the site for years. How can I cleanup the DB to see if that’s the issue or what else can I do to try and fix this? The page I need help with: [ log in to see the link] Hello, Thanks for reaching out. Is it possible that your website does not meet the system requirements of Blog2Social ? We can assure you that Blog2Social works properly on over 70,000 websites worldwide and generally does not slow down websites. However, you could try the following steps: 1) Activating the “ Legacy mode ” in your Blog2Social settings. 2) Unticking the box “ Add Open Graph Image Data ” (Settings -> Social Meta Data). Additionally, you might consider increasing your website’s memory limit to 512M and your execution time to 400. Of course, you can also delete database entries. We’ve attached a screenshot of the Blog2Social database tables for you: https://prnt.sc/MNP2Pop4gsB4 Feel free to let us know if this resolved your request or if you have any further questions. Thanks for the reply. I turned on a “Throttle Heartbeat API” feature in another plugin. That seemed to cause the conflict/issue. I turned that back off and now all seems fine again! Thank you for your feedback. Could you tell us which plugin triggered this behaviour on your website? The plugin was FlyingPress. However, it only happened when I turned on the “Throttle Heartbeat API” feature.

Comments

4 shown
Blog2Social-Support 2025-07-01T07:24:00+00:00

Hello, Thanks for reaching out. Is it possible that your website does not meet the system requirements of Blog2Social ? We can assure you that Blog2Social works properly on over 70,000 websites worldwide and generally does not slow down websites. However, you could try the following steps: 1) Activating the “ Legacy mode ” in your Blog2Social settings. 2) Unticking the box “ Add Open Graph Image Data ” (Settings -> Social Meta Data). Additionally, you might consider increasing your website’s memory limit to 512M and your execution time to 400. Of course, you can also delete database entries. We’ve attached a screenshot of the Blog2Social database tables for you: https://prnt.sc/MNP2Pop4gsB4 Feel free to let us know if this resolved your request or if you have any further questions.

extremeleadprogramcom 2025-07-01T14:54:00+00:00

Thanks for the reply. I turned on a “Throttle Heartbeat API” feature in another plugin. That seemed to cause the conflict/issue. I turned that back off and now all seems fine again!

Blog2Social-Support 2025-07-02T06:55:00+00:00

Thank you for your feedback. Could you tell us which plugin triggered this behaviour on your website?

extremeleadprogramcom 2025-07-02T12:27:00+00:00

The plugin was FlyingPress. However, it only happened when I turned on the “Throttle Heartbeat API” feature.