WPCodeBox plugin review and common issues

Twitter/X significantly restricted its API in 2023, requiring paid API subscriptions for most use cases. Check: (1) your Twitter/X developer app plan — the free API tier is extremely limited; posting to Twitter requires at least a Basic paid API tier ($100/month) unless you qualify for certain exemptions; (2) the API credentials in Revive Old Posts → Settings → Social Accounts → Twitter must match an active Twitter/X App; (3) verify the API app has “Read and Write” permissions — “Read only” apps cannot post tweets; (4) check the Revive Old Posts → Log for specific API error codes.

Configure exclusion rules in Revive Old Posts → Settings → Sharing: (1) set a “Maximum post age” to prevent sharing posts older than a threshold (e.g., 5 years); (2) use the “Exclude categories” setting to skip categories like “News,” “Announcements,” or “Events” that contain time-sensitive content; (3) exclude specific posts individually by adding them to the exclusion list in their post meta (Revive Old Posts adds a checkbox in the post editor to exclude that specific post); (4) set a minimum age (e.g., at least 30 days old) to prevent recently published posts from entering the recycling rotation.

Revive Old Posts uses WordPress cron for scheduling. Issues: (1) WordPress cron requires site traffic to trigger — on low-traffic sites, scheduled sharing may run late. Set up a true server cron (via hosting control panel) to trigger wp-cron.php every few minutes; (2) go to Revive Old Posts → Log and check if the cron job is registering at all; (3) a caching plugin may be blocking the cron trigger; (4) verify the sharing interval is not set too long (a 24-hour interval with few qualifying posts may not trigger visible sharing); (5) confirm the social account connection is still valid — expired OAuth tokens prevent sharing.

In Revive Old Posts → Settings → Post Format → Categories, select “Include only selected categories” and check the categories you want to recycle. Only posts in those selected categories will be shared. This is useful for blogs with mixed content (tutorials, opinions, news) where only the evergreen tutorial category should be recycled, while opinion pieces and news are too time-sensitive for recycling.

UTM parameter tracking requires Revive Old Posts Pro. Go to Pro → Settings → UTM Tracking and enable UTM parameters. Configure: utm_source (e.g., twitter, facebook), utm_medium (e.g., social), utm_campaign (e.g., revive_old_posts). When configured, every shared link includes these UTM parameters. In Google Analytics, filter traffic by utm_campaign=revive_old_posts to see how much traffic is being generated from recycled older content sharing.

Effectiveness depends heavily on social media audience engagement and platform algorithm treatment of automated posts. Sites with engaged Twitter/X or LinkedIn followings see meaningful traffic from recycled content. Instagram and Facebook typically require authentic, manually crafted posts for engagement — automated recycled posts perform less well. For content sites with large Twitter followings, Revive Old Posts can add 5-15% to social referral traffic from older content at minimal effort. Measure ROI by enabling UTM tracking (Pro) and comparing traffic in Google Analytics before and after.

Revive Old Posts tracks which posts have been shared and, by default, waits until all eligible posts have been shared at least once before resharing the same post (complete cycle). You can configure a minimum interval between shares of the same post and whether posts can be reshared after a waiting period. For evergreen content, resharing on a 30-60 day cycle keeps it visible to followers who may have missed it originally.

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.