Idea Board:

Beta
#1
  1. Minor Bug: With ACF’s new bidirectional fields we are able to loop through those connections pretty intuitively using nested loopers. That said, for whatever reason, the bidirectional data disappears in CS preview but is totally functional and visible on the frontend.

Reproduction: Create bidirectional fields > Create Archive > Setup standard consumer > Add div inside of that consumer > Add looper provider to that div accessing the bidirectional field > Add headline with Title dynamic content > Consume (at this point the headline will disappear)

Helped somebody out with this in the video below. You’ll notice the issue at the 2:30 marker.

  1. Potential for Improvement: Have seen this more and more but I think it might be wise to change the permanent document deletion in CS to a soft “trash” deletion. Have seen people make this mistake several times.

Screen Shot 2023-08-29 at 9.55.35 AM

  1. Potential for Improvement: I love the new HTML editor inside of text and headline fields. It would be amazing, however, to be able to pick my default (beyond just Rich Text or not). As I’d still prefer RAW since the text wraps (HTML for paragraph text is tough to work with).

Screen Shot 2023-08-29 at 9.56.29 AM

Screen Shot 2023-08-29 at 9.58.11 AM
Screen Shot 2023-08-29 at 9.58.11 AM721×339 29.6 KB

Screen Shot 2023-08-29 at 9.58.15 AM

  1. Potential for Improvement: Occasionally I’ve seen people (including myself) properly set conditions but forget to set the preview and then they wonder why their Archive or Single Post Layout isn’t loading data. I think the preview pane should attempt to intelligently preset itself based on the layout condition – if set.

For example if I specify that a layout that I’m working in is set to Post Type = Post then the preview pane could automatically set post type = post. If no condition is set, then the standard preview pane functionality makes complete sense.

Screen Shot 2023-08-29 at 10.03.59 AM

1 Like
#2

Agree 100% on the above feedback.

FWIW, for #1, for me, the bidirectional data doesn’t display in the builder for just the first item in the index. Seems to be fine for all the subsequent entries :man_shrugging:

1 Like
#3
  1. I’ll have to take a look at these new field types. Appreciate the notes from both of you!
  2. I think that should be as simple as using this WP function instead of delete. I have a look into this more though.
    https://developer.wordpress.org/reference/functions/wp_trash_post/
  3. Line Wrapping preference for all code editors is something already ready in 6.4 actually. I think we’re going to set this enabled by default too, to keep parity with “Raw”. As for the more granular rich text editor preference part, I think we can get that in during 6.4 beta
  4. I agree this is a pain point for me too. Part of me think it is trying to change the preview based on conditions, it’s just not doing it well enough.

Thanks have a great day!

3 Likes
#4

Thanks @charlie for everything you’re doing to make Pro better than ever. It’s obvious that you have a load of technical skill, combined with an amazing attitude and work ethic! I’m so glad you joined the team.

7 Likes
#5

This 100%+ :tada: — We appreciate you!

1 Like
#6

Thanks for the kind words. More exciting things to come! Have a great weekend.

2 Likes