Urgent.News

What's breaking now, across thousands of outlets.

Tech

Two Rewrite Changes That 404'd Every Post on This Blog

An SEO audit of this blog turned up a list of small, unglamorous findings. /blog/ returned 404. Category archive URLs contained a literal /./ segment — /blog/./wordpress-performance — while tag archives were clean. Author archives 404'd for every author. None of these looked dangerous. They looked like an afternoon. That evening, every single post on the site 404'd. Twice. Two separate changes,…

An SEO audit revealed several small issues in the blog's permalink structure. The / / segment in category archives and the broken tag archives were the primary concerns. Despite appearing harmless, these issues led to two separate incidents where the entire blog went offline.

The first incident occurred when category archives started 404-ing. Subsequently, author archives and all posts followed suit. The second incident happened two hours later when all posts were again inaccessible.

Two changes were made to resolve the issues. The first involved altering the category_base setting from 'blog' to an empty value. This resolved the issue with category archives, allowing them to function properly. The second incident was addressed by implementing custom rewrite rules using the add_rewrite_rule() function.

Despite the temporary nature of the issues, the root cause of the problems remained unclear. The elimination of the custom category rule proved to be the effective solution.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

We Designed a Monitoring Stack, Then Decided Not to Build It

The plan was a good plan. Continuous frontend performance monitoring for 30 to 40 WordPress sites: sitespeed.io runners on Hetzner Cloud, a time-series store, artifacts in object storage, Grafana on…

  • Planned monitoring stack for 30-40 WordPress sites
  • Architecture decision records questioned stack viability
  • Self-hosted stack cost €4,900/year two, break-even at 600 URL profiles

How to add an MCP server to VS Code (mcp.json, .mcp.json and fixes)

How to add an MCP server to VS Code Checked against the official docs: Oct 28, 2026 VS Code's agents can call tools from MCP (Model Context Protocol) servers, for example to drive a browser, read…

  • Use MCP: Add Server command in VS Code's Command Palette
  • Choose ID, save location, and provide trust/sign-in info
  • Add server via guided flow, gallery, or manual config file

Cursor rules vs AGENTS.md: which to use (and .cursorrules)

Cursor rules vs AGENTS.md Checked against the official docs: Oct 27, 2026 Cursor gives you three ways to hand your coding agent standing instructions: project rules in .cursor/rules , an AGENTS.md…

  • AGENTS.md is a markdown file for project instructions, supported by multiple coding agents.
  • .cursor/rules/.mdc files are Cursor-specific rules for certain situations, scoped by globs.
  • .cursorrules is legacy and will be deprecated, migrate to .cursor/rules/.mdc format.

More from Friday 20 November →