awardbee

@tim, yes I have got things back up and running, although it wasn’t fun spending a whole day on it! Stupid hackers…

I’m definitely a lot more vigilant now about the plugins I install. It’s sad, since a lot of plugins do such useful things…

Thanks for all your hard work on WordFence, ever since getting my sites back up it’s the first plugin I installed. I didn’t mean to imply in another thread that WordFence doesn’t work well or it isn’t effective, just that installing it after a site is already heavily compromised might be too late, and of course a site might be compromised through another backdoor besides WP

I got hacked too this past weekend. And I installed WordFence as a countermeasure. Unfortunately it was too late. Like you, I noticed that WordFence doesn’t detect .php (and .html) files that aren’t part of the WP core, even if they have names that to a human eye obviously aren’t part of a normal WP install.

If you’ve removed files and they come back, then, you’re in trouble. They might be deep in your database, or they might have a backdoor still open to your site that will render your cleaning attempts useless.

No matter what you do please heed this warning: BACK UP YOUR POSTS NOW!!! Go to “Tools -> Export” and export everything. Take screen shots of your site, your WP dashboard and your plugins in case you need to reconstruct everything from scratch.

You never know when your site could be taken down completely, or shut down by your host because your hackers have turned your site into a brute force bot.

I had back-ups done through my host (Digital Ocean) they saved my behind. Do not rely on WordFence to protect your site any further – if files come back after you’ve cleaned them and WordFence isn’t detecting them, your site is compromised beyond easy repair.

Hi there Tim! I did do all the steps in the guide. I had Wordfence clean out both WordPress blogs that I run, both of which were hacked. ??

I think they must have a backdoor or something, and maybe it’s interfering with Wordfence being able to detect malicious files.

Last night my server was apparently used for a brute force attack! And my server has since been shut down. I’m working now to try and migrate my files out (the one step I didn’t follow in the guide was backing up!) and fire up a new server, this time more secure!

Thanks for your help. I think maybe by the time I had Wordfence installed it was too late, my site was too compromised.

(no content, just marking thread resolved)

Just a follow-up: I reinstalled WordPress 4.0 on my server and now everything works fine. Something must have gotten corrupted in how pictures were being rendered because it affected only the featured image and parallax galleries.

Thanks again for your help Nick and Michael! You guys make an awesome plugin!! I guess if I ever have a mysterious problem in the future, just reinstall WordPress haha.

@nick and Michael, OK touche must be a problem w/ my server or theme then. Thanks for your guys’ help!

@chris, OK will check to make sure it’s not a problem w/ my server or wordpress install first and will ping you guys. thanks!

Reverting to Aesop 1.1 didn’t help the parallax gallery issue.

I downloaded your guys’ quick fox for the lightbox issue and can confirm that grid gallery lightbox works now!!

@michael, the thing is I’ve had the same parallax problem in the twentyfourteen theme. Also Worldview by Upthemes is “aesop compatible” out of the box, whatever that means ?? It only started happening yesterday. I’m thinking I’ll try rolling back to the previous version of Aesop and see if it’s still a problem.

Here’s an example of the stacked parallax issue:

https://awardbee.com/?p=835&shareadraft=baba835_543d85ae34354

I just made a test post and only put a stacked parallax gallery in it.