You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe.
With the goal set, to transform RSVPs into regular comments (#687), GatherPress might be able to re-use some of the core/comments… blocks, as block-variations to archive the needed RSVP functionality.
This issue is meant as a first collection of related Infos:
Based on your working branch I made some tests using the core/comment(s-...) blocks in combination with a pre_get_comments filter. This allowed me to use the default blocks with the new created RSVPs, which was nice.
I went on testing, added more interactivity to new variations of the core comments blocks one-by-one, which progressed nice & slowly, but it felt not correct, because this was far out of the GatherPress scope. A little more research proved me right: There was already & still is, an open PR adding this and more, core interactivity to the comment blocks.
Take a look at this amazing screencast (taken from the PR) and imagine, GatherPress could just create some block-variation and restrict the use to the new RSVP comment_type, like I did in my non-interactive beginning.
Screen.Capture.on.2023-08-16.at.15-32-27.mp4
This would be .... Wow! I think.
And it would allow GatherPress' RSVPs to benefit from all of the built-in and plugin-powered spam-protection and (some of) the core Discussion settings.
Is your enhancement related to a problem? Please describe.
With the goal set, to transform RSVPs into regular comments (#687), GatherPress might be able to re-use some of the
core/comments…
blocks, as block-variations to archive the needed RSVP functionality.This issue is meant as a first collection of related Infos:
comments_array
not called inrender_block_core_comment_template()
WordPress/gutenberg#47655Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: