SWalberg

Andrew, you’re using a strawman. No one is arguing for putting everyone’s issues in the same thread.

What we had earlier was someone that provided a problem along with instructions for reproduction. Someone followed on and said “I did that, saw the same problem, and also tried this too.” As a software developer I look at that and say “awesome! I wish more people would do that!”.

The gist of the better thought out posts above is “that may be true, but in most cases the people that post here are one level above asking where the ‘any’ key is so we’ve found it best to assume we’ll need to start from ‘is it powered on?’ and take every question on its own”.

Most of the arguments made in here seem to stem from this assumption that anyone that posts here is clueless. That’s fine, and if it means that the forums run more smoothly then more power to you. But as you’ve seen you’re alienating the more technical members.

Sean

I can appreciate your points, Jan and esmi. It seems the crowd of people that come here for help is different than what I’m used to and require different ways of dealing with them.

I don’t think there’s any disagreement as to what the forum guidelines say. A cursory reading of the post indicates that the OP is looking to have a discussion about the appropriateness of the rule.

One only need to look outside the PHP/WordPress world to see examples of this. It’s quite popular for people to add “this affects me too” or even just a thumbs up emoji over on GitHub issues. People also use the same thread to share their solutions. Rather than having a dozen calls for help, one with a solution, we now have one place with a dozen confirmations and a solution. And the maintainer knows what the biggest problems are.

If you go to StackOverflow and ask a question that’s already been asked, you’ll get shut down pretty quickly as a duplicate and told to post in the original thread.

I realize the technical bar is set a bit lower in the WordPress world as a result of the “Design for the Majority” philosophy and as a result, non technical people often mistake other people’s problems for their own. However there must be something between a regimented “Always make your own post” and “all pile on one thread”.

The links are in the page, you can view the source to find them. There’s some CSS that hides it which isn’t going to get loaded when Facebook does the preview. https://www.isithacked.com/check/http%3A%2F%2Fwrongfairway.com%2F shows the links.

You’ll want to go through the set of links that were posted earlier to clean up your site.

kmessinger, there are definitely some funny links on the site. See https://www.isithacked.com/check/http%3A%2F%2Fnurturinghealingtouch.com%2F

There is a block of text injected along with some JavaScript to hide it.

Go to Settings -> General, and look to see if you have “anyone can register” checked and if the new user default role is “contributor”.

It takes a while for Google to add you to their list, and I’ve even watched an infected site go on and off the list over the course of a few months without any changes from the site.

I’d love it if you sent me the files (sean at ertw dot com), or posted them to pastebin so I could look into them. Sometimes these kinds of malware post genuine links for SEO juice, or sit around waiting for instructions. It’s hard to know.

Just for kicks, could you see if your site triggers anything at https://isithacked.com ?

Thanks,

Sean

Copied the sql to https://gist.github.com/swalberg/7696138

I’m not a cPanel user, but there should be some way of blocking just that IP address from accessing your site.

cPanel -> IP Deny Manager is what Google tells me, YYMV though.

Check your logs for requests from that address (76.164.208.163). I’m not sure I’m reading the output correctly but it’s possible that host is hammering your site trying to spam you.

Even if WordPress’ usage for a single request is low, lots of requests at the same time will use much more resources.

Your website is responding with a 200 status code meaning “yea, this page is ok”. So “luckynbr.com/blahblahblah” is a valid page on your site.

At the same time https://www.luckyshotpics.com has a url structure similar to what you’re seeing. So my guess is that you link to that site somewhere and goofed up the url, or someone else linked to your site and goofed up the page somehow. Now robots and people are following it. Since that other site is an image site it also could be an image tag, so people aren’t even actively clicking on it, they’re just viewing the page that links to it.

You can’t do much about how people come into your site so I wouldn’t worry about it. If your logs show the referring site you might be able to get them to fix it, or you can search your own site to see if you’re the culprit.

The “anything is a valid page” is not a great position to be in. That might be part of your theme, it might be in the .htaccess file.

BTW “all” isn’t a valid value for the display property. See https://developer.mozilla.org/en-US/docs/Web/CSS/display

Sorry, I’m not going to be much more help here. They seem to do it in the linked jsfiddle but I just gave it a shot with the chrome inspector and couldn’t reproduce it on your page.

Stuff like this isn’t my strength, I had hoped that the link would have pointed you in the wrong direction.

Maybe browse around Stack Overflow a bit more and someone will have a better solution.

Hi Viensia,

Upgrading your version of WordPress and checking validation errors is the “have you rebooted?” of the WordPress world. It serves you well to keep on top of the constant upgrades, but it’s not what’s causing your web browser to render this incorrectly.

Have a look at https://stackoverflow.com/questions/15808134/zurb-foundation-4-bullets-wont-center-align-in-chrome-and-ie9-ie10 which seems to explain what you’re seeing and offer a solution.

Sean

What’s happening here is you’ve got a tonne of options set to autoload (plus other stuff). So when the page loads — forget the theme or plugins — it’s building objects for every single one of those rows just in case some code later down the line might want to look at it. Eventually it runs out of memory it’s allowed to allocate and you get the white screen.