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

The new Gutenberg editor and the future of ACF #622

Open
pagelab opened this Issue Jun 29, 2017 · 141 comments

Comments

Projects
None yet
@pagelab

pagelab commented Jun 29, 2017

Knowing that:

  1. The Gutenberg editor has high probability to be the new WordPress default editor for the 5.0 version,
  2. As a result, the current WordPress PHP metabox system is likely to be greatly limited in favor of a JS flavor of metaboxes.

My question is: what are the plans for ACF in the near future, as this will change pretty much everything that has been done so far with ACF and will affect everyone that works with it?

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Jun 29, 2017

Owner

Hi @pagelab

Thanks for the topic. The Gutenberg UI is very exciting, but I must agree with the majority of developers that the metabox changes are worrying.

I need to do some further reading, but it sounds more like a discussion at the moment as apposed to a definite announcement.

This is definitely a topic to stay tuned to. If you are following the Gutenberg project, would you mind posting back if there are any major decisions / anouncements made?

Thanks again

Owner

elliotcondon commented Jun 29, 2017

Hi @pagelab

Thanks for the topic. The Gutenberg UI is very exciting, but I must agree with the majority of developers that the metabox changes are worrying.

I need to do some further reading, but it sounds more like a discussion at the moment as apposed to a definite announcement.

This is definitely a topic to stay tuned to. If you are following the Gutenberg project, would you mind posting back if there are any major decisions / anouncements made?

Thanks again

@pagelab

This comment has been minimized.

Show comment
Hide comment
@pagelab

pagelab Jun 30, 2017

This is definitely a topic to stay tuned to. If you are following the Gutenberg project, would you mind posting back if there are any major decisions / anouncements made?

Sure, I'll post it here as soon as they settle down on the topic of metaboxes. As everybody else, I'm keeping a close eye on this one.

pagelab commented Jun 30, 2017

This is definitely a topic to stay tuned to. If you are following the Gutenberg project, would you mind posting back if there are any major decisions / anouncements made?

Sure, I'll post it here as soon as they settle down on the topic of metaboxes. As everybody else, I'm keeping a close eye on this one.

@marsjaninzmarsa

This comment has been minimized.

Show comment
Hide comment
@marsjaninzmarsa

marsjaninzmarsa Jun 30, 2017

Looks like they plan to support "legacy" metaboxes via PHP callback. It's WordPress after all.

marsjaninzmarsa commented Jun 30, 2017

Looks like they plan to support "legacy" metaboxes via PHP callback. It's WordPress after all.

@pagelab

This comment has been minimized.

Show comment
Hide comment
@pagelab

pagelab Jun 30, 2017

Here's some main Gutenberg tickets concerning the future of PHP metaboxes, FYI:

pagelab commented Jun 30, 2017

Here's some main Gutenberg tickets concerning the future of PHP metaboxes, FYI:

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Jul 2, 2017

Owner

Thanks @pagelab - some awesome info here

Owner

elliotcondon commented Jul 2, 2017

Thanks @pagelab - some awesome info here

@cr101

This comment has been minimized.

Show comment
Hide comment
@cr101

cr101 Aug 6, 2017

@elliotcondon You will want to read comment #320523428 in regards to rendering PHP metaboxes

cr101 commented Aug 6, 2017

@elliotcondon You will want to read comment #320523428 in regards to rendering PHP metaboxes

@pagelab

This comment has been minimized.

Show comment
Hide comment
@pagelab

pagelab Aug 6, 2017

pagelab commented Aug 6, 2017

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon
Owner

elliotcondon commented Aug 6, 2017

Thanks @cr101 and @pagelab

@nylen

This comment has been minimized.

Show comment
Hide comment
@nylen

nylen Aug 7, 2017

Please also read WordPress/gutenberg#952 (comment) as it is still very much true.

nylen commented Aug 7, 2017

Please also read WordPress/gutenberg#952 (comment) as it is still very much true.

@chvon7thal

This comment has been minimized.

Show comment
Hide comment
@chvon7thal

chvon7thal Aug 7, 2017

After 30min look to the plugin, I thing we will have to rethink some, but not all, about how to use ACF. For my part, I builded a "block" component, with several type of boxes, beginning with the notion of columns, able to display different content types, including free formated text, and images.
Probably this part (text and images) won't be necessary anymore.

I also build a ICS Event component, or a contact description based on vcard, for those there will be the question of where to define/populate them and how to link them...

For myself I left the idea of custom-post in favor of custom-fields and it gives amazing opportunities for flexibel content and linkings.

But I also short circuited the rendering part of ACF, preferring a kind of caching in the meta-datas: In other words, I use ACF for its flex content system in the admin part. With acf-save I pre-render them. i.e.: For one post I can have one author only, or three (author, translator, photograph) - So if my flex field is populated, I render the format and save it in my own metadata as the author block. In the front-end, I only check the existence of the cached block.

