Summary
When syncing pages between Agility instances via @agility/cli, the dynamic.visibleOnMenu and dynamic.visibleOnSitemap flags on dynamic pages are not preserved from the source instance - both are always written as true on the target instance, regardless of the source value. Non-dynamic (folder/static) pages sync these flags correctly.
Steps to Reproduce
- On a source instance, configure a dynamic page with
visibleOnMenu: false (and optionally visibleOnSitemap: false).
- Run the CLI sync to a target instance.
- Inspect the resulting page definition on the target instance.
Expected Behavior
The target page's dynamic.visibleOnMenu and dynamic.visibleOnSitemap values should match the source instance exactly.
Actual Behavior
Both flags come out as true on the target instance. This was confirmed across multiple dynamic pages and different page templates.
Non-dynamic (folder/static) pages, including one with a mixed menu: false / sitemap: true combination, synced correctly.
Environment
@agility/cli version 1.0.0-beta.13.28
Summary
When syncing pages between Agility instances via
@agility/cli, thedynamic.visibleOnMenuanddynamic.visibleOnSitemapflags on dynamic pages are not preserved from the source instance - both are always written astrueon the target instance, regardless of the source value. Non-dynamic (folder/static) pages sync these flags correctly.Steps to Reproduce
visibleOnMenu: false(and optionallyvisibleOnSitemap: false).Expected Behavior
The target page's
dynamic.visibleOnMenuanddynamic.visibleOnSitemapvalues should match the source instance exactly.Actual Behavior
Both flags come out as
trueon the target instance. This was confirmed across multiple dynamic pages and different page templates.Non-dynamic (folder/static) pages, including one with a mixed
menu: false/sitemap: truecombination, synced correctly.Environment
@agility/cliversion1.0.0-beta.13.28