* Initial commit of changes
* final touches on styling
* Refactored to observe and resolve the document/media node names
---------
Co-authored-by: DESKTOP-16T01G5\Umbraco <obk@umbraco.dk>
Co-authored-by: leekelleher <leekelleher@gmail.com>
* Initial stab at how this could look
* Authorization PoC wip
* Add connection manager
* Add DI to its own class
* Use enum instead of string
* Use groups
* Refactor group management into its own service
* Update a users groups when it's saved
* Add saved events
* Wire up deleted notifications
* Ensure update date and create date is the same
* Cleanup
* Minor cleanup
* Remove unusued usings
* Move route to constant
* Add docstrings to server event router
* Fix and suppress warnings
* Refactor to authorizer pattern
* Update EventType
* Remove unused enums
* Add trashed events
* Notify current user that they've been updated
* Add broadcast
We don't need it, but seems like a thing that a server event router should be able to do.
* Add ServerEventRouterTests
* Add ServerEventUserManagerTests
* Use TimeProvider
* Remove principal null check
* Don't assign event type
* Minor cleanup
* Rename AuthorizedEventSources
* Change permission for relations
* Exctract event authorization into its own service
* Add some tests
* Update name
* Add forgotten file
* Rmember to add to DI
* Render all URLs in document workspace info tab and ensure protocol-less links can be used to access the intended URL.
* Removed unused import.
* Removed scheme from resolved URL.
* Reload children of destination after duplicate of content.
* Revert changes to generic duplicate to action.
* Don't assume entity type of duplicated item is the same as the destination. Instead treat as "document" unless destination unique is null, when it will be "document-root".
* add todo back
* remove console log
---------
Co-authored-by: Mads Rasmussen <madsr@hey.com>
* Display variant selection on unpublish only if the document is variant.
* Allow for publish and unpublish of variant and invariant content.
* Added integration tests for amends to ContentPublishingService.
* Fixed assert.
* Fixed assert and used consistent language codes.
* Further integration tests.
* Added create date to document and media children endpoints.
* Sort by name or create date for documents and media.
* Fix build issues.
* Only render column headers for sorting if all pages of children are loaded.
* Add indicator and debounce sorting by column headers.
* Expose schedule date for on document get endpoint
* typo fix
* stupid stuff
* Enable content scheduling features in the publishing service
* Replace obsoleted non async calls
* Add content scheduling test
* Publush and schedule combination test
* More invariantCulture notation allignment and more tests
* Link up api with updated document scheduling
* More invariant culture notation allignment
* Fix breaking change
* Return expected status codes.
* Fix constructor
* Forward Default implementation to actual core implementation
Co-authored-by: Bjarke Berg <mail@bergmania.dk>
* Forward default implementation to core implementation
Co-authored-by: Bjarke Berg <mail@bergmania.dk>
* Make content with scheduling retrieval scope safe
---------
Co-authored-by: Bjarke Berg <mail@bergmania.dk>
* Use data type configuration to determine default value for empty toggle property values.
* Added/updated unit tests.
* Fixed failing integration tests.
* Applied similar default value display for the slider property editor and aligned implementation of true/false with this.
* Fixed unit tests.
* Removed "duplicate" JsonPropertyName attributes and added a custom TypeInfoResolver for data type configuration so we can re-use the existing ConfigurationField attributes.
* Minor cleanup
---------
Co-authored-by: nikolajlauridsen <nikolajlauridsen@protonmail.ch>
* Don't allow create when there is validation errors
* Fix tests
* Add tests
* Fix last test
* Fix more tests
---------
Co-authored-by: Jacob Overgaard <752371+iOvergaard@users.noreply.github.com>
* feat: include the option whether a login provider has disabled local login
* feat: include information whether change password or two factor is allowed
* generate new OpenApi.json
* generate new ts client
* feat: request the server configuration and include in the UmbAppContext
* fix: for login screen, check that a provider did not disable the local login
* fix: use UmbAppContext to fetch the version check period
* chore: remove unused method
* revert current user configuration changes
* generate new ts client
* fix: add condition for "allow password change" on the change password button
* fix: create new IsDefaultKind condition to separate change password logic
* fix: update "allow change password" and "allow mfa" conditions to take the user configuration into consideration
* chore: export consts
* remove falsely named attribute that happens to not be useful anyway
* chore: revamp logic for early return to make it more readable
* convert `isInitialized` to a Promise as it is only being resolved once anyway, which then additionally saves a call to `this.observe` in the conditions
---------
Co-authored-by: Niels Lyngsø <nsl@umbraco.dk>
* Add notification handler
* Add IsContentPublished that bypasses caching
* Add clarifying comment
* Refactor, to never hit the db
* Remove old comment
* Don't add warnings if disabled
* Dedicated configuration option to suppress unroutable content warnings
---------
Co-authored-by: kjac <kja@umbraco.dk>
* Ensure sort order is used when rendering the list of allowed documents that can be created under an item in the content section.
* Fixed issue preventing sorting of the allowed content types.
