Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ACF (Pro) fields no longer working as expected #6754

Closed
maddisondesigns opened this issue May 15, 2018 · 1 comment
Closed

ACF (Pro) fields no longer working as expected #6754

maddisondesigns opened this issue May 15, 2018 · 1 comment
Labels
[Status] Needs More Info Follow-up required in order to be actionable. [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.

Comments

@maddisondesigns
Copy link

Describe the bug
ACF Pro (Advanced Custom Fields Pro) fields don't work as expected. I have a number of test ACF fields, including Post Object dropdowns. Two of my Post Object fields are supposed to display a list of WooCommerce Products and another one is supposed to display a list of Pages. None of these Post Object fields display any content

To Reproduce
Steps to reproduce the behavior:

  1. Activate ACF Pro
  2. Create Field group
  3. Add Post Object Field to display on Page
  4. Edit page and try to select an entry from Post Object field

Expected behavior
Post Object fields don't display any content

Screenshots
gutenberg-postobject

Desktop (please complete the following information):
macOS Sierra 10.12.1 (16B2659)
Firefox Quantum 60.0 (64-bit)

Additional context
Created due to #3580 being closed

_Gutenberg 2.8.0
WordPress 4.9.5

Activated plugins:
Advanced Custom Fields PRO 5.6.10
Gravity Forms 2.3.1
Gravity Forms Gutenberg Add-On 1.0-beta-4
WooCommerce 3.3.5
Yoast SEO 7.4.2_
@Soean Soean added the [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes. label May 15, 2018
@danielbachhuber
Copy link
Member

@maddisondesigns Can you share any debugging you've done?

Are these fields powered by the REST API? If so, could this be caused by #6576?

@danielbachhuber danielbachhuber added the [Status] Needs More Info Follow-up required in order to be actionable. label May 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Status] Needs More Info Follow-up required in order to be actionable. [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@danielbachhuber @Soean @maddisondesigns