reidbusi

I fixed it myself for now. But note there is a bug in the WP 4.3 code: when you cancel a password change, wordpress still updates the password with the generated password. I don’t have the time to submit a bug report.

One of the sites I have the plugin installed on was reporting 404 exploits where there was none. It was blocking access to a page that actually was there. But only that one page. I could find nothing unique about it. I disabled the 404 exploit checking on that site.

Would you be willing to hand over the plugin to be maintained by a shop with the staff and time to do it?

Would it make a difference if someone paid you to do it? I need this now.

That is what one would expect, however, it uses jquery clone (which should bring the event listeners as well) but…

Divi/js/custom.js:2420

$this_menu.on( 'click', 'a', function(event){
		event.stopPropagation();
	} );

Their menu code overrides the popup listeners.

So fo now what I did was modify their js to not copy the seconday menu to the main mobile menu and added some custom css to not hide the secondary menu at the mobile media query breakpoints.

Thanks for the reply though!

Is there any chance of this happening?

P.S. A throttle on the preload would be awesome too!

That’s great! Thanks! ??

Version 4.0.30

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.

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

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.

Tried clearing all transients, got same result.

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)

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?

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?