The question that I will check: Can I create a placeholder for that in Gutenberg and how flexibel would it be (change place, or order with an other guttenberg-custom-block.

chvon7thal commented Aug 7, 2017

After 30min look to the plugin, I thing we will have to rethink some, but not all, about how to use ACF. For my part, I builded a "block" component, with several type of boxes, beginning with the notion of columns, able to display different content types, including free formated text, and images.
Probably this part (text and images) won't be necessary anymore.

I also build a ICS Event component, or a contact description based on vcard, for those there will be the question of where to define/populate them and how to link them...

For myself I left the idea of custom-post in favor of custom-fields and it gives amazing opportunities for flexibel content and linkings.

But I also short circuited the rendering part of ACF, preferring a kind of caching in the meta-datas: In other words, I use ACF for its flex content system in the admin part. With acf-save I pre-render them. i.e.: For one post I can have one author only, or three (author, translator, photograph) - So if my flex field is populated, I render the format and save it in my own metadata as the author block. In the front-end, I only check the existence of the cached block.

The question that I will check: Can I create a placeholder for that in Gutenberg and how flexibel would it be (change place, or order with an other guttenberg-custom-block.

@lukecav

This comment has been minimized.

Show comment
Hide comment
@lukecav

lukecav Aug 28, 2017

A number of comments related to ACF and metaboxes in this post.
https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/

lukecav commented Aug 28, 2017

A number of comments related to ACF and metaboxes in this post.
https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/

@cr101

This comment has been minimized.

Show comment
Hide comment
@cr101

cr101 Aug 28, 2017

@elliotcondon Do you plan to release a version of ACF and/or ACF PRO that will be compatible with Gutenberg in WordPress 5.0?

cr101 commented Aug 28, 2017

@elliotcondon Do you plan to release a version of ACF and/or ACF PRO that will be compatible with Gutenberg in WordPress 5.0?

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Aug 29, 2017

Owner

Hi guys
Thanks for the comments.

@lukecav - it's hard to believe that WP are even considering removing the WP metaboxes. I am scared for every WooCommerce user.

@cr101 - Yes, of course. Once we get official statements / documentation for the gutenberg changes, I will release updates ASAP to ensure compatibility.

Owner

elliotcondon commented Aug 29, 2017

Hi guys
Thanks for the comments.

@lukecav - it's hard to believe that WP are even considering removing the WP metaboxes. I am scared for every WooCommerce user.

@cr101 - Yes, of course. Once we get official statements / documentation for the gutenberg changes, I will release updates ASAP to ensure compatibility.

@lukecav

This comment has been minimized.

Show comment
Hide comment
@lukecav

lukecav Aug 29, 2017

I am sure WooCommerce will not change at all, since those metaboxes are on custom post type for product etc.

lukecav commented Aug 29, 2017

I am sure WooCommerce will not change at all, since those metaboxes are on custom post type for product etc.

@pagelab

This comment has been minimized.

Show comment
Hide comment
@pagelab

pagelab Aug 29, 2017

Some key points regarding meta boxes from Matt's post:

There will definitely be a plugin that gives you the legacy / old edit page.
There will be no problem to provide a legacy interface for a few releases.

So, it seems that this mitigates a lot the pressure on ACF.

pagelab commented Aug 29, 2017

Some key points regarding meta boxes from Matt's post:

There will definitely be a plugin that gives you the legacy / old edit page.
There will be no problem to provide a legacy interface for a few releases.

So, it seems that this mitigates a lot the pressure on ACF.

@lukecav

This comment has been minimized.

Show comment
Hide comment
@lukecav

lukecav Aug 29, 2017

Stress the words for a few releases, again not define major or minor releases of Gutenberg.

lukecav commented Aug 29, 2017

Stress the words for a few releases, again not define major or minor releases of Gutenberg.

@cr101

This comment has been minimized.

Show comment
Hide comment
@cr101

cr101 Aug 29, 2017

The Gutenberg development is moving at a very fast pace and the new editor will be in WordPress core in only a few months. v1.0 was released today

cr101 commented Aug 29, 2017

The Gutenberg development is moving at a very fast pace and the new editor will be in WordPress core in only a few months. v1.0 was released today

@digitalbaboon

This comment has been minimized.

Show comment
Hide comment
@digitalbaboon

digitalbaboon Aug 29, 2017

I also would love an ACF update that works with Gutenberg considering 1.0 is released and it is rather usable already.

digitalbaboon commented Aug 29, 2017

I also would love an ACF update that works with Gutenberg considering 1.0 is released and it is rather usable already.

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Aug 29, 2017

Owner

Hi guys,

Thanks for the comments. Don't worry, I am keeping up with all Gutenberg news.

Please don't mistake v1.0 for an official release, the Gutenberg project is far from complete and this is only their versioning style.

Once we get official statements / documentation for the Gutenberg changes, I will release updates ASAP to ensure compatibility. Until then, there is no point worrying.

If anyone is worried about the Gutenberg project direction, please be sure to post on the Gutenberg github issues: https://github.com/WordPress/gutenberg

Owner

elliotcondon commented Aug 29, 2017

Hi guys,

Thanks for the comments. Don't worry, I am keeping up with all Gutenberg news.

Please don't mistake v1.0 for an official release, the Gutenberg project is far from complete and this is only their versioning style.

Once we get official statements / documentation for the Gutenberg changes, I will release updates ASAP to ensure compatibility. Until then, there is no point worrying.

If anyone is worried about the Gutenberg project direction, please be sure to post on the Gutenberg github issues: https://github.com/WordPress/gutenberg

@CreativeDive

This comment has been minimized.

Show comment
Hide comment
@CreativeDive

CreativeDive Sep 2, 2017

@elliotcondon The answer of the founder and CEO Matt Mullenweg to metaboxes at https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/:

Matt: Some things like toolbar buttons will definitely need to be updated to work with Gutenberg, other things like Metaboxes there will be no problem to provide a legacy interface for a few releases. But I would say that plugin authors should start updating their plugins in late September if they want to benefit from Gutenberg’s launch.

He says to metaboxes: ... for a few releases. That means the metaboxes are removed after a few versions, maybe WP 5.3, 5.4 or 5.5. It's very hard to believe this :-(

But I hope for a full compatibility by ACF and the gutenberg editor and missing meta boxes.

CreativeDive commented Sep 2, 2017

@elliotcondon The answer of the founder and CEO Matt Mullenweg to metaboxes at https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/:

Matt: Some things like toolbar buttons will definitely need to be updated to work with Gutenberg, other things like Metaboxes there will be no problem to provide a legacy interface for a few releases. But I would say that plugin authors should start updating their plugins in late September if they want to benefit from Gutenberg’s launch.

He says to metaboxes: ... for a few releases. That means the metaboxes are removed after a few versions, maybe WP 5.3, 5.4 or 5.5. It's very hard to believe this :-(

But I hope for a full compatibility by ACF and the gutenberg editor and missing meta boxes.

@brograhamer

This comment has been minimized.

Show comment
Hide comment
@brograhamer

brograhamer Sep 5, 2017

ok. NO. Enough is enough.

ACF / metaboxes are what makes Wordpress a powerful CMS, not just a blogging platform. Blocks cannot, and will never, replace what ACF is. Blocks can, however, enhance custom themes and add some functionality to users without the use of ACF and / or a third party builder.

As a theme developer for a company that builds custom websites using Wordpress, the removal of these metaboxes is entirely unacceptable without discussing a solution.

Why don't we keep metaboxes until we have an alternative that ties in with Gutenberg flawlessly before we even discuss their removal?

  1. How are plugin authors like ACF going to adapt to Gutenberg? Far as I can tell there are no real answers here. Also entirely unacceptable.

  2. I am EXTREMELY excited for Gutenberg, I love it - but it will literally destroy businesses who rely on Wordpress to build custom websites for their clients.

I would prefer to never manually create my own metaboxes ever again without the help of ACF.

Yes, I understand a solution is being worked on - but NOBODY here knows what that even looks like or if it's possible. So far this seems pretty heavy handed against businesses and plugin creators with the "figure it out / open source / not our problem" montra.

I keep commenting here for any sign of a solution. I keep leaving with more questions, more anxiety, and more frustrations. This is absolutely ridiculous.

Will metaboxes that ACF and Yoast provides exist under the Gutenberg edit (not legacy)?

This should be dead simple to answer. Sadly, not finding those answers, and my pure excitement and love for how it functions is hinging on this very fact.

brograhamer commented Sep 5, 2017

ok. NO. Enough is enough.

ACF / metaboxes are what makes Wordpress a powerful CMS, not just a blogging platform. Blocks cannot, and will never, replace what ACF is. Blocks can, however, enhance custom themes and add some functionality to users without the use of ACF and / or a third party builder.

As a theme developer for a company that builds custom websites using Wordpress, the removal of these metaboxes is entirely unacceptable without discussing a solution.

Why don't we keep metaboxes until we have an alternative that ties in with Gutenberg flawlessly before we even discuss their removal?

  1. How are plugin authors like ACF going to adapt to Gutenberg? Far as I can tell there are no real answers here. Also entirely unacceptable.

  2. I am EXTREMELY excited for Gutenberg, I love it - but it will literally destroy businesses who rely on Wordpress to build custom websites for their clients.

I would prefer to never manually create my own metaboxes ever again without the help of ACF.

Yes, I understand a solution is being worked on - but NOBODY here knows what that even looks like or if it's possible. So far this seems pretty heavy handed against businesses and plugin creators with the "figure it out / open source / not our problem" montra.

I keep commenting here for any sign of a solution. I keep leaving with more questions, more anxiety, and more frustrations. This is absolutely ridiculous.

Will metaboxes that ACF and Yoast provides exist under the Gutenberg edit (not legacy)?

This should be dead simple to answer. Sadly, not finding those answers, and my pure excitement and love for how it functions is hinging on this very fact.

@lukecav

This comment has been minimized.

Show comment
Hide comment
@lukecav

lukecav Sep 5, 2017

@CreativeDive

Matt Mullenweg is one of the co-founders of WordPress, with the other co-founder being Mike Little.
https://en.wikipedia.org/wiki/Mike_Little

lukecav commented Sep 5, 2017

@CreativeDive

Matt Mullenweg is one of the co-founders of WordPress, with the other co-founder being Mike Little.
https://en.wikipedia.org/wiki/Mike_Little

@CreativeDive

This comment has been minimized.

Show comment
Hide comment
@CreativeDive

CreativeDive Sep 5, 2017

@lukecav thanks for this information ;-)

CreativeDive commented Sep 5, 2017

@lukecav thanks for this information ;-)

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Sep 5, 2017

Owner

@brograhamer - thanks mate. this is a great response, but I think you posted it in the wrong thread. Can you please post your reply on the WP Gutenberg Metaboxes discussion here: WordPress/gutenberg#952

Its important that WP hear the voices of all concerned developers!

Owner

elliotcondon commented Sep 5, 2017

@brograhamer - thanks mate. this is a great response, but I think you posted it in the wrong thread. Can you please post your reply on the WP Gutenberg Metaboxes discussion here: WordPress/gutenberg#952

Its important that WP hear the voices of all concerned developers!

@brograhamer

This comment has been minimized.

Show comment
Hide comment
@brograhamer

brograhamer Sep 6, 2017

@elliotcondon It was meant for here, but certainly can be posted there as well. I think I speak for everyone when I say this entire process is extremely exciting but equally as frustrating. I'll see if I can condense it into something just as firm but more easily understood.

brograhamer commented Sep 6, 2017

@elliotcondon It was meant for here, but certainly can be posted there as well. I think I speak for everyone when I say this entire process is extremely exciting but equally as frustrating. I'll see if I can condense it into something just as firm but more easily understood.

@pagelab

This comment has been minimized.

Show comment
Hide comment
@pagelab

pagelab Sep 15, 2017

https://ma.tt/2017/09/on-react-and-wordpress/

(...) the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library. It will likely delay Gutenberg at least a few weeks, and may push the release into next year.

pagelab commented Sep 15, 2017

https://ma.tt/2017/09/on-react-and-wordpress/

(...) the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library. It will likely delay Gutenberg at least a few weeks, and may push the release into next year.

@brograhamer

This comment has been minimized.

Show comment
Hide comment
@brograhamer

brograhamer Sep 15, 2017

Yikes. How big of an impact is this on Wordpress itself, for those of us unfamiliar with React?

brograhamer commented Sep 15, 2017

Yikes. How big of an impact is this on Wordpress itself, for those of us unfamiliar with React?

@lukecav

This comment has been minimized.

Show comment
Hide comment
@lukecav

lukecav Sep 15, 2017

@brograhamer

React is not in WP core yet, but seems like it will push WP 5.0 out to 2018. Preact and Vue seem to be the top replacements for React use in Gutenberg.

lukecav commented Sep 15, 2017

@brograhamer

React is not in WP core yet, but seems like it will push WP 5.0 out to 2018. Preact and Vue seem to be the top replacements for React use in Gutenberg.

@pagelab

This comment has been minimized.

Show comment
Hide comment
@pagelab

pagelab Sep 30, 2017

Metabox support is in the works (tested with ACF):

WordPress/gutenberg#2804

pagelab commented Sep 30, 2017

Metabox support is in the works (tested with ACF):

WordPress/gutenberg#2804

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Oct 1, 2017

Owner

Thanks @pagelab - sounds promising

Owner

elliotcondon commented Oct 1, 2017

Thanks @pagelab - sounds promising

@joelstransky

This comment has been minimized.

Show comment
Hide comment
@joelstransky

joelstransky Oct 4, 2017

I just gave Gutenberg a spin. They're off to a great start on a tool with lots of potential but I have to agree with a lot of the reviews in that it's really only an improvement on the_content edits. I was happy to see that there's now an "Extended Settings" section where metaboxes will re-emerge.
This could mean some very cool things for ACF in terms how Field Groups get associated with their location rules. Field groups as Gutenberg block types would be a cool thing to see. I'm actually really excited to see where this leads (and would love to participate in whatever work gets us there)

joelstransky commented Oct 4, 2017

I just gave Gutenberg a spin. They're off to a great start on a tool with lots of potential but I have to agree with a lot of the reviews in that it's really only an improvement on the_content edits. I was happy to see that there's now an "Extended Settings" section where metaboxes will re-emerge.
This could mean some very cool things for ACF in terms how Field Groups get associated with their location rules. Field groups as Gutenberg block types would be a cool thing to see. I'm actually really excited to see where this leads (and would love to participate in whatever work gets us there)

@cr101

This comment has been minimized.

Show comment
Hide comment
@cr101

cr101 Oct 25, 2017

Gutenberg 1.5 adds Initial Support for Meta Boxes
It's encouraging to see progress is made towards custom fields support. I certainly hope that there will be a way to remove/hide the 'post content' editor for CPTs as it takes too much space and it pushes the custom fields too far down the page.
We rarely use the current tinyMCE editor in our projects.

cr101 commented Oct 25, 2017

Gutenberg 1.5 adds Initial Support for Meta Boxes
It's encouraging to see progress is made towards custom fields support. I certainly hope that there will be a way to remove/hide the 'post content' editor for CPTs as it takes too much space and it pushes the custom fields too far down the page.
We rarely use the current tinyMCE editor in our projects.

@lukecav

This comment has been minimized.

Show comment
Hide comment
@lukecav

lukecav Oct 27, 2017

Not showing metaboxes by default on load, until you click on Extend Settings, seems like a bit of a mess in Gutenberg as well as.
new product extend settings wc
WordPress/gutenberg#3165

lukecav commented Oct 27, 2017

Not showing metaboxes by default on load, until you click on Extend Settings, seems like a bit of a mess in Gutenberg as well as.
new product extend settings wc
WordPress/gutenberg#3165

@kevinwhoffman

This comment has been minimized.

Show comment
Hide comment
@kevinwhoffman

kevinwhoffman Oct 28, 2017

Hey ACF friends, I share many of your concerns outlined in this issue, and I've been trying to bring them to light in the Gutenberg repo, most recently in WordPress/gutenberg#3151 (comment). Please voice your concerns there as well.

kevinwhoffman commented Oct 28, 2017

Hey ACF friends, I share many of your concerns outlined in this issue, and I've been trying to bring them to light in the Gutenberg repo, most recently in WordPress/gutenberg#3151 (comment). Please voice your concerns there as well.

@lukecav

This comment has been minimized.

Show comment
Hide comment
@lukecav

lukecav Nov 1, 2017

At least the Extend Settings element was removed from Gutenberg, so that metaboxes show on load now.

lukecav commented Nov 1, 2017

At least the Extend Settings element was removed from Gutenberg, so that metaboxes show on load now.

@shanejones

This comment has been minimized.

Show comment
Hide comment
@shanejones

shanejones Nov 2, 2017

I've just noticed that Metaboxes are back although I've also noticed that the ACF fields that I have on the page won't save when I update the post. It just changes to this and doesn't really do anything.

Screenshot

shanejones commented Nov 2, 2017

I've just noticed that Metaboxes are back although I've also noticed that the ACF fields that I have on the page won't save when I update the post. It just changes to this and doesn't really do anything.

Screenshot

@kevinwhoffman

This comment has been minimized.

Show comment
Hide comment
@kevinwhoffman

kevinwhoffman Nov 2, 2017

@shanejones Content not saving has been documented here. Please give it a thumbs up or add a comment if you have additional info. WordPress/gutenberg#3277

kevinwhoffman commented Nov 2, 2017

@shanejones Content not saving has been documented here. Please give it a thumbs up or add a comment if you have additional info. WordPress/gutenberg#3277

@shanejones

This comment has been minimized.

Show comment
Hide comment
@shanejones

shanejones Nov 3, 2017

@kevinwhoffman Weirdly, I demo'd this to someone yesterday and it eventually saved. The version that didn't save was a very complex custom field setup. Fingers crossed for it to get fixed.

shanejones commented Nov 3, 2017

@kevinwhoffman Weirdly, I demo'd this to someone yesterday and it eventually saved. The version that didn't save was a very complex custom field setup. Fingers crossed for it to get fixed.

@TimVevida

This comment has been minimized.

Show comment
Hide comment
@TimVevida

TimVevida Nov 16, 2017

Maybe an interesting feature in Gutenberg 1.17: nested blocks. See WordPress/gutenberg#2743
Also, meta boxes are no longer in an iframe: WordPress/gutenberg#3345

TimVevida commented Nov 16, 2017

Maybe an interesting feature in Gutenberg 1.17: nested blocks. See WordPress/gutenberg#2743
Also, meta boxes are no longer in an iframe: WordPress/gutenberg#3345

@JoshFialkoff

This comment has been minimized.

Show comment
Hide comment
@JoshFialkoff

JoshFialkoff Apr 6, 2018

Is there an ACF-authored plugin that we can use on test sites which use Gutenberg?

JoshFialkoff commented Apr 6, 2018

Is there an ACF-authored plugin that we can use on test sites which use Gutenberg?

@pkarjala

This comment has been minimized.

Show comment
Hide comment
@pkarjala

pkarjala Apr 6, 2018

@JoshFialkoff You can install the current version of ACF and it will work with the ACF block underneath the Gutenberg editor.

pkarjala commented Apr 6, 2018

@JoshFialkoff You can install the current version of ACF and it will work with the ACF block underneath the Gutenberg editor.

@JoshFialkoff

This comment has been minimized.

Show comment
Hide comment
@JoshFialkoff

JoshFialkoff Apr 6, 2018

I see @pkarjala. I was assuming that ACFs would look more Gutenberg-like. Here's a screenshot.
2018-04-06 14-05-12

Is it on the roadmap for ACFs to match the Gutenberg look and feel?

JoshFialkoff commented Apr 6, 2018

I see @pkarjala. I was assuming that ACFs would look more Gutenberg-like. Here's a screenshot.
2018-04-06 14-05-12

Is it on the roadmap for ACFs to match the Gutenberg look and feel?

@pkarjala

This comment has been minimized.

Show comment
Hide comment
@pkarjala

pkarjala Apr 6, 2018

That's the ongoing discussion! 😄 This is the current "gap" implementation until the full version update of Gutenberg is released.

pkarjala commented Apr 6, 2018

That's the ongoing discussion! 😄 This is the current "gap" implementation until the full version update of Gutenberg is released.

@JoshFialkoff

This comment has been minimized.

Show comment
Hide comment
@JoshFialkoff

JoshFialkoff Apr 6, 2018

JoshFialkoff commented Apr 6, 2018

@jcklpe

This comment has been minimized.

Show comment
Hide comment
@jcklpe

jcklpe Apr 7, 2018

@rchipka Tried the plugin just now and got it activated but there seems to be a problem when I actually try to write a post. I've put an issue on the github page for the plugin.

jcklpe commented Apr 7, 2018

@rchipka Tried the plugin just now and got it activated but there seems to be a problem when I actually try to write a post. I've put an issue on the github page for the plugin.

@rchipka

This comment has been minimized.

Show comment
Hide comment
@rchipka

rchipka Apr 10, 2018

@thedonquixotic This will be fixed in the upcoming version.

I revised the code to better integrate with Gutenberg 2.6.0.

Also, I'm considering renaming it to Advanced Custom Blocks, as long as that's cool with @tdmalone.

In addition to major stability/integration improvements, this version will add the ability to make a field group its own block type (with the option to allow child blocks).

The ability to make a field group a block type will allow you to use the Gutenberg add block ("+") to select (by name) the ACF field group and show the fields for that field group in the block content (or in the sidebar).

The latest plugin will also require installing Gutenberg Block Templates (which I'll be releasing as a separate plugin).

This plugin will enable developers to easily add or modify layout for any block type (in PHP) by placing a PHP file with the block's name into your theme's blocks directory.

This is especially powerful because it allows composing custom, nestable, PHP-rendered Gutenberg blocks with integrated ACF fields.

And, since it's all done in a PHP block template file, a developer doesn't need to know any JS/React in order to get a simple block with some fields up and running.

Think of it as a WordPress template "partial", but for block content.

Advanced Custom Blocks will hook into this plugin's AJAX call in order to save custom block attributes before rendering the block content/template.

It will also hook into get_field to automatically get an ACF field value from a block's attributes within the block template.

rchipka commented Apr 10, 2018

@thedonquixotic This will be fixed in the upcoming version.

I revised the code to better integrate with Gutenberg 2.6.0.

Also, I'm considering renaming it to Advanced Custom Blocks, as long as that's cool with @tdmalone.

In addition to major stability/integration improvements, this version will add the ability to make a field group its own block type (with the option to allow child blocks).

The ability to make a field group a block type will allow you to use the Gutenberg add block ("+") to select (by name) the ACF field group and show the fields for that field group in the block content (or in the sidebar).

The latest plugin will also require installing Gutenberg Block Templates (which I'll be releasing as a separate plugin).

This plugin will enable developers to easily add or modify layout for any block type (in PHP) by placing a PHP file with the block's name into your theme's blocks directory.

This is especially powerful because it allows composing custom, nestable, PHP-rendered Gutenberg blocks with integrated ACF fields.

And, since it's all done in a PHP block template file, a developer doesn't need to know any JS/React in order to get a simple block with some fields up and running.

Think of it as a WordPress template "partial", but for block content.

Advanced Custom Blocks will hook into this plugin's AJAX call in order to save custom block attributes before rendering the block content/template.

It will also hook into get_field to automatically get an ACF field value from a block's attributes within the block template.

@tdmalone

This comment has been minimized.

Show comment
Hide comment
@tdmalone

tdmalone Apr 10, 2018

@rchipka Haha no permission from me required, but I am honoured to have provided the inspiration for the name ;)

I wonder though if we should take this discussion to a new issue in your repo, so we don’t clutter this issue for Elliot?

tdmalone commented Apr 10, 2018

@rchipka Haha no permission from me required, but I am honoured to have provided the inspiration for the name ;)

I wonder though if we should take this discussion to a new issue in your repo, so we don’t clutter this issue for Elliot?

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Apr 11, 2018

Owner

Hi @rchipka and friends.

I just wanted to say hi, and let you know that I've been working on some ACF + Gutenberg stuff. I'm keeping this under wraps until a later date, but wanted to flag this with you after seeing your latest posts.

Please keep working on your plugin. I'm really excited to see the community embrace ACF + Gutenberg in any and all ways! But keep in mind there might be something in ACF core that does a similar job!

Thanks
E

Owner

elliotcondon commented Apr 11, 2018

Hi @rchipka and friends.

I just wanted to say hi, and let you know that I've been working on some ACF + Gutenberg stuff. I'm keeping this under wraps until a later date, but wanted to flag this with you after seeing your latest posts.

Please keep working on your plugin. I'm really excited to see the community embrace ACF + Gutenberg in any and all ways! But keep in mind there might be something in ACF core that does a similar job!

Thanks
E

@tdmalone

This comment has been minimized.

Show comment
Hide comment
@tdmalone

tdmalone Apr 11, 2018

Glad you're working on it E, but it's a pity it's under wraps! Why not develop alongside the community? :)

tdmalone commented Apr 11, 2018

Glad you're working on it E, but it's a pity it's under wraps! Why not develop alongside the community? :)

@cjke

This comment has been minimized.

Show comment
Hide comment
@cjke

cjke Apr 11, 2018

It is a commercial project - there is probably a level of risk around ownership depending on the level of help he accepts.

cjke commented Apr 11, 2018

It is a commercial project - there is probably a level of risk around ownership depending on the level of help he accepts.

@rchipka

This comment has been minimized.

Show comment
Hide comment
@rchipka

rchipka Apr 11, 2018

@elliotcondon Thanks for the update.

Hopefully Advanced Custom Blocks serves as a temporary solution and perhaps a model for what goes into ACF core.

The same goes for Gutenburg Block Templates. Ideally a similar solution is implemented in Gutenberg core.

rchipka commented Apr 11, 2018

@elliotcondon Thanks for the update.

Hopefully Advanced Custom Blocks serves as a temporary solution and perhaps a model for what goes into ACF core.

The same goes for Gutenburg Block Templates. Ideally a similar solution is implemented in Gutenberg core.

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Apr 12, 2018

Owner

Hi @tdmalone

I'm keeping things private until Gutneberg is in a more finished and positive place.
What I can tell you is that our integration is working, and it's exciting to think about all the new opportunities this will open up for ACF developers!

Owner

elliotcondon commented Apr 12, 2018

Hi @tdmalone

I'm keeping things private until Gutneberg is in a more finished and positive place.
What I can tell you is that our integration is working, and it's exciting to think about all the new opportunities this will open up for ACF developers!

@jameshoftonspd

This comment has been minimized.

Show comment
Hide comment
@jameshoftonspd

jameshoftonspd Apr 12, 2018

Thanks for the update Elliot, love using ACF and look forward to the new possibilities

jameshoftonspd commented Apr 12, 2018

Thanks for the update Elliot, love using ACF and look forward to the new possibilities

@CreativeDive

This comment has been minimized.

Show comment
Hide comment
@CreativeDive

CreativeDive Apr 17, 2018

@elliotcondon Did you review the following issue with the currently released Gutenberg version 2.6?

WordPress/gutenberg#6174

CreativeDive commented Apr 17, 2018

@elliotcondon Did you review the following issue with the currently released Gutenberg version 2.6?

WordPress/gutenberg#6174

@rchipka

This comment has been minimized.

Show comment
Hide comment
@rchipka

rchipka Apr 17, 2018

@CreativeDive This is because ACF overwrites the window.wp.hooks object, causing various functions to be undefined or redefined in an incompatible way.

