Joschi Kuphal 吉
https://jkphl.is
•
Apr 5
Randall Degges
https://www.rdegges.com
•
Apr 4
return get_option( 'micropub_default_post_status', MICROPUB_DRAFT_MODE ? 'draft' : 'publish' );
This doesn't work because the problem is not that micropub_default_post_status doesn't exist, it's that it does exist in the database and the value is blank.
Was able to reproduce this after carefully reading the other thread. The key is this: https://github.com/snarfed/wordpress-micropub/issues/104#issuecomment-359267767
If you save the writing settings page, it writes a blank value for micropub_default_post_status to the database, so then the get_option call later will return the blank value instead of the default.
gerwitz
https://github.com/gerwitz
•
Apr 2
I have no strong opinion here, 501 arose from discussion on the IWC Slack.
My API experience falls into REST and deep-stack buckets. Micropub is lighter weight than any non-REST protocol I've used or implemented over HTTP, so it "feels" right for it to act RESTy.
To defend my recommendation, if it's not appropriate to use HTTP codes, why does the spec call for the use of 4xx codes, rather than replying with a 2xx that includes error details?
Eddie Hinkle
https://eddiehinkle.com/
•
permalink
That’s funny, I have that tag query support on my list both for my site and for Indigenous as well!
Chris
https://chrisbeckstrom.com
•
Apr 1
This is great, thanks for creating such a useful tool! Do you also host your own git repo, and if so, how do you integrate that into your website?
I use gitlist (https://github.com/klaussilveira/gitlist) but it’s not integrated into my site at all.
Also on:
