Header Footer Code Manager plugin review and common issues

Instagram’s API has strict requirements for automated posting: (1) only Business or Creator Instagram accounts can use the API for direct posting — personal accounts cannot; (2) Instagram requires posts to contain an image — text-only posts are not supported via the API; (3) the connected Facebook Business Page must have the correct permissions to the Instagram account; (4) video posts have additional format requirements (MP4, specific dimensions, duration limits); (5) verify the Blog2Social → Accounts → Instagram connection is current — Instagram’s OAuth tokens expire and require reconnection.

Duplicate posts occur when: (1) the WordPress post was saved as a draft multiple times triggering multiple Blog2Social scheduling events; (2) the auto-post setting is enabled and the post was published, unpublished, and republished — each publish triggers a new social post; (3) a scheduled post and a manual share both went live; configure Blog2Social → Settings → Auto-Post to trigger only on the first publication (not on updates). Also check the Blog2Social scheduling queue for duplicate entries and delete them before they publish.

Blog2Social uses WordPress cron for schedule execution. Verify: (1) WordPress cron is running reliably — set up a true server cron to trigger wp-cron.php every 5 minutes for reliable scheduled posting; (2) in Blog2Social → Posts → Scheduled, verify the posts are queued with their intended publish times; (3) check Blog2Social → Posts → History for posts that show as published — compare actual publish time vs scheduled time to see if cron timing is the issue; (4) server time zone must match the expected local time for scheduling to work as intended.

After clicking “Auto-Post” or “Schedule” in the WordPress post editor, Blog2Social opens a preview/customization screen showing the generated social post for each connected platform. Click on any platform to edit that platform’s specific content: change the headline, edit the post text, add or remove hashtags, select a different image, and adjust the scheduling time. Each platform’s post is independently customizable. This pre-publish review step is Blog2Social’s key differentiator over fully automated tools that post without review.

In Blog2Social → Posts → Content Recycling, configure a recycling campaign: select the category/categories to include, the post age range (published between X months and Y months ago), the scheduling frequency (share one post per day, every 3 days, etc.), and the social networks to post to. Blog2Social generates a queue of older posts scheduled for future sharing. Review the queue and adjust individual posts’ content or timing before the campaign runs.

Blog2Social has tighter WordPress integration — it generates social posts directly from WordPress content with automatic image pulling and content formatting. Buffer and Hootsuite are platform-agnostic social media managers that require manually creating each social post or RSS-based auto-posting. For WordPress-centric content teams that primarily share their own WordPress posts, Blog2Social’s automatic content formatting and WordPress admin integration streamline the workflow. For teams managing multiple brands, diverse content types, or client accounts, Buffer and Hootsuite’s broader social media management features are more comprehensive.

Blog2Social supports standard WordPress posts, pages, and custom post types. Configure which post types trigger auto-posting in Blog2Social → Settings → Post Types. WooCommerce products, portfolio items, and other custom post types can be auto-shared if their content (title, featured image, description) is appropriate for social sharing. Some custom post types without featured images or with structured data that doesn’t translate well to social posts may need manual social sharing.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.