-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend the generic control to support post fields #5
Comments
Which fields are needed? See also the Gutenberg issue WordPress/gutenberg#22724, which has been Closed even though the work is not complete. Note that
|
The
Here's the output from the
|
Need to explain why the paragraph tag surrounding the output of the ExplanationIt's the I believe this is undesirable processing... a feechur. I don't imagine I'll experience the problem when the shortcode has been converted to a block. But what about other people expecting to see the paragraph if they use this construct? |
I raised an issue WordPress/gutenberg#33345 |
I found it easier to extend the Fields block in oik-blocks.
For I needed to write new logic to register the |
The [bw_field] and [bw_fields] shortcodes support both post meta fields and fields which are properties of the post.
eg post_date, post_modified.
These are used in Fizzie to display a series of inline fields, see
block-template-parts/metadates.html
I could use the same solution in Written, but think it would be better to have a block based solution.
Options are:
post-date
block for the first fieldpost-modified-date
block for the other onepost-date
block to display post modified dateThe text was updated successfully, but these errors were encountered: