Turns out it’s not just mobile users having these types of 404 errors with parts of a single page on the theme. Here’s new 404 errors:
URL with 404 error: http://www.johnrothra.com/blog/wp-content/themes/customizr/inc/js/tc-scripts.min.js
Referring URL: http://www.johnrothra.com/response-relevant-bad-dating-advice/
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.77.4 (KHTML, like Gecko) Version/7.0.5 Safari/537.77.4
URL with 404 error: http://www.johnrothra.com/blog/wp-content/themes/customizr/inc/js/retina.min.js
Referring URL: http://www.johnrothra.com/response-relevant-bad-dating-advice/
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.77.4 (KHTML, like Gecko) Version/7.0.5 Safari/537.77.4
URL with 404 error: http://www.johnrothra.com/blog/wp-content/themes/customizr/inc/js/fancybox/jquery.fancybox-1.3.4.min.js
Referring URL: http://www.johnrothra.com/response-relevant-bad-dating-advice/
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.77.4 (KHTML, like Gecko) Version/7.0.5 Safari/537.77.4
URL with 404 error: http://www.johnrothra.com/blog/wp-content/themes/customizr/inc/js/bootstrap.min.js
Referring URL: http://www.johnrothra.com/response-relevant-bad-dating-advice/
User Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53
URL with 404 error: http://www.johnrothra.com/blog/wp-content/themes/customizr/inc/js/modernizr.min.js
Referring URL: http://www.johnrothra.com/response-relevant-bad-dating-advice/
User Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D201 Safari/9537.53
URL with 404 error: http://www.johnrothra.com/blog/wp-content/themes/customizr/inc/css/blue.min.css?ver=3.1.15
Referring URL: http://www.johnrothra.com/response-relevant-bad-dating-advice/
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.77.4 (KHTML, like Gecko) Version/7.0.5 Safari/537.77.4
Some browsers can be set to ignore links to ad sites. Maybe they’re picking up on the “ad-” in the url?
I’m not sure what “ad-” is in the URLs that are being rejected (404’d). None have “ad-” in them. All the URLs seem to be part of the themes functionality.
When I go to http://www.johnrothra.com/blog/wp-content/themes/customizr/inc/, I see a list of all files in the directory, and the js directory isn’t there. Could it have been deleted by mistake? You might need to redownload Customizr, extract that folder, and upload it to your server via FTP or whatever file management application your host provides.
The latest update changed some of the structure of the parent theme. The css and js directories are now under “admin.” However, as the theme changed its call structure, when a browser pulls the site, it should follow that updated call structure.
When did you update the theme? According to Super-Cache, the cached page was generated on 2014-07-07 at 7:48PM. Did you update the theme after then?
The theme updated yesterday or the day before (July 7th or 8th) — the day the update was released. I’ve cleared the cache now, though.
I hope @electricfeet sees this because he’s (she’s?) a lot more familiar with the theme than I am.
I’m now getting a ton of these 404 errors related to the layout of the theme’s new call structure since the update a few days ago! I think the theme designer needs to see this!
Here’s a screenshot of my 404 log showing the most recent URLs to get 404 errors and the number of hits on each one. As you can see, they are related to the parent theme and all these started showing up after the update. Also, the user agents are both Windows, Mac, and smart phones.
Image: https://drive.google.com/file/d/0B4mnNZ1F-EDsT1BaeUtmZHB5OHM/edit?usp=sharing
Hi @jrothra, your site seems to work fine now.
Can you please confirm that it is OK and tell us what you did to fix it?
Thanks
If you this issue is fixed, could you please set the forum topic status as resolved?
Thanks and I look forward to reading from you!
The issue isn’t fixed and I did nothing except report 404 errors, so it’s not resolved. Here’s the most recent screenshot showing that the errors are increasing: https://drive.google.com/file/d/0B4mnNZ1F-EDsc1M5Z0FPejlNbUU/edit?usp=sharing
Note especially #s 1-7 and 10.
Many of these 404’d files seem to have been moved with the latest version. I’ve cleared the cache multiple times, yet the calls seem to still be failing. These started with the update to Customizr 3.1.17.
Ok looking back at your website, this page for example do have the 404 problem.
Apparently your WordPress is installed in /blog directory and you managed some redirections on http://www.johnrothra.com.
This might be the root of the problem.
Or there might be a plugin issue.
I would recommend to identify clearly the issue by first desactivating all your plugins and see what you get.
I would also recommend to read this page about diagnosing issues in Customizr.
Best
WP was installed in /blog/ many years ago and I adjusted it to work via the root following WP’s instructions (cf. http://codex.ww.wp.xz.cn/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install).
A few months ago I also changed the permalink structure from /year/month/post-slug/ to just domain.com/post-slug.
The redirects I have setup are twofold:
1. Bots and old links out there that keep trying to find the old permalink system are being sent to the new one
2. Old directories created by me before I used WP that I later deleted, pointing old links/bot crawls to someplace else.
Neither of these redirects are significant nor do they affect the theme trying to pull based on the old structure (3.1.16 and before). Since all this started with the update to 3.1.17, I suspect that has more to do with it than plugins or redirects. Later tonight I will check the diagnosis page to which you linked.
