chrisruggia

It turned out that the wfHoover table in the database had bloated to 400+MB.

This exceeded the size limit on my hosting and INSERT privileges had been suspended for the database user account. Accordingly, the scan would not conclude, I could not upload images to the site, and WordPress auto-updates were broken.

To regain control of the database, I had to manually delete all the wf tables and deactivate Wordfence.

What would cause such a huge table? What does wfHoover do, and how can it be controlled?

The domain is visitalpinetx.com, the wp-admin folder is not password protectd, and there are no other security plugins.

OK, I tried disabling all plugins except WordFence and switching themes to twentyfifteen, and then manually updated to 4.2.1.

Neither affected the stuck scan, still apparently trying to complete itself since April 19.

Anything else I can try? Thanks!

Will do. I’ll probably do it early tomorrow morning, and will report back. Thanks!

No errors showing up in the console.

It could be entirely unrelated, but I did notice that the WordPress latest version checker is not working either. I’m running 4.2 and it’s incorrectly showing as the current version (should be prompting me to upgrade to 4.2.1).

I may manually upgrade and see if that clears anything up…

Thanks Lee, I will try it.

Hello Lee, thanks for replying.

You’re right that the problem is in an interaction between my theme’s code and the plugin, but I haven’t been able to figure out how to correct it.

The issue is that when I require a file in my theme, like so:

require( 'widgets/widgets.php' );

the include path would be relative to my theme, like so:

/serverpath/wp-content/themes/holland/widgets/widgets.php

but when I enable the plugin, the include path is rewritten like so:

/serverpath/wp-content/themes/1/widgets/widgets.php

and my site breaks. When I turn off the plugin, the include path reverts to its original, correct version and the site works again.

I thought I had this fixed, and it’s working in Chrome on my mac, but IE still gives me include errors, like so:

Warning: require(/serverpath/wp-content/themes/1/widgets/widgets.php): failed to open stream: No such file or directory in /serverpath/wp-content/themes/holland/functions.php on line 382

The require() path is not resolving properly with the new version of the plugin and WP 3.6.1. Instead of the “holland” directory, it’s looking for a “1” directory.

It looks like whether I use get_template_directory() or get_stylesheet_directory() the plugin is replacing the theme name with “0” or “1” depending on which theme is selected.

THANKS!

I’d suggest offering a legacy download link for 1.18, at least for a while until PHP 5.4 is more widely adopted by hosts.

That way people (like me) who didn’t notice the 5.4 requirement can more easily step back one version if they don’t have up-to-date backup files. I had updated automatically a few times, so for now I’m using the backup version I had on my machine, which was 1.11.

My client’s site that uses your plugin is at media temple, which only offers 5.3.15 for their (gs) hosting.

You might possibly consider editing the notice in the changelog to be a bit more prominent (maybe something like “WARNING: This version requires PHP 5.4 and will not activate without it!”).

Thanks VERY MUCH for your work providing this plugin. It’s been a great help for my client and their staff.

Thanks, Barry!

I had replaced WordPress’s default jQuery with my own version a while back, and when I updated that, the problem was fixed for me.

I’m getting this error as well. In Chrome’s Inspector, jquery.pjax.js gives me an error that reads:

Uncaught TypeError: Object # <Object> has no method ‘on’

and it kills all javascript after that point. Since The Events Calendar’s js is in the head, that means all my other plugins don’t work.

I haven’t had a chance to see if the error is theme-specific.

Final Update:

Turns out it was not a punctuation problem, but a slug problem.

When I viewed the dashboard page for my taxonomy, I found that ‘river-trips’ apparently had been created, deleted, and created again, because its slug was not ‘river-trips’ but ‘river-trips-2’, causing my code not to work.

Now I’m headed to manually edit the database to try to get rid of any trace of the original slug so my code can work…

But the problem above can be considered resolved.

Update:

The code works when I use a taxonomy terms without hyphens in it.

‘river-trips’ does not work, but ‘directions’ does.

Does anyone know of a problem with punctuation within a taxonomy?

I just realized that when I said “please ignore”, one might have thought I meant the entire topic, and not just the extra post.

I do really need some help, if anyone can offer it. Thanks very much for any suggestions.