Cache API

Welcome!

The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bug? Create a ticket in our bug tracker.

Want to contribute? Get started quickly with our tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on our reports page, like patches needing testing.

Other questions? We also have a detailed handbook for contributors, complete with tutorials.

Cache API component

The Object Cache API lives in cache.php. The cache can be replaced by persistent object caches such as Memcached Redux and APC Object Cache.

Create a new ticket

34 open tickets in the Cache API component

34 open tickets	defect (bug)	enhancement
Awaiting Review	17	9
Future Release	3	4
	0	1

34 open tickets. Last 7 days: +0 tickets

5 tickets that have no replies

View list on Trac

#40420 key/group naming confusion in _get_non_cached_ids() performance
#41615 Small clean-up in cache.php
#43341 Proposal: new cache helper functions
#45662 Set Last changed helper function
#46388 WP_User::get_data_by(): Cache non-existent users to prevent triggering multiple queries performance

34 open tickets

Open bugs: 20. View list on Trac

Help maintain this component

Component maintainers:

Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.

Contributors following this component:

WordPress.org