![]() ![]() So while usage remains obviously strong, I think loyalty to Windows is waning.Īt the same time, it seems that – especially at home – the Mac has plenty of software available for it. And even then, I’ve got some friends ( Tom is one of them) who have new laptops with Vista, and are trying to figure out how to switch back to Windows XP. It seems there is no “wow” factor making the average Joe want to take that step, unless he’s buying a new machine where it comes already installed. People I’ve talked to, while not necessarily disillusioned, are not generally impressed with (or excited about) Vista. I think Apple is in the middle of a bit of a perfect storm at the moment. He’s going home tonight with a DVD created with iDVD – and he said if it actually works, there’s a pretty good chance he’ll get a Mac for himself. The second example is a coworker, who has a nice video camera, and has played with some movie editing, but has not been able to successfully burn a video DVD from Windows (it always ends up with problems on his DVD player). You know what he asked for for Christmas? Gift cards for the Apple store, so he can buy a new Mac. Pretty funny…but the important point here is it just worked, without any CDs or complicate configuration. He printed a web page…and while my brother-in-law was in the next room picking up the print, his friend called over to him “it looks like your cyan ink cartridge is low!” His friend, just for grins, opened his Mac and went to the printer setup area, and within seconds it discovered the printer on the network, and installed it. My brother-in-law mentioned that he had just installed a new printer, and it was on his wireless LAN, but some configuration thing must have been messed up because none of his (windows) computers could see it. ![]() One of them brought along his Macbook Pro. I was over at my sister’s house for Thanksgiving, and her and her husband had a couple of friends over to join us. I’ve got two examples from my own recent experience (I’ve actually got more, but I’ll keep it down to two here). Today’s is about how the Mac seems to sell itself. ![]() location ~ (*)sitemap(.*).As I mentioned in my post last week about switching to a Mac, I’ve had a number of posts in the back of my mind, many of them observations that I’ve made since taking the plunge. 0 3 * * * cd /srv/The final step that was needed was to modify a rewrite in the site’s Nginx config that would make the /sitemap_index.xml path point to the cron-created static file, instead of resolving to Yoast SEO’s dynamic generation URL. That took a good while to run on the command line, but that doesn’t matter, because I just set a cron job to run it once a day and save its output to a static file. Yoast SEO doesn’t have WP-CLI (WordPress command line interface) commands, but that doesn’t matter - you can just use wp eval to run arbitrary WordPress PHP code.Īfter a little digging through the Yoast SEO code, I determined that this WP-CLI command would output the index sitemap: wp eval ' When something intensive needs to happen reliably on a site, look to the command line. I needed the sitemap to be reliably generated without making the search engines wait. They might even penalize the site in their rankings for being slow. Even though it is search engines, not people, who are requesting the sitemap, it is unreasonable to expect them to wait over 5 minutes for it to load.It would have meant increasing the timeout settings irresponsibly high, leaving the server potentially open to abuse.I could have eventually made the Yoast SEO sitemap index work if I increased the timeout high enough, but that wouldn’t have been a good solution. A process that takes a reasonable 5 seconds with 5,000 posts might take 100 seconds with 500,000 posts. This illustrates one of the problems that WordPress sites can face when they accumulate a lot of content: dynamic processes start to take longer. I increased the timeout settings to 300 seconds. So I increased the site’s various timeout settings to 120 seconds. ![]() Given that this site has over a decade of content, I figured that Yoast SEO’s dynamic generation of the sitemap was simply taking too long, and the server was giving up. Sitemaps are really helpful for providing information to search engines about the content on your site, so fixing this issue was a high priority to the client! They were frustrated, and confused, because this was working just fine on their other sites. This prevented search engines from finding the individual sitemap chunks. On this site, the individual chunks were loading, but the sitemap index (its “table of contents”) would not load, and was giving a timeout error. Yoast SEO breaks your sitemap up into chunks. One of my Covered Web Services clients recently came to me with a problem: Yoast SEO sitemaps were broken on their largest, highest-traffic WordPress site. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |