Hi, thank you for your work on this plugin. I am experiencing a weird issue using the free version. context:
– page is a template for an archive page – in the template a query loop block loads ‘x’ articles – inside the query loop block several MFB blocks load data – some of the MFB blocks load Post meta from the REST api while others from ACF fields
now, in my setup only the data from ACF fields is visible on the frontend. at the same time, inside the FSE editor, all MFB load the proper data (both ACF and Post Meta). is this a bug..?
Thank you for your feedback. Could you please provide me with more details about your issue? I would need several screenshots of the block’s settings or a recorded video of your page from the admin side. Additionally, could you explain how you register your post meta fields?
Hi, thank you for your reply. As I said, the MFB fields are properly populated in the FSE window but not on the frontend. Again, not all of them are affected. Fields pulling ACF data content render just fine while fields set to pull data from the REST API such as ‘id’ or ‘content’ only render in the FSE interface and not in the front-end).
here a view of the FSE window, in the image the selected block is set to pull the ‘id’ field from the rest api and properly does so:
in the following image, the front-end display. the ‘id’ should appear where I inserted the red rectangle with the three ‘?’. while the data in the red rectangle is missing, the green data from ACF fields appears as expected.
inspecting the generated code shows the field is properly rendering the wrapping div elements but albeit without filling it with data:
This reply was modified 8 months, 2 weeks ago by en_fer.
@n_feragnoli Ah, I see now. You want to display core REST fields for posts, such as ID, title, content, etc.? The current version of MFB does not support displaying these core REST fields. Since there are already core blocks available to display post titles and post content, I have not added support for these fields. Could you share some good reasons why you prefer not to use core blocks for these fields?
MFB is going to include support for displaying post title in the next version, however I’m not sure which additional fields should be included in the supported list.
This reply was modified 8 months, 2 weeks ago by Phi Phan.
hello again. ah, I see. I guess I must’ve been confused by the fact that the block control in the inspector allows to select as source the REST API fields (i.e. any field available in the the REST API) and by the fact that those fields are, indeed, rendered in the FSE interface (hence, I take, they’re simply not displayed in the public output of MFB).
Regarding the why: not all REST fields are available in other blocks. the id, for instance (as in my example – although in that case only for demonstration purposes). that said, having a block which – in fact -gives plain and simple access to all REST fields might be handy in several ways (thing that, apparently MFB already does). Furthermore, I think it’d be very confusing to restrict access to REST fields to a selectedsubset of fields (i.e.: here you can query the REST fields but only this, that, and the other one). I expect mostly developer-y people to be oriented towards the use of MFB, thus… people with the knowledge about what REST fields are and what data they hold.
@n_feragnoli Thank you for the insight. The main reason I don’t support displaying all REST fields on the frontend is that we have to manually retrieve the values of those fields for the frontend. While we could display these fields automatically by initializing a REST server, it may impact performance. Therefore, unless there is a good reason to do so, I avoid displaying these core REST fields by default.
I’ve received a request to display the post title, so I will include support for it in the next version.
I’m also having a similar problem but, with ACF fields. I have an archive template that catches any categories or tags, but I can’t show some of the fields from ACF like a post object field and a select field. Is there a workaround for this?
If you place the MFB inside a Query Loop block, it will show the value for the post—not the category or tag. If you want to display the value for a term, you’ll need to place the block outside of the Query Loop.
If you’d like more help, feel free to share an admin account for your site. I’d be happy to take a look at your template. You can send the details to [email protected].
Best, Phi
This reply was modified 6 months, 3 weeks ago by Phi Phan.
I celebrated too early… for some reason when I clear the cache using (LiteSpeed) the ACF fields goes away again in the front-end. Then if I open the post and purge cache the field shows up. Have you received any issues with cache?
@carlbtmn Could you describe what you’re trying to display, a post meta field or a term meta field? Let me know more about your fields so I can better understand the setup.
I haven’t seen any caching issues with this use case so far, however, the field values are cached using object caching behind the scenes.
If you’d like me to take a look at your template, feel free to share an admin account for your staging site.
Viewing 12 replies - 1 through 12 (of 12 total)
The topic ‘Meta fields displaying in FSE editor but not on frontend’ is closed to new replies.
