crdunst

Sorry, just to clarify, I wouldn’t expect you to set up a demonstration just for us – I just would assume you have an example of your plugin working somewhere to take a look at it in action?

I’m sorry, we won’t have the logs or details to help diagnose the issue now; it’s a high traffic site.

We deleted the duplicate orders, and the client is actually in the process of moving to Shopify unfortunately.

I just wanted you to know that there seems to be an issue reported by multiple people, in the spirit of giving helpful feedback. If you hear of other instances, you’ll be aware others have reported it.

Kind regards.

Hi, yes by Ghost feeds, I mean feeds that seem to have created by themselves. Exactly like the first image in this thread. Those feeds seem to be empty as they say ‘Feed not available’, and we didn’t create them, they’ve come from nowhere.

Further, they still seem to be appearing daily, except Tuesdays/Saturdays for some reason, latest one was created today.

By ‘hanging’ I mean the process starts on our original , genuine feed, but doesn’t seem to complete as far as the % displayed goes, so the progress indicator will get stuck at a random number. Checking now, it’s been on 71% since I started this reply. Strangely the feed does seem to generate regardless of the percentage – the feed xml isn’t malformed, and it includes the most recent products.

Without going through the system report I’m not sure if there’s anything sensitive in there, happy to send it to you over email if you let me know the best address to send to.

In terms of debugging, it’s a revenue generating, high traffic site so not possible to toggle plugins/theme on and off. Plus the feed seems to be generating the products, so we’ve not delved deeper.

Thanks.

• This reply was modified 11 months, 2 weeks ago by crdunst.

Just more updates, if that helps you…

I tried to download v3.3.1 from your repo, but when installed, it seems to think that’s v3.3.0. I tried activating anyway, and it gave a WP feedback message that ‘it can’t be activated as it’d give a fatal error’.

Instead, I deleted the copy from your repo, and grabbed a copy of the original plugin from our server backup, from before we updated the plugin yesterday. When re-installing this (which was in fact 3.3.0), I tried activating this, but it re-introduced the error we had in the first place, i.e. the products listing screen isn’t loading (and presumably exhausting memory). It was working before we updated most of the plugins on the site yesterday.

So in summary, your plugin was working. We updated plugins including Woo and your plugin. This started exhausting memory. Rolling back your plugin to the previously working version still didn’t fix the issue.

I’d therefore best guess that the latest Woo version (that we also updated yesterday), isn’t compatible with your plugin from at least 3.3.0 onwards?

Best regards.

• This reply was modified 1 year, 3 months ago by crdunst.
• This reply was modified 1 year, 3 months ago by crdunst.

It was a while ago now, so apologies, but I can’t remember the specifics of your plugin enough to offer feedback. I recall it worked great though straight out of the box.

On a general note, working with all kinds of sites every day, a couple of bug bears with plugins in general:

1) Plugins that add their own top-level menu item in the dashboard, particularly when it’s just their brand name. Worse, when they add to the top nav. Most plugins could comfortably fit their options under ‘settings’ or ‘tools’.

2) Over-styling their front-end. I can usually tell if a plugin is written well or not, by whether they leave their mark-up as vanilla html tags, to pick up theme styling, or whether they add lots of their own styling, requiring lots of overriding on my part with greater and greater css specificity. Some plugins offer a checkbox to apply plugin styling or not, which is fine too.

I’m almost certain your plugin did neither of these things, and it did the job as intended, so no complaints from me. Thanks again for your time developing it.

Hi Ben, our host support came back to confirm there was no record of the firewall blocking access. I tried the onboarding process again, but this time added my own IP to the list of ‘authorised hosts’ during the onboarding, and I was then able to complete and go through to the dashboard.

It looks like it was the plugin blocking me in this case. Now I’m in the full settings, I can see there’s a ‘Automatically Temporarily Authorize Hosts’ option – I don’t remember seeing that during the on-boarding – it might be worth enabling that during the onboarding process?

Either way, this is resolved now, thanks again for your time.