This document outlines WP Job Manager’s code deprecation policy, what is considered internal code, the timelines for removing deprecated code, and which versions of WordPress core and WooCommerce are supported.
When Deprecated Code is Removed
Deprecated code is always removed in a major release. The scenarios below assume that there is at least one minor release that contains the deprecation before the major release in which the code is removed.
Deprecated code removal will adhere to the following guidelines:
- Code that is considered public will be removed in two major versions after the deprecation. This includes hooks, public and protected methods, and global functions that have not been marked with
- Functions and methods marked with
@access privateare considered private and shouldn’t be used. They will be removed in the next major version after being marked as deprecated.
Internal code is considered “not-for-public-use”. This code might change in future releases without being deprecated first. In other words, backward compatibility of internal code is not guaranteed.
- Private methods may be removed without notice.
- Public class constants are considered private and may be removed without notice.
Although in general, we try to maintain compatibility, the officially supported versions can be found below:
- PHP: 7.4 and above.
- WordPress core: The current version and the two most recent ones. For example, if the current version is 6.3 then the supported versions are 6.2 and 6.1.
- WooCommerce: WooCommerce is a requirement for WC Paid Listings paid add-on. The supported versions are the current version and the most recent major one. For example, if the current version is 8.1 the supported versions are 7.0 and above.