A workaround is to replace all occurrences of wp.hooks with wp.acf_hooks within the file /plugins/advanced-custom-fields-pro/assets/js/acf-input.min.js

rchipka commented Apr 17, 2018

@CreativeDive This is because ACF overwrites the window.wp.hooks object, causing various functions to be undefined or redefined in an incompatible way.

A workaround is to replace all occurrences of wp.hooks with wp.acf_hooks within the file /plugins/advanced-custom-fields-pro/assets/js/acf-input.min.js

@CreativeDive

This comment has been minimized.

Show comment
Hide comment
@CreativeDive

CreativeDive Apr 17, 2018

@rchipka Thanks for helping, but I will wait for the fix by @elliotcondon

CreativeDive commented Apr 17, 2018

@rchipka Thanks for helping, but I will wait for the fix by @elliotcondon

@rchipka

This comment has been minimized.

Show comment
Hide comment
@rchipka

rchipka Apr 17, 2018

@CreativeDive Actually, wp.hooks is no longer overwritten in version 5.6.10

Unfortunately, it defaults to the existing (incompatible) wp.hooks functions instead of creating its own acf_hooks object.

This means that Gutenberg hooks will now work, but all ACF hooks will be broken.

The problem is that the existing Gutenberg JavaScript WP hooks API requires the use of a namespace parameter when interfacing with hooks, so ACF's hook API calls would have to be converted over to the new Gutenberg compatible calls.

As long as ACF continues to package its own JS hook/event management system with each release, it should really just put everything into its own acf_hooks object until its ready to integrate with the existing API and remove the packaged one.

rchipka commented Apr 17, 2018

@CreativeDive Actually, wp.hooks is no longer overwritten in version 5.6.10

Unfortunately, it defaults to the existing (incompatible) wp.hooks functions instead of creating its own acf_hooks object.

This means that Gutenberg hooks will now work, but all ACF hooks will be broken.

The problem is that the existing Gutenberg JavaScript WP hooks API requires the use of a namespace parameter when interfacing with hooks, so ACF's hook API calls would have to be converted over to the new Gutenberg compatible calls.

As long as ACF continues to package its own JS hook/event management system with each release, it should really just put everything into its own acf_hooks object until its ready to integrate with the existing API and remove the packaged one.

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Apr 17, 2018

Owner

Hi guys

Thanks for the notifications.
Yes, I'm aware of the wp.hooks issues with Gutenberg and have opened a ticket with the core team: WordPress/gutenberg#6091

For now, I plan to move the ACF hooks into the acf JS object and avoid any conflicting 3rd party libraries.

Owner

elliotcondon commented Apr 17, 2018

Hi guys

Thanks for the notifications.
Yes, I'm aware of the wp.hooks issues with Gutenberg and have opened a ticket with the core team: WordPress/gutenberg#6091

For now, I plan to move the ACF hooks into the acf JS object and avoid any conflicting 3rd party libraries.

@mdgmichael

This comment has been minimized.

Show comment
Hide comment
@mdgmichael

mdgmichael Aug 3, 2018

Hi! I'm very curious about whether/how this has progressed—either in @rchipka’s plugin or in ACF core. My team has a library of custom block types that we've built over the years using ACF's Flexible Content fields, and we're eager to convert them into Gutenberg blocks.

My instinct at this moment is that @rchipka has the right fundamental approach: find a way to place an ACF field group in the settings for a block type, and save the values to the block's attributes as JSON. (I tried using his plugins in our sandbox, but they were last updated in April and I don't think they've survived the last few rounds of WP/Gutenberg updates.)

I also know @elliotcondon was working on a parallel track. Has there been any update on details and/or when we might get our hands on it?

Thanks to all from a massive ACF fan.

mdgmichael commented Aug 3, 2018

Hi! I'm very curious about whether/how this has progressed—either in @rchipka’s plugin or in ACF core. My team has a library of custom block types that we've built over the years using ACF's Flexible Content fields, and we're eager to convert them into Gutenberg blocks.

My instinct at this moment is that @rchipka has the right fundamental approach: find a way to place an ACF field group in the settings for a block type, and save the values to the block's attributes as JSON. (I tried using his plugins in our sandbox, but they were last updated in April and I don't think they've survived the last few rounds of WP/Gutenberg updates.)

I also know @elliotcondon was working on a parallel track. Has there been any update on details and/or when we might get our hands on it?

Thanks to all from a massive ACF fan.

@coollorenzo

This comment has been minimized.

Show comment
Hide comment
@coollorenzo

coollorenzo Aug 3, 2018

Yeah would love if ACF flexible content would become and easy way to add custom Gutenberg blocks. Just what I need as a webdesigner

coollorenzo commented Aug 3, 2018

Yeah would love if ACF flexible content would become and easy way to add custom Gutenberg blocks. Just what I need as a webdesigner

@jcklpe

This comment has been minimized.

Show comment
Hide comment
@jcklpe

jcklpe Aug 4, 2018

Hey, I've been out of the loop on WP stuff because I've been working on some backend projects but I plan on making some huge updates in the next couple of weeks, and would love to give these plugins a whirl. I'll take a look at the Advanced Custom Blocks plugin github myself but hearing about the process from the devs themselves would also be helpful, as I'm still pretty limited in my code skills (but getting better everyday!)

Thank you!

jcklpe commented Aug 4, 2018

Hey, I've been out of the loop on WP stuff because I've been working on some backend projects but I plan on making some huge updates in the next couple of weeks, and would love to give these plugins a whirl. I'll take a look at the Advanced Custom Blocks plugin github myself but hearing about the process from the devs themselves would also be helpful, as I'm still pretty limited in my code skills (but getting better everyday!)

Thank you!

@samuel-hauser

This comment has been minimized.

Show comment
Hide comment
@samuel-hauser

samuel-hauser Aug 8, 2018

Check the ShopTalk with Elliot Condon: https://t.co/t2toSDaSzY

samuel-hauser commented Aug 8, 2018

Check the ShopTalk with Elliot Condon: https://t.co/t2toSDaSzY

@RevConcept

This comment has been minimized.

Show comment
Hide comment
@RevConcept

RevConcept Aug 8, 2018

@samuel-hauser thanks for sharing that!

First, off - I am 100% of the same mindset Elliot is with what ACF "is" and how much is should have nothing to do with the Gutenberg updates...that's the biggest thing I don't understand about this whole plan...there are SO MANY developers using WP in a way that has nothing to do with posts and blogs in a traditional sense, and a glorified page builder is not what my client base needs or wants.

Second, it was such a relief to here that ACF will for sure remain stable and hopefully adapt at some point...but the passion behind it from Elliot is what I liked best! My entire business is built on top of that plugin, ha. That's not to say we wouldn't adapt...but why mess with perfection??

