PublishPress Authors plugin review and common issues

Share count retrieval depends on API access from each platform. Issues: (1) Facebook share count requires a Facebook App configured in Social Warfare → Settings → Social Identity — without App credentials, Facebook counts show as 0; (2) Twitter/X removed public share count API access — Twitter counts now show as 0 for all plugins; (3) Pinterest share counts require correct API configuration; (4) share counts are cached — Social Warfare may be showing cached (old) counts — clear the share count cache in Social Warfare → Settings → Advanced; (5) the post URL must exactly match the URL that was shared (no trailing slash differences).

Check: (1) Social Warfare → Settings → Display → Post Types — verify the button is enabled for the post type of the page you are viewing; (2) per-post override — in the post editor, check the Social Warfare panel for any “do not display” setting; (3) a JavaScript error from another plugin may prevent Social Warfare initialization — check browser DevTools Console; (4) theme conflicts — some themes include their own social sharing that may conflict; (5) clear all caches after changes to Social Warfare settings.

Go to the Social Warfare panel in the post editor. Under the “OG & Twitter Card” section, manually set the Social Warfare image (the image that social networks will use for previews). This overrides whatever image the social network’s crawler might select automatically. For Pinterest specifically, Social Warfare Pro’s Pinterest Image feature allows selecting a dedicated Pinterest-optimized image (typically taller aspect ratio) that differs from the Facebook or Twitter preview image. After updating, use the Facebook Debugger (developers.facebook.com/tools/debug/) to force a cache refresh.

In the WordPress editor, use the Social Warfare Click to Tweet button (a social warfare icon in the classic editor toolbar, or a block in Gutenberg). Enter the quote text and an optional custom tweet text. The plugin renders a styled highlighted quote box within the post with a Twitter/X share button. Readers who click it open a pre-populated tweet with the quote text. Strategically place Click to Tweet boxes around key statistics, insights, or quotable sentences in long-form content to create multiple sharing opportunities within a single post.

In the post editor, scroll to the Social Warfare panel (below the editor). Find the OG & Twitter Card section. Set: OG Title (the title that appears in social shares — can differ from the SEO title and the post title), OG Description (the text snippet shown in the social preview card), and OG Image (the image that appears in social previews). Save the post. Social Warfare outputs these as Open Graph meta tags in the page header, controlling how the post appears when shared on Facebook, LinkedIn, and other OG-compatible platforms.

AddToAny is completely free with a wider platform selection in the free version. Social Warfare has higher-quality button design and superior Pinterest image control (Pro). For most content sites prioritizing clean sharing buttons and basic OG control, Social Warfare free is comparable to AddToAny. For bloggers where Pinterest traffic is significant and who need share count social proof, Social Warfare Pro’s Pinterest-specific features are differentiated. For sites that just want working share buttons across many platforms at zero cost, AddToAny is the pragmatic choice.

Social Warfare renders buttons without requiring external JavaScript libraries to load on every page — the core button rendering is CSS-based. Share count retrieval is handled asynchronously after page load using cached values. This architecture makes Social Warfare one of the lighter-loading social sharing plugins. Share count API calls are cached and serve cached values to visitors, preventing real-time API calls on every page view.

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.