acekin
Forum Replies Created
-
Thanks on both accounts.
Cemal
Brandon, I have an update. I think, as I said earlier, some settings in robots.txt interfere with mobile usability, and they are triggered by something like JetPack sharing. Here is the scoop:
- Usability test gets progressively bent out of shape as folders are excluded from crawling by Disallow. It is sensitive to wp-conent, wp-admin, wp-includes, and their subfolders being disallowed, then comes the themes
- I Disallow wp-content then Allow necessary subfolders, rather than disallowing sensitive ones for safety reasons
- It spews out resources are not accessible warnings but gives a thumbs up until the themes folder is Disallowed
- The message “… too close” appears to be misleading, it is mainly complaining (I think) about not knowing how to render the page
- Interestingly, the other mobile usability test which is based on how visitors see the site is quite alright with all these restrictions and can render the page fine.
I think I mistook the trigger as the cause of the problem. I still do not understand why all is cool until sharing is activated, but I have, through trial and error, narrowed it down to the critical setting in the robots.txt. I am writing this update for general information in case others may run into this kind of problems with Google Search Console.
Cemal
Brandon, I am disabling the sharing feature. If you try the test it may pass after a few hours or a day or so.
Brandon, there is something in my robots.txt file that Google does not like. I can certainly produce this result on demand by denying access to /plugins folder and below. If it cannot see the jetpack folder it starts throwing “unfriendly” signals. By making plugins folder allowed to crawl most of the problems disappear. That said, at the peak of these “mobile unfriendly” ratings I can make the Google crawler happy by turning off Sharing.
In some ways, Google pushes me to think in contradictory ways. It tries to crawl nonexisting URLs in bogus folders. But, if I deny crawling in those folders it gets bent out of shape in the mobile friendly ratings. It feels like the proverbial Catch 22 situation. For instance, now it is complaining that it cannot access:
wp-includes/js/wp-emoji-release.min.js?ver=4.3with the domain and path at the beginning. At this point, it is “reluctantly” giving the site user friendly rating with about 15 errors listed below it.
You are right, there may need to be more space but I cannot control that, at least not easily. It needs CSS update of the sharing module. That’s why I brought it to your attention.
You may ignore the part of my message where I said that the official icons did not show, it was a local browser related issue and has nothing to do with JetPack.
Cemal
Thank you Brandon. My Web site is at:
http://www.keptlight.comI have just turned on sharing again. You can see the sudden jump in the errors in the graph with no change to any of the pages or the theme, here is the link to the image:
https://goo.gl/HLzH04When it starts reporting the error none of the pages get a clean bill of health on this test. There is a second test which reports everything being fine. I think it takes a few days for it to start reporting errors and then reducing them once I disable the sharing. I have just checked one of the links and it reports “Awesome this page is mobile friendly”. But I have tried this experiment a few times and for me never failed. The test link is at:
https://www.google.com/webmasters/tools/mobile-friendly/For some reason, some of the buttons are not showing in the sharing block when I use the official buttons. When I switch to icons only they show up. But I left the official buttons for you to see.
Cemal
I have turned it off and marked the problems fixed at Webmaster Tools. I used it mainly to weed out suspicious attempts to get to a strange URL and then block the IP or the network. But I can live without it until the problem is fixed.
Thanks,
Cemal
Will you recommend that we disable the Live traffic until this is fixed or live with WMT errors? Yes my site is installed in a subfolder with a different WordPress and site URLs.
Cemal
Glad to hear I’m not alone, sorry to hear you are having this problem too. I don’t know why this has eluded them to find a fix, it is a problem that can be replicated on demand, at least on some systems.
Oh, well …
@anna, yes that feature works for me. I see the results in the Blocked IPs list, the reason will be given as “Accessed a banned URL”. Those I manually block because of suspicious code injection attempt (or at least that’s how I interpret that long gibberish URL) show as manual block by admin. If I manually block an IP I generally make it permanents in the same page.
I have documented and demonstrated the Options changes adding the Falcon code to htaccess file quite a while ago and decided to live with it since no solution came through, I still do!
I have reported this problem several times. On my systems I can still make it happen on demand by editing the Options in Wordfence and adding, or deleting, a URL to the “Immediately block IP’s that access these URLs” field. Never fails, WF will dutifully add the Falcon caching code block and I have to go and edit the htaccess file to remove it. Tim will remember my reports from the time when I was a premium member.
I am using the latest version of WF and I have just checked to make sure this still happens, it does.
Update:
The message I kept seeing on the thin banner when I went to view Live Traffic happened to be the last message WF recorded a while back for some reason. Here is how I resolved it:
- Downloaded WordPress 4.2.2, and uploaded the WP-INCLUDE folder on top of what I had
- I ran a new WF scan which finished with no errors and that banner message also disappeared.
- The error message disappeared from the WF banner on top of the Live Traffic pages
Originally I got the impression that it was a current problem that kept refreshing on the banner, it turned out to be the last incident WF recorded. It may be advisable, after a kind of an alarming error message to recheck to verify the error was persisting rather than showing the last message.
The way I resolved the issue is simple, and turned out to be effective as well. The message has not returned yet.
Cemal
I stand corrected, I did not realize that feature was available only to premium members. My premium membership has just expired, which explains the appearance of blocked countries.
Cemal
One option may be to put “Monthly Summary” on the site itself. There is already a two-week summary that can be displayed from the “Screen Options” on the dashboard. Maybe a link to see the monthly activity will eliminate all the mail traffic. An additional nice touch may be an icon, a flag, something like a red disc next to Wordfence dashboard block to indicate that the monthly report is ready; of course the admin should be able to turn this off explicitly or implicitly by viewing the report.
The other question is: Do users get any additional benefit from the monthly report.
Forum: Plugins
In reply to: [Far Future Expiry Header] Far Future Expiry Header breaks NextGEN and othersOne more piece of information for you. When I installed WordPress in a subfolder and then chose the pretty permalinks to show the post title WordPress created the .htaccess in the site root not in the subfolder where WordPress was installed. It is also what they recommend in their codex about “Giving WordPress Its Own Directory.” I have just noticed a second .htaccess file with the Far Future Expiry header information located in the directory where WordPress is installed. That’s why I could not find the inserted code. This is ONLY on my production site. Although it appears to be fine to have multiple .htaccess files in different folders there must be a better way of handling this.
The problem I originally reported was not related to this, I want to clarify that, since it happened on two sites one installed directly in the root and one installed in a subfolder. They both had identical NextGEN gallery grid display problem and no lightbox functionality.
I wanted to update this post to add information for your benefit. I am willing to go without a plugin for this purpose.
Thanks,
Cemal