Plugin yìí kò tíì ṣe àyẹ̀wò pẹ̀lú àwọn ìtújáde mẹ́ta pàtàkì tó kẹ́yìn ti WordPress. Ó lè jẹ́ pé a kò tọ́jú tàbí ṣe àtìlẹ́yìn fún un mọ́, ó sì lè ní àwọn ọ̀ràn ìbámu nígbà tí a bá lò ó pẹ̀lú àwọn ẹ̀yà WordPress tuntun.

Akamai for WordPress

Àpèjúwe

The Akamai for WordPress plugin will automatically purge the cache using the new Fast Purge feature whenever you create or update a post.

With the Fast Purge API, you can automate your publishing flow to maximize performance and offload without compromising on freshness. Switching to a Hold ‘Til Told methodology, you can cache semi-dynamic content with long TTLs, and then refresh it in approximately 5 seconds with Fast Purge.

Development & Support

This plugin is developed on GitHub. Issues should be filed here.

References

Àwọn àwòrán ìbòjú

  • Akamai for WordPress Settings screen

Ìgbéwọlẹ̀

  1. Upload the plugin directory to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Edit the Settings to add credentials

FAQ

Installation Instructions
  1. Upload the plugin directory to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Edit the Settings to add credentials
How long does purging take?

The purge request is almost instantaneous, and the purge itself is completed within 5 seconds.

What is purged?

By default, the front page, and the individual post page are purged. You can additionally enable purging of tag, category, and monthly archives.

What are the limitations?

This API supports the following rate limits per customer:

  • 6,000 URLs per minute (sustained)
  • 5,000 URLs per second (burst)

Purge requests submitted at a higher rate results in a 507 error code. If you receive this error, wait 5 seconds and try again.

In addition, there is a strictly enforced 50,000 byte limit on the size of each request.

Àwọn àgbéyẹ̀wò

Agẹmọ 14, 2024
Terrible plugin, it doesn’t work, and it even generates fatal errors on the website. Unfortunately, this shows how little Akamai cares about its users who work with WordPress. Other services like Cloudflare work much better in conjunction with WordPress.
Èbìbí 21, 2018 1 ìdáhùn
Akamai fixed the error that occurred if the plugin has not set the .edgerc file location (and/or the .edgerc file is missing). However, this plugin is still not very intuitive. Suggestions for improvement are: Inputs for .edgerc file creation. Don’t depend on the user to place this file properly. Security suggestions/checks for .edgerc Cache clearing buttons Advanced configuration modifications besides basic WordPress modifications
Ka gbogbo àwọn àgbéyẹ̀wò 2

Àwọn Olùkópa & Olùgbéejáde

“Akamai for WordPress” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

Túmọ̀ “Akamai for WordPress” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.

Àkọsílẹ̀ àwọn àyípadà

0.6

  • Fix fatal errors when no .edgerc exists or is not found

0.5

  • Fix banner image

0.4

  • Rename plugin to “akamai”

0.3

  • Add support for purging on comments

0.2

  • Use latest Akamai libraries

0.1

  • Initial release