Heres the source https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Web.UI.Client/src/packages/documents/documents/workspace/actions/save.action.ts

❤️ You're my hero, I will get reading, thak you

Do you know of any git repos out there doing anything similar I could look at ?

Afraid not - but ask away in the forums if you need help.

SeoToolkit actually does this. So in https://github.com/patrickdemooij9/SeoToolkit.Umbraco/blob/dev/main/src/SeoToolkit.Umbraco.Common/assets/src/manifests/seoToolkitContentManifests.ts, you can see that I define a ManifestWorkspaceAction which overwrites the Umbraco save one. So the save and publish then calls this action here: https://github.com/patrickdemooij9/SeoToolkit.Umbraco/blob/dev/main/src/SeoToolkit.Umbraco.Common/assets/src/actions/saveAndPublishDocumentAction.ts

@User Note that making your thing overwrite would be more correct. In that way you would no permantly unregistere the core save button, but instead your thing would take its place if its going to be shown. This is relevant if you added conditions to yours. I hope that helps, and that is also what the Seo toolkit does. Read more here: https://docs.umbraco.com/umbraco-cms/16.latest-rc/customizing/extending-overview/extension-registry/replace-exclude-or-unregister

Does anyone has any experience with this Umbraco MCP package? Im currently testing it out but would be really intersted to set it up in a hosted Staging environment for testing. But the open SSE Path which can not be secured through and API Key gives me some headaches. Can anyone or the package developer help me out here? https://www.nuget.org/packages/Axendo.ModelContextProtocol.Umbraco

Package devs are you doing package ranges to ensure your package only installs for a certain major? Such as this

[15.0.0,16.0.0)

to allow it only to be installed for any Umbraco site between greater than 15 but less than 16 for example?!

Currently we dont, but for newer packages we want to align them with umbraco version numbers and then it would make sense to limit them to the major

Yeh that’s my thinking

I was considering just keeping it to version 1, 2, 3...etc, but its confusing what version works on what Umbraco version. But the idea was that if it just works on the next Umbraco, why bother with updating it

As the client stuff is moving fast I am not sure it’s always gonna work going up like the c# stuff

But on the other hand, you want to check if it works on the new umbraco anyway, so it's really a small step to update the version number while checking

I have done for CSP manager, I also made it impossible to install once...

Install once?! What it self destructs if you try to install it a 2nd time?! 🙃

I had to put a patch out as I got the (] mess up

who needs a csp anyway 🔓 😂

So what is the correct syntax?!

My packages all use

Version="[15.0.0, 16.0.0)"

Use

Version="[15.0.0, 99.0.0)"

- future proof! 😂

In 42 years, we'll reach version 100 😆

My packages just have a minimum version. More often than not, they work on the next major version too, and then it would be hassle to have to release a new version just to bump the dependency. Or having to fend off support requests asking for a new release for vX.

Fair, but if the package does NOT work in the new version, how will you handle that? Retroactively add a maximum version? Of just tell them they have to update? I personally think that updating a version number twice a year is not that much of a hassle to be honest.

Official support is (from the start) the minimum dependency. Once it surfaces that a newer version doesn't support, I'll put a notice in the README and (maybe) start working on a new version. Most often I find out myself if something is broken in a newer version, I don't have Jump/Kelleher level popular packages 🙂

hi! do you know if there is any way to get a document type by an alias via the management api? thanks!

🔔 Just a heads up, many of you have already moved your questions over to the forum and I can see healthy activity on the

extending

https://forum.umbraco.com/tag/extending and

packages

https://forum.umbraco.com/tag/packages tags! 🎉 🗄️ This channel will be archived early next week, so make sure you keep on asking your package dev questions on the forum. Thanks!

Hi Umbracians, Just wondering if anyone could help me with an issue I am experiencing with Umb 15 Backoffice, I've been trying to create a package and am using workspaces. It worked fine before, but recently I moved file locations and added extra projects to the solution. Since then, I can't seem to get the WorkspaceViews to work, even though they're the same code all I did was move them around. Not sure if 15 has a cache or something similar? I've ensured the manifest files are being compiled correctly and doesn't seem to have any logs/errors in console. Also, the workspace works, it's just with a headline and a blank canvas (Was expecting content apps (WorkspaceViews) to be there as they were previously) - Any help on this would be much appreciated.

Make sure you disable your browser cache

That has caught me out too many times

Every refresh I do is always with the clear everything (cache, etc...). It happens too many times 😛