Hey Nigel,

Okay, so you will need to install the UmbracoCms.Web package as well I believe.

The PluginController attribute is in the following namespace Umbraco.Web.Mvc

The UmbracoAuthorizedJsonController controller is in the following namespace Umbraco.Web.Editors

As for the database stuff, I believe you need to use the scopeProvider to create a scope that then gives you access to the database. There have been some questions on this recently on the forum but I can't recall where they are sorry.

Nik

Hey Nik

Really appreciate the info - thank you.

Making some progress now., although I may be back... :-)

Cheers

Nigel

OK, next wee issue:

Previously the ContentService had a SetTags() method...

This is not available within V8.

The TagService documentation only details Get methods.

Is anyone able to advise how to set tags programmatically on content and media in V8 please ?

Thanks

Nigel

OK, next issue I've got is as follows:

So currently I have the following controller for my TagManager Tree

public class TagManagerTreeController : TreeController
{
    private TagManagerAPIController tmapictlr;

    public TagManagerTreeController()
    {            
        tmapictlr = new TagManagerAPIController();
    }
...
}

But tmapictlr = new TagManagerAPIController(); isn't happy as my APIController is as follows:

[PluginController("TagManager")]
public class TagManagerAPIController : UmbracoAuthorizedJsonController, IUserComposer
    {
    private IScopeProvider _scopeProvider;

    public TagManagerAPIController(IScopeProvider scopeProvider)
    {
       _scopeProvider = scopeProvider;
    }
...
}

Quite simply I don't understand how to create / pass a "scopeProvider" to my constructor method.

Is anyone able to please help ?

Thanks

Why do you need to instantiate an apicontroller though? :-) They exist so that an http request can come in and ask for something.

That said, if you need to instantiate any class then you can opt it into dependency injection as well.

A bit of background info: https://www.zpqrtbnk.net/posts/composing-umbraco-v8/

So you could do something like this to register your API controller:

[RuntimeLevel(MinLevel = RuntimeLevel.Run)]
public class MyComposer : IUserComposer
{
    public void Compose(Composition composition)
    {
        composition.Register<TagManagerAPIController>(Lifetime.Singleton);
    }
}

Then when you need it you ask for it:

public class TagManagerTreeController : TreeController
{
    private readonly TagManagerAPIController _tmapictlr;

    public TagManagerTreeController(TagManagerAPIController tagManagerAPIController)
    {            
        _tmapictlr = tagManagerAPIController;
    }
...
}

I don't really have the answers, it just feels wrong to call a controller from a controller. Typically I would call a centralized service to do something for me. A service would also work for both controllers and be injectible with DI. Then you'd update the code above to register a TagManagerService (and you would ask for it in both controllers.

is working on a reply...