davidmcc3

I’ve also had it reported (by a client) that they’ve started to get lots of spam.

What can we do?

Hi Oleg

That has worked.

Is there a way of preventing this cookie being created or having it updated? Like the items per page options, clicking the grid or list button on the product pages doesn’t change the display … so I assume it isn’t updating the cookie?

There are many non-tech customers who won’t be able to work out how to get round this.

Regards, David

I may have the answer … there may have been a conflict in Simple:Press where it was set to: “Use the Simple:Press new user email version”

Don’t know why this should cause an issue. Any ideas on that?

Hi Mike
This is work on the development site, so nothing (important) will get broken!
Thanks for your help – I’ll mark this as resolved.
Regards, David

Hi
Just gone back to Plexus LLC site (after just a couple of hours) and they’ve updated their support level to Woo 2.6
Thanks,
David

Hi Mike
Haven’t checked them all, but def. Inventory Manager and Inventory Notifier from Plexus LLC.
David

Hi Mike

I guess that’s fine, so long as there’s nothing I’ll miss or that causes other issues if I’m staying with 2.4.2.

Looking through the change log (rather quickly), I noticed support for Subscriptions 2 being added (have 2.0.12 installed, though not selling subscriptions in Woo), and support for WP4.4 (running 4.4.2)

Thanks for the quick response.
Regards, David

Brilliant deduction, Sterndata!

There was plenty of space previously when I ran the last update, but the client had added some huge image files and used quite a bit of the remaining space in his account.

Changed the space allocation, and the update ran without a hitch.

Many thanks.

Hi Matt

Yes … plugins deleted … a good point to make.

Best regards, David

A quick update.

Found two plugins (both required) to edit the wp-config from withjin WordPress (yes, I know it’s dangerous) – ‘CSS & JavaScript Toolbox’ and ‘WP Core Editor’.

Commented out the init.php loader line, and then deleted the file (from within WordFence) … site still working, and WordFence reports no problems.

All done.

Thanks again for the help.

Hi Matt (?)
The hosting account is on quite an old package which doesn’t have ftp access or a control panel (I’m used to cPanel etc. on my hosting).
I imagine it can be upgraded, but it might cost my friend (whose site this is).
This is the trouble with doing favours!
I’ve taken a backup with duplicator and installed it on my hosting. As you suspected, init.php is called from wp-config. It also calls wp-settings in the next line.
I’ve commented out the line calling init.php – no effect on site (good news!). I’ve then renamed init.php to bin-it.php … site is still fine.
I’ll have to ask the hosting company to edit the file and then remove the bad one.
Thank you very much for your prompt help – much appreciated.
I’ll be recommending my friend gets a premium WordFence license. We have a block, but I didn’t want to give him one of mine!

Thanks for the info … I’ll get on with the testing.

Hi again

I’ve gone back and installed a previous copy of the site and updated WP to 4.1.1, but haven’t updated the theme or plugins.

I can now create the user and enter a password.

The strength indicator tells me I used a ‘bad password’ it was a 5-letter word plus three numbers plus a non-alpha/numeric character.

Is there any documentation on what’s considered good/bad by the plugin?

Thanks.

Hi – thanks for the response.

Sorry … meant that as soon as the first character is entered in the first password field, the button is greyed out, and then nothing changes that.

I’ve tried simple and complex passwords (making sure the same was entered in both boxes), but the button never becomes clickable again.

I’ll try disabling other plugins and changing the theme later and report back.

Hi David

Followed the link … seems it was closed off 14 months ago … I’ve no idea if they’re still working on it, or where to look to find out.

There was a link back to another ticket opened 4 years ago! Personally, I wished they’d fix things like this instead of keep updating the interface.

I’ll have a look through all the plugins to see which are loading language files so I can exclude them all from backups etc.

Many thanks, David.