You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the "status" mapping in a feed's settings is for an element's global status and there is no option to map per-site statuses.
This is also a bit confusing because a feed can target a site, so it appears you're targeting the site-specific status of the element.
This can be worked around by listening to EVENT_STEP_BEFORE_ELEMENT_SAVE and running custom site status logic, but it would be good to support this natively.
This discussion was converted from issue #817 on August 13, 2021 20:04.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description
Currently, the "status" mapping in a feed's settings is for an element's global status and there is no option to map per-site statuses.
This is also a bit confusing because a feed can target a site, so it appears you're targeting the site-specific status of the element.
This can be worked around by listening to
EVENT_STEP_BEFORE_ELEMENT_SAVEand running custom site status logic, but it would be good to support this natively.Beta Was this translation helpful? Give feedback.
All reactions