Advanced Platform features
Pressidium provides platform-specific tools and extension points for developers who need more control over how their WordPress code interacts with the hosting environment.
Use these advanced features to customize cache behavior, integrate with Pressidium-specific WordPress hooks, detect when your code is running on Pressidium, and control the Persistent Object Cache programmatically.
Advanced cache operations
Extend or modify how Pressidium’s caching system behaves for use cases that require custom cache logic.
The advanced cache operations documentation brings together the available platform extension points for modifying or influencing Pressidium’s adaptive cache engine.
Explore advanced cache operations
Use Pressidium-specific WordPress actions and filters
Pressidium’s must-use plugin provides WordPress actions and filters that developers can use to add custom logic or modify platform-specific behavior.
For example, you can run code after cache purge events or modify paths and cache tags involved in cache operations.
Review Pressidium-specific WordPress actions and filters
Purge additional paths when clearing cache
Extend Pressidium’s automatic Page Cache purge behavior when updating one piece of content also affects other URLs.
You can add related paths to the purge operation—for example, when updating a post also changes an archive, listing page, custom post-type index, or another related page that would not otherwise be cleared automatically.
Purge additional paths when clearing cache
Detect when your code is running on Pressidium
If you develop custom themes, plugins, or WP-CLI commands that behave differently depending on the hosting environment, you can detect whether the code is running on Pressidium.
Pressidium exposes the PRESSIDIUM_PLATFORM environment variable for this purpose, with detection methods for both web requests and CLI contexts.
Detect when your code is running on Pressidium
Disable the Persistent Object Cache programmatically
For advanced development or compatibility scenarios, you can disable Pressidium’s Persistent Object Cache through code rather than changing its state manually.
Use this option when your application needs to control whether the Persistent Object Cache is enabled based on programmatic conditions.
Disable the Persistent Object Cache programmatically
Need help?
If you’re unsure whether you need custom platform or cache behavior, contact the Pressidium Support team before adding code that changes the default behavior of your website.
Where to go next
To continue working with advanced platform features:
- Use a staging environment to test custom code before applying it to production.
- Review your site’s logs if custom code causes errors or unexpected behavior.
- Manage your site’s cache to purge or control caching when testing changes.
Was this article helpful?