*Also cannot believe that Auttomattic has never approached him, at all?! Maybe they really are that out of touch with what WP devs are doing...

RevConcept commented Aug 8, 2018

@samuel-hauser thanks for sharing that!

First, off - I am 100% of the same mindset Elliot is with what ACF "is" and how much is should have nothing to do with the Gutenberg updates...that's the biggest thing I don't understand about this whole plan...there are SO MANY developers using WP in a way that has nothing to do with posts and blogs in a traditional sense, and a glorified page builder is not what my client base needs or wants.

Second, it was such a relief to here that ACF will for sure remain stable and hopefully adapt at some point...but the passion behind it from Elliot is what I liked best! My entire business is built on top of that plugin, ha. That's not to say we wouldn't adapt...but why mess with perfection??

*Also cannot believe that Auttomattic has never approached him, at all?! Maybe they really are that out of touch with what WP devs are doing...

@eliot-akira

This comment has been minimized.

Show comment
Hide comment
@eliot-akira

eliot-akira Aug 8, 2018

Here's a link to directly listen to the relevant portion of the ShopTalk podcast:

http://shoptalkshow.com/episodes/323-acf-elliot-condon/#t=39:57

eliot-akira commented Aug 8, 2018

Here's a link to directly listen to the relevant portion of the ShopTalk podcast:

http://shoptalkshow.com/episodes/323-acf-elliot-condon/#t=39:57

@mdgmichael

This comment has been minimized.

Show comment
Hide comment
@mdgmichael

mdgmichael Aug 9, 2018

Whoah! Ask and ye shall receive: https://www.advancedcustomfields.com/blog/the-state-of-acf-in-a-gutenberg-world/

This is exactly what I was hoping for, and we barely even have to wait for it. I'm legit excited to start using ACF Blocks. Thank you, @elliotcondon! This ACF Pro customer is very happy!

mdgmichael commented Aug 9, 2018

Whoah! Ask and ye shall receive: https://www.advancedcustomfields.com/blog/the-state-of-acf-in-a-gutenberg-world/

This is exactly what I was hoping for, and we barely even have to wait for it. I'm legit excited to start using ACF Blocks. Thank you, @elliotcondon! This ACF Pro customer is very happy!

@justiny

This comment has been minimized.

Show comment
Hide comment
@justiny

justiny Aug 13, 2018

Perhaps I'm missing something here, but I'm not seeing the location > rules > field group option for "Block". Is there a function that needs added for that option to show?
acf-gutenberg-blocks-2

justiny commented Aug 13, 2018

Perhaps I'm missing something here, but I'm not seeing the location > rules > field group option for "Block". Is there a function that needs added for that option to show?
acf-gutenberg-blocks-2

@elliotcondon

This comment has been minimized.

Show comment
Hide comment
@elliotcondon

elliotcondon Aug 14, 2018

Owner

Hi Guys.

The upcoming "ACF Blocks" feature is in it's infancy and has not yet been included in the public version. Stay tuned to our blog for updates on this new feature! We plan to have this out in the next month or two :)

Owner

elliotcondon commented Aug 14, 2018

Hi Guys.

The upcoming "ACF Blocks" feature is in it's infancy and has not yet been included in the public version. Stay tuned to our blog for updates on this new feature! We plan to have this out in the next month or two :)

@enoversum

This comment has been minimized.

Show comment
Hide comment
@enoversum

enoversum Aug 22, 2018

@elliotcondon Will there be or is there some kind of early-access-beta-try-before-you-die for the blocks feature? Eagerly awaiting its arrival!

enoversum commented Aug 22, 2018

@elliotcondon Will there be or is there some kind of early-access-beta-try-before-you-die for the blocks feature? Eagerly awaiting its arrival!

@craigpearson

This comment has been minimized.

Show comment
Hide comment
@craigpearson

craigpearson Aug 22, 2018

It'd be really beneficial to get early access to this if possible. Mainly because it sounds exciting, but more importantly so we can start planning in any needed refactors and what they may look like across installations. At the moment we're leaning towards embracing Gutenberg alone for layouts, but it'd be nice to show the team that we don't have to

craigpearson commented Aug 22, 2018

It'd be really beneficial to get early access to this if possible. Mainly because it sounds exciting, but more importantly so we can start planning in any needed refactors and what they may look like across installations. At the moment we're leaning towards embracing Gutenberg alone for layouts, but it'd be nice to show the team that we don't have to

@TwoPaperdolls

This comment has been minimized.

Show comment
Hide comment
@TwoPaperdolls

TwoPaperdolls Aug 22, 2018

You might want to leave a note on the blog post that block isn't available in the location rules yet.

I spent a while chasing my tail trying to figure out what I was doing wrong until I finally came here to see what was up. I had enabled early access and it wasn't available for me either.

TwoPaperdolls commented Aug 22, 2018

You might want to leave a note on the blog post that block isn't available in the location rules yet.

I spent a while chasing my tail trying to figure out what I was doing wrong until I finally came here to see what was up. I had enabled early access and it wasn't available for me either.

@adamr415

This comment has been minimized.

Show comment
Hide comment
@adamr415

adamr415 Aug 23, 2018

Yes, the blog post is a bit miselading since there is even a code example included. I too jumped right in then scratched my head a while.

adamr415 commented Aug 23, 2018

Yes, the blog post is a bit miselading since there is even a code example included. I too jumped right in then scratched my head a while.

@rchipka

This comment has been minimized.

Show comment
Hide comment
@rchipka

rchipka Aug 23, 2018

For those who want to start using something like this right away, you may want to check out the latest version of rchipka/advanced-custom-blocks.

Add a block and target location

screen shot 2018-08-23 at 7 23 20 pm

Block location rules work for Block Name as well as others (like Post Type).

Set block name and icon

screen shot 2018-08-23 at 7 23 33 pm

Block Name is defined at the bottom of the Field Group settings page as well as an optional custom Block Icon (using dashicons slug).

Select our block

screen shot 2018-08-23 at 7 13 59 pm

We can select our block under Widgets by default. As you can see, our block takes on the Field Group name and the custom icon.

Post edit screen

screen shot 2018-08-23 at 7 21 38 pm

Our block takes on all the Field Group fields and layout. Here we have two Testimonial blocks inside of a Columns block.

Note that we're able to seamlessly add (and render) multiple instances of the same fields on the same post type (even though it's not a repeater field!). This allows the user to create their own custom repeater-like layout.

Render your block

Note that in order for our block to become available in the Gutenberg editor, we never had to write any code to actually register that block.

