This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 10:00 – 13:00 | 10:00 – 13:00 | 10:00 – 13:00 | 10:00 – 13:00 | 10:00 – 13:00 | - |
| - | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | 14:00 – 18:00 | - |
Zeitzone des Unterstützers: Asia/Kolkata (GMT+05:30)
Dieses Thema enthält 2 Antworten, hat 1 Stimme.
Zuletzt aktualisiert von vor 14 hours, 14 minutes.
Assistiert von: Minesh.
Environment:
WordPress 7.0, PHP 8.4.23
Toolset Types 3.6.2
Toolset Blocks 1.6.24
Theme: Refined Magazine Pro 1.2.1
Cache: WP Super Cache disabled for testing, issue persists (so it doesn't appear to be a caching issue)
Description:
I have a View with a Loop on the custom post type "Bibliografie". Inside the View Loop, there's a Paragraph block using mixed static/dynamic text via the inline field option, for example:
Edito da [editore_biblio] in [citta_biblio] | [pubblicazione_biblio], del [anno_biblio] | argomento: [argomento_biblio]
Inspecting the generated HTML, each inline field span has:
htmldata-provider="__current_post" data-source="editore_biblio" ...
Observed behavior:
Editor (Gutenberg): in the first loop item, the inline fields are populated correctly; from the second item onward they stay empty.
Frontend: the inline fields are empty for all items in the loop, including the first one (see screenshot of the page versteckter Link).
In both contexts, replacing the same field with a separate native "Single Field" block (not inline, not inside a paragraph) correctly retrieves the value for every loop item.
Possible explanation (unconfirmed):
I noticed the data-provider="__current_post" attribute and wondered whether it might indicate the inline field is bound to the currently viewed/edited post rather than to the context of the specific View Loop item it's placed in — unlike Single Field blocks, which do resolve correctly per loop item. That said, I'm not certain this is actually the cause, just a pattern I noticed while inspecting the markup — I'd appreciate your team's read on whether this is relevant or a red herring.
Request:
Could you please check whether this is a known issue with using inline fields inside a Paragraph block when placed within a View Loop? Ideally the inline field should resolve per loop item (like Single Field does), which would let us build mixed static/dynamic text (e.g. "Edito da [field] in [field]") that isn't currently achievable with standalone Single Field blocks alone.
Reference link: versteckter Link
