BugWP logo BugWP
Back to Community
Home / Community / Plugin → Post types order

Troubleshooting Common Post Types Order Plugin Issues: Warnings, Settings, and More

23 threads Sep 16, 2025 Plugin → Post types order

Content

The Post Types Order plugin is a popular tool for managing the display order of posts and custom post types in WordPress. However, like any complex software, users can occasionally encounter issues. This guide compiles common problems reported by the community and offers solutions to help you resolve them efficiently.

1. PHP Warnings and open_basedir Restrictions

Problem: After migrating a site to a Windows server, activating the plugin triggers warnings about is_readable() and open_basedir restrictions, often followed by a headers already sent warning.

Why it happens: This is typically a server environment issue. The open_basedir PHP directive restricts which files can be accessed. The error suggests the plugin is trying to load a language file from a path that falls outside the allowed directories on the new Windows server.

Solution: This often requires a server-level fix. You may need to adjust the open_basedir setting in your server's PHP configuration (e.g., in php.ini) to include the correct path where the plugin's language files are located. Contact your hosting provider's support for assistance with modifying server PHP directives.

2. Settings Menu Disappears or Becomes Inaccessible

Problem: The plugin's admin menu link vanishes or users with certain roles get a "permissions" error when trying to access it.

Why it happens: This can occur for a few reasons:

  • The DISALLOW_FILE_MODS constant is set to true in wp-config.php.
  • The plugin's settings menu can sometimes be relocated under a different admin menu (like "Posts" or "Media") if its original location becomes unavailable.
  • A default capability setting may be incorrectly set for user roles.

Solution:

  • If you have define('DISALLOW_FILE_MODS', true); enabled, be aware this may intentionally hide certain plugin menus.
  • If the menu is missing, check under the Posts and Media admin menus for a "Re-order" submenu item.
  • To control who can access the plugin, an administrator can navigate to Settings -> Post Types Order and adjust the "Minimum Level to use this plugin&quot> setting. For multisite networks, a global settings change via a filter might be necessary.

3. Deprecated Code and Debug Notices

Problem: Warnings or errors appear in your browser's console or in debug logs, mentioning things like FILTER_SANITIZE_STRING is deprecated or undefined variables.

Why it happens: WordPress and PHP continuously evolve, and functions or constants eventually become deprecated. If a plugin hasn't been updated to use the latest standards, it can trigger these notices, especially when WP_DEBUG is enabled.

Solution: The first and most important step is to ensure you are running the latest version of the Post Types Order plugin. The development team has a history of addressing these deprecation warnings in updates (e.g., version 2.1.4 fixed one such issue). If you are up-to-date and still see notices, you may need to temporarily disable WP_DEBUG on a production site or report the specific new warning to the community for further investigation.

4. Customization Filters Have Changed

Problem: A site feature breaks after a plugin update, and the error is related to a customized function using a specific plugin filter.

Why it happens: To improve code, developers sometimes deprecate old filters and replace them with new ones. For example, the filter cpto/interface_itme_data (which had a typo) was deprecated and replaced with pto/interface_item_data.

Solution: If your custom code breaks after an update, check the plugin's changelog and source code for notes on deprecated functions or filters. You will need to update your custom code to use the new, supported filter names as specified by the plugin developers.

General Troubleshooting Tips

  • Clear Caches: Always clear your browser cache and any server-side or WordPress caching plugins after updating software. This solved a displayed issue with the plugin's update changelog for some users.
  • Conflict Testing: If you experience odd behavior like missing menus, deactivate all other plugins and switch to a default WordPress theme (like Twenty Twenty-Four). If the problem resolves, reactivate your plugins one-by-one to identify the conflict.
  • Check the Codex: For issues like mixed-content warnings (HTTP/HTTPS) for plugin assets, ensure the plugin correctly uses functions like plugins_url() within appropriate hooks like admin_init.

Remember, for persistent issues, the WordPress.org support forums for the plugin can be a valuable resource to search for existing solutions or get help from the wider community.

Related Support Threads Support