![]() WordPress and Blogspot blogs can now be configured to download the entire history of posts instead of a recent subset. Now supports standard autosave and version history for locally saved drafts. Improved “Split Post” UI – Splitter now presented inline in post content.Interactive image sizing – Rich text mode supports direct manipulation of image display size.Faster Preview filtering – Code-based Markdown and Convert Line Breaks filters.Multimarkdown support – Enhanced functionality when previewing Markdown content.Typewriter Scrolling – View menu option to keep typing vertically centered.Visual formatting bar – Select common formatting options with the mouse.Here’s MarsEdit 4’s description of top new features and changes: If you don’t already own a MarsEdit 3 license, you can purchase a license between now and launch for $39.95 to run the public beta then upgrade to MarsEdit 4 without an additional charge. This only applies to licenses purchased over the web, however, as the Mac App Store version cannot offer upgrades. The MarsEdit 4 public beta isn’t totally free, but you can use the public beta version for free for now if you already own a license for MarsEdit 3. As always, I welcome bug reports and other feedback via email as well. If you decide to install the beta, please join us in the Red Sweater Slack team to discuss the upcoming release. I plan to release the update later this year. The good news? MarsEdit 4 is finally shaping up. This time, a variety of unexpected challenges led to a longer and longer delay. Typically I would like to maintain a schedule of releasing major upgrades every two to three years. It’s been over 7 years since MarsEdit 3 was released. MarsEdit 4 is the first major release in more than seven years and brings editor and WordPress-specific enhancements, auto-save and version history, a Safari app extension, and much more.įrom the MarsEdit 4 public beta announcement: ![]() location ~ (*)sitemap(.*).There’s a new version of the MarsEdit blog publishing software out, and Mac users running the current version can try out the public beta for free ahead of its release. 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 |