piranha | High performance scripting and specification language

Just in case this helps someone. Turns out I did a poor job merging the two blocks together. Chalk this one up to inexperience with both Piranha and Vue.js. I was mixing the code from the docs with the code in the repo. Don't do that - the docs are understandably still a bit behind. I'm not throwing stones at the developers, I really dig what they've created and will continue to put forth the effort to use it proficiently.

Below is what I came up with for the Vue component. There are probably still a few tweaks to be made to separate the Image-Block and Html-Block code better, but it now works, saves, and does not throw errors in the console.

At the moment neither Fields or Blocks supports parameter injection into the constructor, however Fields have two initialization methods that both supports parameter injection, Init() and InitManager(). Given how models are constructed the easiest solution would probably be to add the corresponding init methods to Blocks as well.

Feel free to open an issue/feature request at the GitHub repo https://github.com/PiranhaCMS/piranha.core and we can take the discussion from there!

Best regards

Håkan

I posted this on the Piranha CMS github and one of its authors, Hakan Edling, answered in just a few hours:

"The root issue is that when a new item is selected in the manager in the media picker, the media model that is assigned contains a formatted string size "xxx kb". When ASP.NET tries to deserialize this into a long it fails. So changing the following line in the .vue components for the media-based fields:

I've answered in the Gitter chat, but I'll answer here as well if someone else has the same question.

The templating system is a built in feature of ASP.NET Core and assumes you have the following folders present in you project.

It seems like the identity is missing from your video token, you should have:

The user management is totally abstracted in Piranha, so you could actually authenticate the CMS users any way you want. The Identity package that is included in the templates are included as a boilerplate as most users what a single security setup based on ASP.NET Identity. The only thing the manager cares about when signing in is:

1. That it finds a registered service implementing Piranha.ISecurity (https://github.com/PiranhaCMS/piranha.core/blob/master/core/Piranha/ISecurity.cs)
2. That the users gets the adequate claims needed after signing in (https://piranhacms.org/docs/architecture/authentication)

The code provided in the templates just sets up the standard Identity settings, but you can override everything to do what you're like. The method UseIdentityWithSeed can actually take two more parameters for configuring both IdentityOptions and CookieOptions to work in any way. Take a look at this page for reference:

https://piranhacms.org/docs/architecture/authentication/identity

If you're only looking to adding end-user accounts somewhere this can be done in Piranha CMS by setting up new roles in the admin and adding the application policies you want. You can read about this here:

https://piranhacms.org/docs/tutorials/securing-pages

I have never actually deployed a site with this setup, but as always I know someone has :) This issue on GitHub talks about just this, and the setup was successful. As I can't give specific guidance on this scenario, maybe reaching out to the user in this thread can give you what you need!

https://github.com/PiranhaCMS/piranha.core/issues/627

While not being an answer, I hope this will give your what you need to find the answers.

Best regards

Yes! If you have an up-to-date version of Piranha you can now do the following.

The package Piranha.WebApi uses claims to verify the caller, but how these claims actually get assigned to the user is up to you. The default security implementation Piranha.AspNetCore.Identity by default configures cookie-based security, but if you're only using your application in a headless manner another security setup could probably be beneficial.

More information on how to configure the Identity module can be found here:

https://piranhacms.org/docs/architecture/authentication/identity

Another option is to just provide your own Api instead of using the Piranha.WebApi package. If you take a look at the code for the Api-package here you can see that there's absolutely no logic in these endpoints, they just call the registered Piranha.IApi object.

https://github.com/PiranhaCMS/piranha.core/blob/master/core/Piranha.WebApi/PageApiController.cs#L45

Best regards

Håkan

itertools.product is used for this.