Product export results in empty csv labelled "subscribers_…"

Eliminated Subscribe2 plugin as cause (deleted it with data). Still get the same result.

Actually, deleting the Subscribe2 plugin still left its table in the db, the feilds of which are the headings of the empty csv I’m getting.

dropped the _csp3_subscribers table, still get the same result. I suspect I have to cleanup the mess the Subscribe2 plugin made of the snafu that is the WP taxonomy tables…

Also, defining:
define( ‘WOO_CE_DEBUG’, true);
in the plugin seems to have no effect.

Has this plugin been tested on an SSL only site?

Hi reidbusi, WOO_CE_DEBUG will turn off the export file generator and instead print the CSV file to the browser. I’ve not played with Subscribe2 so will need to reproduce this locally. Do you get a CSV file download or just an empty screen? Any information you can provide to reproduce this would be great, alternatively you can contact me at [email protected] to look at this further with you ??

Defining the debug define has no effect for me, I still get a csv file download.

I have turned it back off and am no looking at defining define(‘WP_DEBUG’, true); in wp-config.php to see if it will give me any info.

When I try to export products I get a csv file named ‘subscribers_2014-12-18_14-52.csv’ that contains:
ID,Email,Fname,Lname,Clicks,Conversions,City,Country,IP,Created,Referrer
and nothing else.

I get the same result if I try to export categories or tags, I have not tried users yet, but expect the same.

The feilds in the csv are the same feilds that were in the Subscribe2 plugin table:
CREATE TABLE IF NOT EXISTSwp_csp3_subscribers` (
id int(11) unsigned NOT NULL AUTO_INCREMENT,
email varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL,
fname varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL,
lname varchar(100) COLLATE utf8_unicode_ci DEFAULT NULL,
clicks int(11) NOT NULL DEFAULT ‘0’,
conversions int(11) NOT NULL DEFAULT ‘0’,
referrer int(11) NOT NULL DEFAULT ‘0’,
ip varchar(40) COLLATE utf8_unicode_ci DEFAULT NULL,
created timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (id)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ;`

I originally had the Subscribe2 plugin deeactivated when I started trying to export, when I got these results I deleted it, and still got the same results, then I dropped its table from the db, and I still get the same results.

Using WP Super Cache, and cleaning the cache before every attempt.

So it looks to me that that Subscribe2 plugin has corrupted the database somehow…

Though it just occurs to me to check what your plugin has stored in the db, perhaps it has picked this up and stored it somewhere and will not let go.

I also suspect confusion in the code with Woo Subscribers plugin?

Aha… when I try to export with define(‘WP_DEBUG’, true); set in wp-config.php I get”

Notice: Use of undefined constant E_DEPRECATED - assumed 'E_DEPRECATED' in /home/###acct###/public_html/wp-content/plugins/minimum-purchase-for-woocommerce/woo-integration/vtmin-parent-definitions.php on line 27
WordPress database error: [Table '###acct###_wp.wp_csp3_subscribers' doesn't exist]
SELECT * FROM wp_csp3_subscribers

ID,Email,Fname,Lname,Clicks,Conversions,City,Country,IP,Created,Referrer

But no hint as to who/what is still trying to query that non existent table. This leads me to believe that perhaps you plugin has stored it somewhere, confusing it for the Woo Subscribers plugin (even though this is the free version of your plugin which does not support that anyway)

Hi reidbusi, I have a feeling the $_POST[‘action’] that we detect is being used by another WordPress Plugin and you’re seeing that Plugin’s export. If you’re using WooCommerce Subscriptions Exporter then that’s the reason, disabling their Plugin resolves this

I’ve made a note to add a check that it is our Plugin requesting an export this will reduce the chance of similar conflicts

Tried clearing all transients, got same result.

Nope, not using WooCommerce Subscriptions Exporter. So that’s not it.

I will search the site code for instances of the $_POST[‘action’] that your plugin uses to see if there are any conflicts.

We don’t do any queries to that table so it’s another Plugin, downloading a local copy of all activated Plugins then searching the files for that subscribers table will turn up the suspect.

Roger, doing so now… (thanks for the help! :))

Culprit identified: SeedProd Coming Soon Pro

Export now working with it deactivated.

Kind of embarrassed I did not think to just search the site code for that table name as you suggested.

Turns out it was not Subscribe2 after all…

Thanks again for your most helpful help! ??

I shall go gently inform SeedProd now.

Awesome, happy to help, and please do ??

Sorry I’ll get a patch out ASAP!