Controller action is not working with 404 error

[kudryavtsevda]

I am trying to render cshtml view via standart approach: controllers and razor view. But it is not working with 404 error.
Module name: OrchardCoreContrib.Html, Controller name: GrapesJSController, View name: Index
This is startup.cs

This is GrapesJSController

This is the simplest view:

This is the manifest

And this is the bad result:

Please tell me anybody what am I doing wrong?

[Skrypt]

Have you added the OrchardCore.Contrib.Html module to your Mysite.Web project as a reference?
Have you enabled the module feature in the admin?

[kudryavtsevda]

Have you added the OrchardCore.Contrib.Html module to your Mysite.Web project as a reference? Have you enabled the module feature in the admin?

Yes, I have added it and enabled. Moreover this module works good apart from this issue.

Also I noticed that due to some reason startup.cs of the module is not invoked. I have no idea why. But as a result this route is not in the list of routes.

[hishamco]

Can you change the route name and have a try?

[Skrypt]

The Manifest.cs file has an error like @hishamco is mentioning. You should name your Module the same as your assembly name. So in that case OrchardCoreContrib.Html

[kudryavtsevda]

The Manifest.cs file has an error like @hishamco is mentioning. You should name your Module the same as your assembly name. So in that case OrchardCoreContrib.Html

thank you for your assistance but let me correct you: it is me who found the root of the issue on my last screenshot

[hishamco]

Seems the issue because we have a single feature, @kudryavtsevda let me double check again

[kudryavtsevda]

Seems the issue because we have a single feature, @kudryavtsevda let me double check again

Yes, the author of tutorial claims: The technical ID of the feature. The base feature should have the same name as the module (i.e. its csproj file).
But for the second feature he says: We commonly suffix the base feature/module ID and name for sub-features.

So it is explicitly outlined and I would not consider it is as I issue or bug. Just only as an inconvenience which makes me throw all day long in a trash

[Skrypt]

You don't need to have a module and feature for this simple module. This is what we meant. You will generally use a feature inside a module if you have sub-features that can be disabled. Just, for example, the Lucene module has a Search feature which is not required for the Lucene module to work.

[Skrypt]

The Manifest.cs file has an error like @kudryavtsevda is mentioning. You should name your Module the same as your assembly name. So in that case OrchardCoreContrib.Html

[jtkech]

Yes, if a module has only one feature it is not required to use the Feature attribute, this only one main feature is created automatically with the module Id, but it's okay to still use the Feature attribute so that it is easier to add other Features afterwards, but then, yes it is strongly recommended that the first Feature (or only one) matches the module Id. Anyway, here at least the route area should match the related feature Id.

[jtkech]

yes, @kudryavtsevda found the issue !!!

[hishamco]

Seems it's my bad to change the features IDs serveral days ago, I remember that change done when I planned to add extra feature but I didn't

@kudryavtsevda I will publish a patch release soon, also you can check that the Id has been changed serveral days ;)

Thanks again

[hishamco]

Wait a minute @kudryavtsevda seems I didn't publish the package yet, it's WIP PR OrchardCoreContrib/OrchardCoreContrib.Modules#36, but again I need to fix the OCC.Users modules, don't blame me because it's WIP ;)

[hishamco]

@jtkech could you please check my comment here, I just checked the source, everything seems to work fine

[jtkech]

@hishamco

Yes in place of using OCC.Users.Impersonation for your first and only one feature, and then having to decorate your startup and controller with [Feature("OCC.Users.Impersonation")], better to just use OCC.Users without having to decorate anything. But then in any case, your route area should match the related feature Id that you will use at the end.

[hishamco]

That means nothing wrong with what I did, coz I'm planned to add extra features, which requires me to such decoration for every feature, right?

[jtkech]

Yes but usually we don't do that for the first feature

And currently your route area OCC.Users doesn't match your feature Id OCC.Users.Impersonation

[masterflylox]

Does the orchard sovereign archive still exist? Where can I view it? On github? What is the link? I get a 404 error every link.

[Piedone]

What are you referring to by "orchard sovereign archive"?