How to connect the authoring views

[mwpowellhtx]

Using the Coming Soon boilerplate stuff initially. I see what I think are the rendered outputs. Is there a way to review the admin or author level views, however? I see I can access an https://localhost:5001/admin page, for instance, but I do not see anything that indicates the content, items, views, or other half-expected CMS artifacts, etc. Apologies if my verbiage is a bit clumsy. Thanks!

[Piedone]

Not really sure what your question is about, but are you asking where the display (HTML and else) of admin pages are coming from? They are from TheAdmin theme and from the respective modules. E.g. this template is for the title editor.

[mwpowellhtx]

I see this message in green: Feel free to browse the menu and discover all its possibilities.

However, I do not see any menus in which to edit anything. Perhaps I am doing something incorrectly.

Edit: Indeed, reviewing the code behind that, there does not appear to be any mention of any menus, like legit they are not there. Was this a boilerplate placeholder, perhaps?

Are we better off starting from a green field workflow and rolling our own 'coming soon' version, perhaps?

[Piedone]

Can you add a screenshot? To the left of that you should see the admin menu.

[mwpowellhtx]

Can you add a screenshot? To the left of that you should see the admin menu.

I do not have that menu on the left. Again, starting from the Coming Soon boilerplate.

[Piedone]

The Coming Soon adds that menu as well, just a little shorter. Could you share a full-window screenshot? As well as is there anything under App_Data\logs?

[mwpowellhtx]

This is 'plain Jane' out of the box. There are no logs. This is exactly what I am seeing, as I said.

[mwpowellhtx]

I might also note, the company name is not reflected anywhere, either. MvcSandbox versus the name I entered on the input side.

[hishamco]

I see this message in green: Feel free to browse the menu and discover all its possibilities.

The message appears in the dashboard, if you don't see the menu please attach a screenshot I may have a look, sometimes it happens if there's a js bug or a caching issue, may be there's something wrong there

[mwpowellhtx]

Plus side admin did at least prompt me for credentials, so that much is 'working'.

[mwpowellhtx]

Using the 'latest' 1.2.2 NuGet production release package, AFAIK. Thank you.

[hishamco]

I need to add some commits in one of my PR, then I will have a look

[mwpowellhtx]

I get this warning in the console:

DevTools failed to load source map: Could not load content for https://ajax.aspnetcdn.com/ajax/jquery/jquery.min.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

And it does not load anything else, perhaps?

[hishamco]

As I told you, so please wait until I investigate on that

[mwpowellhtx]

Another data point for you perhaps. No worries. I am paused in the workflow evaluation. Thank you.

[mwpowellhtx]

In summary, as I mentioned, evaluating whether OrchardCore/CMS may be ready to adopt for our purposes... In terms of not only the technology stacks, which 'I know' so to say, but more importantly, 'is it ready to start being productive generating content from a business perspective', let alone any other language level business enhancements.

Any ideas why none of the input details are connected with the rendered pages? I gather there is 'something' that needs to be connected there, somehow. Out of the box, all I can say is, it is a non-starter at the moment, unless/until those dots have been connected.
1. Ability to admin the CMS itself
1. Connecting the input details with the rendered pages themselves
1. Ability to identify the Site template as something (anything) else other than 'Default', i.e. . But maybe that is the admin menu wiring that exposes that, I do not know, cannot say.

Using postgres for our database backend. Again, this is out of the box from the 1.2.2 NuGet package; I did not do anything special or other than following the template getting started, Coming Soon.

At the moment at least in the Coming Soon template, gauging readiness for adoption, scale of 1-10, somewhere between a 3-5; letter grade, something like a C- possibly a D+. Now, if there is a 'better' template to start from that is more capable that empowers us to proceed, working around the issues I've organically stumbled upon, that's a different story.

I have also noticed in the Chrome console warnings, failing to load the jquery minified assets, for starters. Perhaps there are front end elements that are loaded in dynamically in that sense; but without the jquery, the dots fail to connect.

Failed to load resource: the server responded with a status of 404 () - re: favicon.ico:1
DevTools failed to load source map: Could not load content for https://ajax.aspnetcdn.com/ajax/jquery/jquery.min.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

