Insert PHP Code Snippet plugin review and common issues

Go to Elegant Themes → Monarch → Configuration → Floating Sidebar. Configure the Mobile settings to hide the floating sidebar on mobile devices — this is the most common solution. Alternatively, set a minimum viewport width below which the sidebar is hidden. Monarch provides responsive visibility settings for each placement type. For mobile, consider enabling the “On Image Hover” or “On Content” placements instead, which integrate more naturally with the content flow on small screens.

Share count retrieval depends on network API availability. Check: (1) Facebook share counts require correct Facebook App credentials — go to Monarch → Social Networks → Facebook and verify the App ID and App Secret are entered; (2) Twitter/X no longer provides public share count APIs — Twitter counts will show as 0; (3) Pinterest share counts may require site verification; (4) share counts are cached — clear Monarch’s cache by deactivating and reactivating the plugin or using the Monarch settings cache clear option; (5) very new posts may have zero legitimate shares — share count display is accurate.

Monarch’s pop-up frequency (show once per X days) uses browser cookies to remember whether the visitor has seen the pop-up. Issues: (1) the visitor is clearing cookies between sessions — the pop-up will appear again after cookie clearing; (2) testing in different browsers or incognito mode resets the cookie; (3) the cookie duration may be set to a very short period — increase it in Monarch → Configuration → Pop-Up → Display Settings; (4) if caching is serving different versions of the page to different visitors, cookie state may not be passed consistently.

In Elegant Themes → Monarch → Configuration → Fly-Ins, create a new Fly-In configuration. Set the trigger to “After Scrolling” and configure the scroll percentage (e.g., 60% — triggers when the reader has scrolled 60% of the post). Select which networks to show, button style, and animation. Configure which content types to display it on (Posts only). Save. The fly-in appears smoothly from the corner of the screen when the configured scroll depth is reached — a non-intrusive sharing prompt for engaged readers.

Monarch provides a Divi sharing module that can be added inside the Divi Builder layout. In the Divi Builder, search the module library for “Monarch Social Sharing” or “Social Sharing” — the module allows placing sharing buttons at any position within the Divi layout. Configure the button style, networks to display, and alignment within the module settings. This approach is more precise than automatic placement and allows sharing buttons to appear between specific content sections rather than only above or below the entire post content.

Yes — Monarch is included in the standard Elegant Themes membership ($89/year for access to all Elegant Themes products including Divi, Extra, Bloom, Monarch, and unlimited site usage). There is no standalone Monarch purchase. The $89/year membership provides excellent value if you are using Divi for multiple sites, as Monarch and Bloom are bundled additions that would cost $50-100/year each as standalone plugins from competitors.

Yes — Monarch is a standalone social sharing plugin that works on any WordPress theme, not just Divi. The native Divi integration (Divi sharing module) is an enhancement, not a requirement. Sites using Astra, GeneratePress, Neve, or any other theme can use Monarch for social sharing. The Elegant Themes membership just requires that you own the membership — Monarch functions independently of which theme is active on the site.

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.