robmaric

I have had Claude Opus 4.6 Thinking analyse the plugin and it found the issue. Here’s a summary of why it happens and how it fixed it for me:

The issue: The “Exclusive offer – 60% off!” discount notice in your Instagram Feed plugin keeps reappearing after clicking “I’m not interested.” This happens because the dismissal is saved per-user in wp_usermeta, but the notice itself is stored in a shared site-wide option (sb_instagram_feed_notices). On a site with multiple admins, any admin who hasn’t dismissed the notice will re-add it to the shared option when they load any admin page — causing it to reappear for admins who already dismissed it. The display logic (SBNotices::display_notices()) never checks the per-user dismissal state before rendering.

How it was resolved: The dismissal flag (sbi_ignore_new_user_sale_notice = 'always') was set in the database for all admin users, and the stale notice entry was removed from the shared option. This replicates what the plugin does when a user clicks “I’m not interested,” just applied to all admins at once so no one can re-trigger the cycle.

Never mind! I see the issue is not your plugin but instead the theme style adding a margin. Fixed.

Thanks so much for the fast reply Krystian

I just did two things now – I updated WooCommerce itself (hadn’t updated it for a few weeks at least) and also turned on the new UI in the paypal payments plugin. Now the red PayPal error is gone. Phew!

Hi Shameem, Thank you so much for your thorough reply. I am grateful for your excellent support. I have given your plugin a 5 star review. Orders not syncing into ShipStation can be a massive headache for small businesses who need things to ‘just work’ so they can dispatch their orders! Thank you so much for taking a close look at the issue.

Great to hear! Thanks.

Thanks Maya for the fast reply! We will consider the premium plugin.

Sorry you asked me to do that the first time – oops.

// ERROR: The file /home/mywebsite/webapps/mywebsite/wp-content/cache/tmpWpfc does not exist, it must have already been deleted.

Ok it’s my cache that’s the problem. I’m using WP Fastest Cache. I know you require us to turn off Litespeed (I’ve seen that warning on Litespeed sites) so I guess this must be the same issue. I turned off WP Fastest Cache and tried again and it worked.

WP Fastest Cache doesn’t integrate with any server level technology here, like Litespeed would. I’m just using it at the PHP level. So maybe there’s a way around this issue rather than turning caching off for that long? i.e. Whitelist a particular URL? If not, no huge deal, I can deal with it as I don’t scan that often.

• This reply was modified 9 months, 2 weeks ago by robmaric.