Category: Bug fixes

You have just moved a site to a new server, tested locally, and everything looks fine — but when you open the domain in a browser, you see a completely different site. Clearing the cache does not help. What is happening?

When we register new post type is recommended use names in the singular (e.g. default post types — post, page, etc.), but in some cases it's not always convenient.

The Google Language Translator plugin (by Translate AI Multilingual Solutions) can produce a frustrating side effect: after a page is translated, some text that was originally uppercase or title-cased is displayed in lowercase. The issue is not a bug in the translation itself — it is a CSS text-transform conflict triggered by how the plugin…

On single-page or landing-page WordPress sites where the navigation uses anchor links (#section), WordPress marks all matching anchor items as active simultaneously. This happens because the CMS compares the full current URL against each menu item URL and considers a match whenever the page URL appears in the item’s href — regardless of the fragment.

When making outbound HTTPS requests with cURL — from a PHP script, a site scraper, or wp_remote_get() — you may encounter the following warning:

A common WordPress pagination bug causes the second (and subsequent) pages to display exactly the same posts as the first page. The fix is a single missing line in your WP_Query arguments.

If you suddenly cannot add a featured image, upload files to the Media Library, or select images in Advanced Custom Fields — and you see a JavaScript error in the browser console — the culprit is very likely a misconfigured Content Security Policy (CSP).

When you pass an array through json_encode() on the PHP side and then parse it with JSON.parse() or receive it via jQuery’s $.ajax, you may find that json_decode() returns null — or the JavaScript side receives unexpected string values instead of integers. The root cause is almost always a type mismatch in the PHP array.

A custom WP_Query loop with AJAX-based sorting works correctly for one post type but produces wrong order for another. The sort arguments look right. The most common cause is a third-party plugin — specifically one that overrides the default post order at the database level.