majofa

@trois there is an .htaccess file in the tmp folder.
And one interesting thing: even if I disable the WF cache and delete the /tmp/ folder, in a few second the folder and the file with the malicious code are created again, including the .htaccess file.
I am running gotmls as per @yitwail advice and found some interesting results. The malware scan returned a list of .js files marked as potential threats.
I am reviewing very carefully each one of them and I will post the results.

I want to start this post saying that I think Wordfence plugin is probably the best and most useful plugin I have ever used.

But then, this is the issue I am facing with Wordfence.

My site was hacked right after I enabled the Wordfence Falcon Engine.
After cleaning up the site, it was hacked several more times.
After a long search, I realized that the hacker was using one of the wordpress files for writing the code that steals the site′s information.
The file is: /wp-content/plugins/wordfence/tmp/configCache.php

Initially I deleted the file, but it kept coming back, so I deleted the /tmp/ folder. It came back.
So I proceeded to delete the plugin, manually deleted all Wordfence tables and only then I reinstalled Wordfence. But to my dismay, I found that the malicious code kept being writed to the file as soon as I enabled the plugin.

To this day, I have not been able to locate where the spurious code is nested, so I have to keep Wordfence disabled. A new installation is out of the question as the site has massive amounts of posts and data.

I will very much appreciate any help.

Hi
I have updated to the last version 4.4.5.4 and still can′t get the popup to show.
No rules.

When I apply the addon Test Head Footer, I get the following message:
Your active theme:
Is missing the call to <?php wp_head(); ?> which should appear directly before </head>
Is missing the call to <?php wp_footer(); ?> which should appear directly before </body>

But the calls are present in header.php and footer.php

I was having the same problem as you all.

Finally today I got lucky and found the solution in this blog:

https://www.taqin.net/contact-form-7-file-upload-not-working/

Same problem here: WP 3.3.1

I found a partial solution in
https://forums.lesterchan.net/index.php/topic,4564.0/prev_next,prev.html#new

On line 418 modded to…
wp_schedule_event(time()+$backup_options[‘backup_period’], ‘dbmanager_backup’, ‘dbmanager_cron_backup’);

Line 424 modded to…
wp_schedule_event(time()+$backup_options[‘optimize_period’], ‘dbmanager_optimize’, ‘dbmanager_cron_optimize’);

Line 430 modded to…
wp_schedule_event(time()+$backup_options[‘repair_period’], ‘dbmanager_repair’, ‘dbmanager_cron_repair’);

Now the time displays correctly tomorrow′s date but ……
backup still does not run on the set date.

This excellent plugin has really saved my site from countless attacks (average 2300 attacks per day).

But I am having the same problem: my editors are getting locked out after the second intent to post an entry.

And there are no means to whitelist an ip address. That is what I think is missing.

Other than that, this plugin has been a lifesaver for us.

OK, you are right.
Once disabled Viva Gallery plugin, Easy FancyBox is working like a charm.

Thank you very much.

I have the same problem.

I am using version 2.2 because any other update will not work in my site.

I updated to WordPress 3.1.3 and smooth slider stopped to slide. I shows only one post in the front page -no slide-, although in the administration module I can see the 5 posts sliding normally.

Site: https://linafacr.com

Pro Player 4.7.7 was working perfectly with WP version 2.8.6

I have just updated to WP version 2.9 and now Pro Player is showing an error “This playlist is not a valid XML file”.

You are absolutely right.
I checked Internet Options—>Privacy —>Advanced—>Override automatic cookie handling and now IE8 is displaying the embedded files.
It was not necessary to check Always allow session cookies

Thanks k3davis.
After further investigation, we found that the issue only occurs with IE version 8. All other versions load fine.

It worked perfectly
Thank you very much.

Since upgrade form version 2.0.2 to 2.0.3 and later 2.0.4 I experienced the same problem. I had reported it but have no reply yet.

What I did was revert to version 2.0.2 and that solved the problem for the time being