I do not care about a favicon at the moment. However the jquery issue seems like a snafu to me. The asset may well not exist via https://ajax.aspnetcdn.com sources? I do not know; again, from an adoption perspective, these are far deeper dives than we are willing to assume.

Edit: Happily 'striking' these from the discussion. As mentioned below, turns out I was basing this mistakenly on an incorrect project template... So when the foundation isn't great, of course, this was the issue. Created a project instead based on the CMS project template, and that made all the difference. I just did not want to leave the impression that I was somehow making it work not working, if you will. Again, appreciate all the hints, it was certainly helpful.

[mwpowellhtx]

Following up with Setup side concerns. Hopefully that makes it a bit clearer.

Also, the issue of 'scalability' for a smaller number of pages it is probably fine. But how does it scale into the hundreds or thousands of pages? At least as discovered by one (now defunct?) competitor, Carnotaurus CMS. In my experience, when we talk about a document database infrastructure, usually has to do with the kind of loading lazy/eager-ness, how well factored the document tables are, talking about MartenDB for instance and some of its features, inclusion, filtering, etc. I do not know if it would be any better/worse for relational analogs, also depending on the normalization and similar loading policies.

Maybe it is better to start from a blank slate recipe, perhaps; which would that be? And then build the sites, versions, etc, out from there. Have not tried that yet; open to suggestions, constructive feedback, etc.

[hishamco]

Ah, seems You are using OrchardCore.Application.Mvc.Targets? not OrchardCore.Application.Cms.Targets

[hishamco]

Nothing wrong with TheComingSoon theme, I just added a new tenant using this theme

[mwpowellhtx]

BTW I'm using the source...

Ah okay; yeah, we are "not", we are running against released packages 1.2.2.

...could you please send a gif showing tenant creating with TheComingSoon theme?

No. Not sure I follow there; what do you mean "TheComingSoon theme".

As I stated, we're not interested to cut our fingers on beta or preview quality code. We are interested in being productive to the business on released modules, 1.2.2 at the time of this response.

If there is an RC or it is ready to push in a 1.2.3 or 1.3.0, I'd encourage that trajectory instead.

[hishamco]

Postgres is just a database

[hishamco]

Running OrchardCore.Application.Mvc.Targets shows the MvcSandbox which is similar to what attached here

[hishamco]

Please share the content of your .csproj content seems there's something wrong on the target

[mwpowellhtx]

In context here, got 'er sorted, I think. At least now themes showing up as expected, admin includes the appropriate menuing, etc.

[ns8482e]

It seems you are not using CMS package.
Use this package for CMS https://www.nuget.org/packages/OrchardCore.Application.Cms.Targets/1.2.2

[mwpowellhtx]

Okay, so that does not 'work' either, in fact, I get an exception dropping the MVC targets package dependency. Apparently that is required.

An unhandled exception occurred while processing the request.
InvalidOperationException: The view 'Index' was not found. The following locations were searched:
/Areas/OrchardCore.Setup/Views/Setup/Index.cshtml
/Areas/OrchardCore.Setup/Views/Shared/Index.cshtml
/Views/Shared/Index.cshtml
/Pages/Shared/Index.cshtml
Microsoft.AspNetCore.Mvc.ViewEngines.ViewEngineResult.EnsureSuccessful(IEnumerable<string> originalLocations)

To recap, starting from the OrchardCore project template, added in the CMS targets.

[mwpowellhtx]

👍 Now we're cooking with gas! Started from the CMS and not the MVC project template, that was the difference.

Apologies for the confusion.

[hishamco]

All the best, hope it works without an issues ;)

[mwpowellhtx]

It's one step closer at any rate; appreciate the orientation.

[hishamco]

If you faced another related issue please let us know, otherwise make the right answer

[mwpowellhtx]

After some helpful hints, troubleshooting and zeroing in on the issue, turns out I had to start from the CMS template, not the MVC template. That sorted us out.

[hishamco]

Seems me then Niraj already said that and your mark your as answer ;)

[mwpowellhtx]

Starting from the project template? No, I think it was a reference to the NuGet packages, not the VS project templates. But the clues helped isolate the root cause, certainly.