Some of you may have woken up this morning to emails from Google Webmaster Tools, telling you Googlebot cannot access CSS and JS files on your site.
If you have a WordPress site with a
robots.txt file, this may be the cause.
Up until July 28th, 2015, it was common for Google to crawl WordPress sites with a
robots.txt file that blocked certain directories from user-agents (browsers) as a security precaution. Starting today, Google is requesting they be able to crawl CSS and JS files for your WordPress site, so they can fully render the page, and make sure it is functioning correctly.
There’s a malady that’s common in many design portfolios. They are filled with images of the finished design artifacts, but they don’t elaborate on whether or not they actually solved their client’s problem.
In many cases, they don’t even address the reasons why each client was prompted to seek out professional web design in the first place.
Because this practice is so prevalent, designers and prospective clients alike are unaware this is a concern. But I believe it is a symptom of greater issues in the design sales process.
WordPress currently powers 24% of all websites. By a wide margin, the most popular e-commerce plugin on WordPress is WooCommerce. So it’s natural that you might to modify some of the user interface copy that comes with WooCommerce out of the box.
Recently, a reader asked how would you change the Return To Shop link on the Cart page. The text on some WooCommerce buttons can be changed with filters that you add to your
functions.php file. But this particular button requires a different approach.
Today’s posts answers a question that doesn’t come up that often, but is worth answering for the times it does.
Namely, “Have you ever resold work you’ve done for one client, for other clients?”
Every once in a while, I share code snippets or development tutorials on the blog. Up until recently, I was using a plugin to handle code highlighting. (That’s where the code blocks have their own fancy code styling.) But then I discovered my plugin was causing a conflict with another part of my site, so I needed a different solution.