Wordpress Vigilance and Plans
First, behold the benefits of automated testing: TRAC 5180. :-)
Update: fixed in revision 6243 (history)
Goals I’d like to set for myself for the next release of Wordpress are twofold: get the APE messages to 0 errors and 0 warnings; and to cleanup the code so that Atom entries are produced in exactly one place and consumed in exactly one place. (Pete Lacey has indicated that he shares the latter goal and has some additional goals).
The first warning is re: auth and as it is my server, I can certainly configure it for tls/ssl, and will do so.
I’d like to know who the best person (or persons) on the WordPress team to chat with w.r.t. how best to retain foreign markup. This could be an additional database column, or it could be a special form of an attachment, and I would be open to any other idea.
A combination of the code cleanup and handing foreign markup would mean that people who use an APP tool could post extension elements that actually appear in their feed. Does anybody know of any actual use cases for such a function?
A baby step towards converging the wp-app and feed-atom code can be found in this patch. This change (or something like it) could be a first step towards supporting grammars like SVG in WordPress.