WPIntell

Source evidence

Does not support closures

WP REST API Cache · review · 2018-05-22T07:28:00+00:00

complaintsentiment
highseverity
0.91relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 2 stars
Xedin Unknown unresolved
This plugin appears to cache REST API responses based on their handlers, not on their request. When a handler is written in the form of an anonymous function, it doesn’t work, producing a fatal error. Truly, except with the help of a couple of PHP libraries, serialization of closures is not possible in PHP at all. Endpoint authors cannot be expected to use named functions (bleh!) just because of this limitation. Another major problem is that the plugin apparently uses WP transients to cache the response body. No other caching medium can be used. Not sure why I would cache a 1MB JSON response in a transient in the DB – a file seems to be a much better way for that. Finally… why re-invent the wheel? Use PSR-16. Hi @xedinunknown-1 , How I can simulate that error? Thanks This reply was modified 8 years ago by airesvsg .

Comments

1 shown
airesvsg 2018-05-29T14:42:00+00:00

Hi @xedinunknown-1 , How I can simulate that error? Thanks This reply was modified 8 years ago by airesvsg .