This implementation does not require any custom block registration mechanism ahead of time. Instead it simply creates the block and uses a filter for rendering that block's content.

Filters:

add_filter('acf/render_block', function ($output, $attributes) {
add_filter('acf/render_block/name=block_name', function ($output, $attributes) {

<?php
add_filter('acf/render_block/name=testimonial', function ($output, $attributes) {
  ob_start();
  ?>
  <div class="testimonial">
    <img src="<? the_field('avatar'); ?>" />
    <h3><? the_field('author'); ?></h3>
    <span><? the_field('testimonial'); ?></span>
  </div>
  <?
  return ob_get_clean();
}, 10, 2);

Note: For even simpler block templating, an extension could be created that hooks render_block and attempts to auto-load a block template from within a directory like blocks/block-name.php.


TODO:

  • Built-in block template targeting (blocks/block-name.php)
  • Store ACF field data in block attributes (in addition to post_meta)
  • Allow customizing the block's group (right now it's in Widgets)
  • Add block location rule restrictions based on parent's "Block Name"
  • Register new field type "Gutenberg Blocks" so that we can nest blocks as fields
  • Enable sidebar position for field group
  • Add block count restrictions

rchipka commented Aug 23, 2018

For those who want to start using something like this right away, you may want to check out the latest version of rchipka/advanced-custom-blocks.

Add a block and target location

screen shot 2018-08-23 at 7 23 20 pm

Block location rules work for Block Name as well as others (like Post Type).

Set block name and icon

screen shot 2018-08-23 at 7 23 33 pm

Block Name is defined at the bottom of the Field Group settings page as well as an optional custom Block Icon (using dashicons slug).

Select our block

screen shot 2018-08-23 at 7 13 59 pm

We can select our block under Widgets by default. As you can see, our block takes on the Field Group name and the custom icon.

Post edit screen

screen shot 2018-08-23 at 7 21 38 pm

Our block takes on all the Field Group fields and layout. Here we have two Testimonial blocks inside of a Columns block.

Note that we're able to seamlessly add (and render) multiple instances of the same fields on the same post type (even though it's not a repeater field!). This allows the user to create their own custom repeater-like layout.

Render your block

Note that in order for our block to become available in the Gutenberg editor, we never had to write any code to actually register that block.

This implementation does not require any custom block registration mechanism ahead of time. Instead it simply creates the block and uses a filter for rendering that block's content.

Filters:

add_filter('acf/render_block', function ($output, $attributes) {
add_filter('acf/render_block/name=block_name', function ($output, $attributes) {

<?php
add_filter('acf/render_block/name=testimonial', function ($output, $attributes) {
  ob_start();
  ?>
  <div class="testimonial">
    <img src="<? the_field('avatar'); ?>" />
    <h3><? the_field('author'); ?></h3>
    <span><? the_field('testimonial'); ?></span>
  </div>
  <?
  return ob_get_clean();
}, 10, 2);

Note: For even simpler block templating, an extension could be created that hooks render_block and attempts to auto-load a block template from within a directory like blocks/block-name.php.


TODO:

  • Built-in block template targeting (blocks/block-name.php)
  • Store ACF field data in block attributes (in addition to post_meta)
  • Allow customizing the block's group (right now it's in Widgets)
  • Add block location rule restrictions based on parent's "Block Name"
  • Register new field type "Gutenberg Blocks" so that we can nest blocks as fields
  • Enable sidebar position for field group
  • Add block count restrictions
@jcklpe

This comment has been minimized.

Show comment
Hide comment
@jcklpe

jcklpe Aug 24, 2018

Love it. Going to try this this week. I just finished rebuilding my work computer and just need to get my server connections back up :) Woo!

jcklpe commented Aug 24, 2018

Love it. Going to try this this week. I just finished rebuilding my work computer and just need to get my server connections back up :) Woo!

@jcklpe

This comment has been minimized.

Show comment
Hide comment
@jcklpe

jcklpe Aug 28, 2018

Hey, got Robbie's plugin installed and working, though still working through some possible limitations of use it has for my needs.

That said, and this doesn't do the exact same thing, I thought I should link this other plugin that I found while searching stuff that some people here might find useful: https://github.com/youknowriad/gcf

jcklpe commented Aug 28, 2018

Hey, got Robbie's plugin installed and working, though still working through some possible limitations of use it has for my needs.

That said, and this doesn't do the exact same thing, I thought I should link this other plugin that I found while searching stuff that some people here might find useful: https://github.com/youknowriad/gcf

@jcklpe

This comment has been minimized.

Show comment
Hide comment
@jcklpe

jcklpe Aug 28, 2018

Oooh, actually I just found a plugin that does exactly what I need it to do. Technically it doesn't hook into Advanced Custom Field and it only has text and text area field types but it does what I need it to do and I like the UI a bit more than Robbie's. Maybe it's something that Robbie or Elliott would want to contribute to it or perhaps would find the code useful to their own projects: https://github.com/rheinardkorf/advanced-custom-blocks

It's also got a killer logo, I gotta say.

jcklpe commented Aug 28, 2018

Oooh, actually I just found a plugin that does exactly what I need it to do. Technically it doesn't hook into Advanced Custom Field and it only has text and text area field types but it does what I need it to do and I like the UI a bit more than Robbie's. Maybe it's something that Robbie or Elliott would want to contribute to it or perhaps would find the code useful to their own projects: https://github.com/rheinardkorf/advanced-custom-blocks

It's also got a killer logo, I gotta say.

@adamr415

This comment has been minimized.

Show comment
Hide comment
@adamr415

adamr415 Aug 29, 2018

@rchipka is your project what will be implemented into ACF. I want to get a jump on transitioning my ACF sites but wasn't sure if it was worth the effort until it was finalized into ACF.

adamr415 commented Aug 29, 2018

@rchipka is your project what will be implemented into ACF. I want to get a jump on transitioning my ACF sites but wasn't sure if it was worth the effort until it was finalized into ACF.

@rchipka

This comment has been minimized.

Show comment
Hide comment
@rchipka

rchipka Aug 29, 2018

@adamr415 No, it's a completely separate implementation.

That being said, anything you build using my version can be easily ported over to the ACF implementation based on the examples provided in the blog post.

It would only require the adding acf_register_block for each block as well as updating the location rules to use ACF's "Block Name" rule.

rchipka commented Aug 29, 2018

@adamr415 No, it's a completely separate implementation.

That being said, anything you build using my version can be easily ported over to the ACF implementation based on the examples provided in the blog post.

It would only require the adding acf_register_block for each block as well as updating the location rules to use ACF's "Block Name" rule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment