* add button group for multiple preview urls
* generate default + sub buttons for urls
* allow button group to render label without a localisation key
* remove the existing preview button
* add data-element attr for buttons for tours + tests
* use info button style
* set the target of the new window
* get the additional preview urls from the active variant
* Revert "Make sure the property editor layout is contained within its container (prevent Z-index bleed-through) (#13583)"
This reverts commit 8463d906a7.
* remove seemingly unused attribute readonly
* contain everything with contain:layout
this is set if the property editor is in preview mode to make sure all overlays work
* Revert "remove seemingly unused attribute readonly"
This reverts commit 7a2743e8f664e707e8df5022fe754dfd77c508ea.
* Added a longer timeout for the tests. Also bumped the timeout for isSuccessNotificationVisible
* Added a longer timeout for our tests and the isSuccessNotificationVisible method
* Updated the locator for the flaky test. The locator we had before could sometimes find two elements, which resulted in flaky tests.
* Bumped version of playwright
* Updated to use isSuccessNotificationVisible()
* Added a wait for timeout
* Updated to use isSuccessNotificationVisible()
* Bumped the timeouts
* Bumped our timeouts
* Bumped version of our testhelpers
* Updated the button for save and publish and added an wait for timeout
* Added a missing save for the test
* The test could sometimes find two locators. It should be fixes now
* Removed old usage of notification to be visible
* Removed unnecessary timeouts since we have defined the timeouts in the test helpers
* Added test for checking if a settings model contains default value.
Fixed tests
* Bumped version
* Moved createSliderWithDefaultValue function to our testHelpers. Removed the use of count in test since there was only one
Sometimes a tab, e.g. a "block list settings model" might register some default values, but if the user never clicks on the tab then they are not registered due to how AngularJS renders views with "ng-if".
* Added test for checking if a settings model contains default value.
Fixed tests
* Bumped version
* Moved createSliderWithDefaultValue function to our testHelpers. Removed the use of count in test since there was only one
Sometimes a tab, e.g. a "block list settings model" might register some default values, but if the user never clicks on the tab then they are not registered due to how AngularJS renders views with "ng-if".
* WIP: Fix publish descendants and related notifications
* Removed related entitities from publish notification
* Fixed root not being saved when publishingWithDescendants
* Updated integrationtests to reflect the update view on when to save the root when its part of a branch
* PR formatting fix
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
* PR Cleanup
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
* Spicing up the codebase with some PR pattern matching
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
---------
Co-authored-by: Sven Geusens <sge@umbraco.dk>
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
* WIP: Fix publish descendants and related notifications
* Removed related entitities from publish notification
* Fixed root not being saved when publishingWithDescendants
* Updated integrationtests to reflect the update view on when to save the root when its part of a branch
* PR formatting fix
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
* PR Cleanup
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
* Spicing up the codebase with some PR pattern matching
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
---------
Co-authored-by: Sven Geusens <sge@umbraco.dk>
Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
* Revert "Change default UpgradeUnattended value to true (#13281)"
This reverts commit e5d6372dbd.
* Set UpgradeUnattended value to true for new projects
* Revert "Change default UpgradeUnattended value to true (#13281)"
This reverts commit e5d6372dbd.
* Set UpgradeUnattended value to true for new projects
This is needed so it can be used as a discriminator field by System.Text.Json
Changed both ApiElement and IApiElement to ensure not only ApiContentResponse,
but also ApiBlockItem, which uses the interface directly, are adjusted.
* don't set label key to entire content model...
* Remove the default parameter value
---------
Co-authored-by: kjac <kja@umbraco.dk>
(cherry picked from commit 5dfb914e0f)
