Alain Schlesser

We should change the way we refer to the change we make to the DevTools. What we need is feedback on validation errors for users, even when DevTools is "hidden"....

As debugging is obviously a big and important part of using the AMP plugin, I think sprinkling debugging code throughout the other pieces of logic too much is a problem...

> With 996157a, the behavior of the debugging query vars is a little different. What about the flag without value? ``` &amp_flags[reject_all_errors] ```

> Ah, good question. That'll be false. @kienstra Would it make sense to change this so that no flag value means `true`?

Three possible ways this can be done: 1.) Cron job working off a queue that cache refreshes are queued into. 2.) Non-blocking loopback/AJAX request to trigger the cache refresh in...

Adding a filter now would create a public interface we need to support indefinitely, while we are actually planning on doing a major refactor. For people having an immediate need...

An alternative would be to add a separate button besides the `Spam` & `Trash` buttons. Something like `Send for Analysis` or similar. If they just want to get rid of...

And, yes, the original idea was to ask for permission once on clicking `Spam` and then have this be the new default.

I have encountered a similar error, that is probably caused by the same reason: ``` ERROR: [Semantical Error] The annotation "@Annotation" in method \ExtendedClass::method() was never imported. Did you maybe...

I made some minor updates to the pull request referenced in #24 so that it works as I originally intended. It should work for normal WP sites and wp-starter sites,...