njwp

Thanks. I’m doing a job for a foreign client with foreign hosting so I’m not even going to attempt communication with hoster ??

Could be something to do with using a temporary (host supplied) URL or a resource issue. Really not a problem for me to disable cron when I need to.

The reason I thought of doing it is when the duplicator job got stuck I went to see if I could see any error messages in host cpanel and cron was running every 2 seconds, so it seemed like a good idea to try disabling it. I think it was the duplicator job that was kicking off the cron, because when I cancelled the duplicator job, cron did go back to normal frequency

Same problem here

Windows 10
running WampServer 3.1.2
PHP 7.0.23
Apache 2.4.29

Only started happening after upgrade to WordPress 4.9.7

great – perfect solution, Thanks for the quick response.

Thanks for the reply.

When you say extensions – I assume you mean extensions for Popup Maker?
I don’t have any of those extensions installed.

Looking at your code, in:
easy-modal-v2.php

you have:
function popmake_emodal_init()
with this line
add_filter( 'popmake_get_the_popup_data_attr', 'popmake_emodal_get_the_popup_data_attr', 10, 2 );

and you are initialising that function:

add_action( 'init', 'popmake_emodal_init' );

It looks as though this should only trigger if you have the ‘Enable Easy Modal v2 Compatibility Mode ‘ option checked in settings.

I don’t have that option checked, so that shouldn’t be firing – but maybe it is?

I have done a search through my whole plugin codebase, and that is the only place in your code calling that function that I can see.

• This reply was modified 6 years, 5 months ago by njwp.
• This reply was modified 6 years, 5 months ago by njwp.

check what you have set up under ‘Targetting’.

I had the same problem – the popup would only open on menu click if it was already on that page and then I realised I had set the Targetting to ONLY enable the pop-up on that page.

Once I removed the Targetting condition, it worked correctly.

• This reply was modified 6 years, 5 months ago by njwp.

Jordy – you are so spot on. Your plugin is great. I came here to give you a review and get confronted by this idiot review.

Your reply is classic – thanks!

@wpsolutions

Yes this was my conclusion, but a lot of people are going to be Googling this as windows defender will be on a LOT of PCs so best to get an answer out there

@duongcuong96
Thanks for the solution.

I disabled: pdo_mysql and mysqli
and enabled: nd_pdo_mysql and nd_mysqli

BackWPup now runs correctly.

My site is not live as it is still in the setup phase. I certainly wouldn’t be happy making this sort of change on a live site, as I have no knowledge of the difference in those PHP extensions and would assume a hoster configures a site in the best way.

@duongcuong96
Thanks for the follow up.
My hoster has upgraded to the 10.2.13 version of MariaDB but the memory issue is still there when trying to run a DB backup

same issue here
DB: 10.2.12-MariaDB

tried to allocate: 1701601920 bytes

brand new install so nothing in the database yet other than default install data, so no way should need that amount of memory

• This reply was modified 6 years, 10 months ago by njwp.

Same problem here.

It was becuase I already had a website and was trying to install wordpress into a subdirectory.

The .htaccess from the main site was interfering with the install

I added:

RewriteCond %{REQUEST_URI} !^/sub-dir/ [NC]

before my rewrite rules in the main site .htaccess where ‘sub-dir’ was the subdirectory I was installing wordpress into.

It worked then

perfect – thank you so much. It now works with BackWPup, which makes it so much more convenient.

Will this also fix the incompatibility with the BackWPup plugin which is also a backup plugin that won’t run when maintenance mode is enabled?
It seems what is happening is that when it tries to run wp-cron.php it gets the maintenance page
Thanks

Hi Miles – try the previous version 1.0.11

yes I have the same problem