Releases: limbo-works/Limbo.Umbraco.TwentyThree
v13.0.0
First release for Umbraco 13. This release will not work with other versions of Umbraco.
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 13.0.0
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 13.0.0
v2.0.6
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.6
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.6
Changelog
-
Added album search filter in the video overlay (see 1562dfc)
As part of the video overlay for finding videos, it's now possible to limit the displayed videos to a single album. -
Misc UI improvelements (see cabebc4)
This includes showing the video play count and average play time in the property editor, as well as the video play count in the video overlay.
v2.0.5
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.5
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.5
Changelog
-
Changing the
Credentials
property toList<T>
instead ofIReadOnlyList<T>
as .NET 6 won't populate the property if is has a default value (see #1 and 34c6db7)
For thev2.0.4
, I made a change to theCredentials
property so that the package provides a default value for the property in case no configuration has been added toappsettings.json
. If the default value isn't there, and no configuration has been provided, the property value would end up beingnull
, which would cause null reference errors throughout the package.Setting a default value therefore seemed to fix the issue. But I might have only tested this in Umbraco 12 (.NET 7), and not in Umbraco 10 (.NET 6), as .NET 6 doesn't seem to support this for properties where the type is an interface like
IList<T>
orIReadOnlyList<T>
.Therefore, the fix changes the property type to a
List<T>
in which case the property is correctly populated in both .NET 6 and .NET 7. -
Updated controller to send photo token to the TwentyThree API (see #2 and e2c281b)
If a token is specified as part of the input (embed code), we should make sure to send that token to the TwentyThree API along with the photo ID. This means that we can fetch information about the photo/video even if the API user doesn't have access to the video.
v2.0.4
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.4
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.4
Changelog
-
Updated the upper bound for the Umbraco dependencies to allow using the package with Umbraco 12 (see 0ee9826)
As Umbraco 12 was released earlier this month, and no changes are required for the package to run on Umbraco 12, the upper bound of the Umbraco dependencies has been raised to allow running on Umbraco 12. -
Updated package manifest filter to set
PackageId
property in Umbraco 12 (see 7bf5dcd)
In Umbraco 12, thePackageManifest
clas now has aPackageId
property to indicate the NuGet ID of a package. As of this release, the package uses reflection to set this property when the package is used with Umbraco 12. -
Fixed
TwentyThreeSettings.Credentials
default value (see 475ec4c)
The default value should be an emptyIReadOnlyList<TwentyThreeCredentials>
instead ofnull
. Otherwise the package will fail in different parts when configuration for the package hasn't been added toappsettings.json
. -
Updated the Limbo.Umbraco.Video dependency (see dd142cf)
Might as well reference the newest version.
v2.0.3
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.3
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.3
Changelog
-
Video overlay now shows video descriptions by default (see c66d4d3)
The overlay for selecting a video now shows a description for each video when available. Since descriptions can be quite long, a new Max description length option has been introduced on the content type. -
Misc UI improvements and localization (see 06184d7)
More parts of the property editor and related overlays are now localized and translated to Danish. -
Added support for custom credentials icons (see 303e8fd)
When multiple credentials are configured for the package, the user has to select an account (credentials) before being able to pick a video or spot. With this release, it's now possible to specify an icon for each credentials / account, which will then be shown in the account picker overlay. -
Improved error handling (see 6cd5cc1)
The package is now better at showing error messages to the user, and exception messages written to the Umbraco log now contain a bit more details. -
Added video description to property editor (see c11c95a)
The property editor will now also shown the video's description if available.
v2.0.2
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.2
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.2
Changelog
- Implemented new upload link feature (see 9e8cada)
TwentyThree supports creating an upload page in their end, so this feature adds support for showing a "Upload video" link in the property editor, which after selecting one of the configured accounts, will take the user to the upload page. This feature does not allow uploading videos directly from Umbraco.
v2.0.1
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.1
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.1
Changelog
- Updated the Skybrud.Social.TwentyThree dependency
TheSkybrud.Social.TwentyThree
package handles the underlying communication with TwentyThree API. The newest version of the package contains a fix since the TwentyThree API is now returning timestamps as floating point numbers instead of integers.
v2.0.0
v2.0.0-alpha004
New alpha release 🎉
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.0-alpha004
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.0-alpha004
Changelog
-
Property editor constants should be public (see 4a4555a)
Making the constants public means they can be accessed from outside of the package. -
Static create methods should be public (see 9c632f0)
In some cases we might need to create new instances from outside of the package, so the two staticCreate
methods are now public.
v2.0.0-alpha003
New alpha release 🎉
Installation
To install the package via NuGet, you can use either .NET CLI:
dotnet add package Limbo.Umbraco.TwentyThree --version 2.0.0-alpha003
or the older NuGet Package Manager:
Install-Package Limbo.Umbraco.TwentyThree -Version 2.0.0-alpha003
Changelog
-
Fixed issue with wrong JSON property name for
TwentyThreeConfiguration.AllowSpots
property (see 39d99b0) -
Updated Skybrud.Social.TwentyThree dependency (see 0a25ef5 and 7ad1d52)
The package is now usingv1.1.1
instead ofv1.1.0-beta001
. -
Video duration is now specified in seconds when serializing to JSON (see 81b2c38)
TheTwentyThreeVideoDetails
class contains a property that exposes the video's duration as aTimeSpan
. When serialized to JSON, the value would be equal to callingToString()
on theTimeSpan
. As of this release, the duration is now instead specified in seconds. -
Added logic to mitigate bad string
"null"
values (see 383944d, 59a1afe)
If the user hasn't selected a video, we should ideally save anull
value indicating that the property doesn't have a value. But Umbraco will convert an actualnull
value to a string containing the value"null"
, which then gives a different meaning, and causes a number of Angular errors when interacting with the property editor. -
Added delay to input field so we don't spam the server if user enters URL manually (see 7f247e1)
By adding a small delay, we won't make requests to the server until the user has stopped entering. This therefore potentially reduces the amount of requests to the server, but also ensure the user won't see an error for each key stroke if they are entering the URL manually.