gordonium

Hey Oliver, thanks for the speedy response and follow-thru connecting with Woo! Great support. Well done.

Thanks for the update Morgan! It appears the system is unable to connect our email to an account and thus we can’t send logins for troubleshooting. Please feel free to contact us directly with another way to give you that access.

Agreed. The export by category doesn’t appear to be working for us either (although it has in the past). There’s another support ticket open for this.

I concur. We’ve used this for years and it appears it’s no longer sorting by category for exports (which is a problem that locks up our server with over 8k products). We’re running into the same bulk issue problem as well.

Please let us know when the category sort export is working again. Happy to give you access to our staging environment if that would be helpful for troubleshooting.

I have verified it doesn’t appear to be another plugin conflict – see other open support ticket.

I second this. I can see it loads for a split second and then disappears.

Same issue, same circumstances. Upgraded to PHP7, triggers fatal error: Uncaught Error: Class ‘SimpleShareButtonsAdder\Simple_Share_Buttons_Adder’ not found.

Hurray for staging areas!

Thanks for the follow up! Quick too.

I totally understand and appreciate that plugins are always evolving and bugs happen.

I understand how multisite table structure works, which is why my experience perplexed me. We activated the plugin on a single site on the network (ID #124). Thus I would expect the plugin to create its 8 tables as wp_124_table1, wp_124_table2, wp_124_table3, etc. Right?

What I saw happen was a create of a whole PILE of tables as wp_124_1_table1, wp_124_1_table2, wp_124_1_table3 (all 8), then onto wp_124_2_table1, wp_124_2_table2, wp_124_2_table3, and so on for *every site on the network* yet all nested beneath the 124 ID. Thus for our 120+/- site network, by activating the plugin on one site, 960 tables were created. Yow!

I imagine this is not what you intended. We had long-since deactivated and deleted the plugin (it just didn’t do *exactly* what we were looking for – totally unrelated to this issue), and the tables were left behind – presumably because they were created by a bug and your clean-up code didn’t know how to find them; again, totally understandable.

Unfortunately this happened months ago and I only just identified it in the database during routine housekeeping and cleaned it up. I wish I had better diagnostic information for you. Is there anything I can do to help the “bug hunt” at this point?

I did not. I ended up just not using SU inside ALM

Take a hike wpgrowth.

I’d like this feature also… any suggestions?

Thanks for your input. This is more of a pipe dream item for me, so I don’t know when I might break ground. In any case, I’ll keep you posted!

I was just thinking about writing a tool like this. Do you still need it? Can you give me an idea of the feature you’d be looking for?