Content Type and App not registered in demo project

[Michael Haufe]

I've been evaluating a number of CMSes for my organization and Magnolia was one of the final contenders.

To get a better feel for the CMS I have been following the offical Getting Started guide:

<https://hd.magnolia-cms.com/docs/getting-started/hello-headless/>

I am at the step where a new Content Type and App is defined:

<https://hd.magnolia-cms.com/docs/getting-started/hello-headless/#defining-our-content-type>

According to the documentation:

"Magnolia will automatically pickup the new content type and will make it available on our running instance."

This did not happen for me. The new content type and new app are not being displayed in the dashboard. I also do not see them listed under the Definitions app. I have already logged out and logged back in.

The paths:

basic-headless-demos/magnolia/light-modules/basic-tours-lm/apps/tours.yaml

basic-headless-demos/magnolia/light-modules/basic-tours-lm/contentTypes/tours.yaml

Is this a known issue? 

In the console I see:

2021-01-18 16:01:45,484 WARN  info.magnolia.cms.filters.ContentTypeFilter       : Content type for http://localhost:8080/magnoliaAuthor/.magnolia/admincentral/PUSH ... is not set.

2021-01-18 16:01:45,484 WARN  info.magnolia.cms.filters.ContentTypeFilter       : Response is not committed yet. Setting content type: text/html.

What is the resolution for this?

My environment:

Windows 10 + WSL

[Michael Haufe]

It seems a restart of the server is required...

[Christopher Zimmermann]

Hi Michael, 

Hmm wierd,  a restart should not be required. It sounds like the the file observation mechanism did not work correctly. Did you follow the tutorial exactly - or did you do anything differently? 

Which version of Magnolia have you installed? (You could find it in the "About" app.)

If you make a change to the content type file now - maybe just changing a label for example - does it pick up the change after closing and opening the app?

Cheers, Topher

--
You received this message because you are subscribed to the Google Groups "Magnolia User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to user-list+...@magnolia-cms.com.
To view this discussion on the web, visit https://groups.google.com/a/magnolia-cms.com/d/msgid/user-list/921c233f-c14a-4c8e-830d-3ab5be43a6dbn%40magnolia-cms.com.

--

Best regards,

Christopher Zimmermann / Product Manager 
christopher...@magnolia-cms.com 

Skype: czimmermann_magnolia

Magnolia 
Oslo-Strasse 2, 4142 Münchenstein (Basel), Switzerland
Office: +41 61 228 90 00 www.magnolia-cms.com 
 

[Michael Haufe]

On Tuesday, January 19, 2021 at 8:39:02 AM UTC-6 christopher...@magnolia-cms.com wrote:

Hi Michael, 

Hmm wierd,  a restart should not be required. It sounds like the the file observation mechanism did not work correctly. Did you follow the tutorial exactly - or did you do anything differently? 

Which version of Magnolia have you installed? (You could find it in the "About" app.)

If you make a change to the content type file now - maybe just changing a label for example - does it pick up the change after closing and opening the app?

 Changing the file name or the label in either file made no difference.

I seem to be having the same issue with creating a REST endpoint.

Is there a means of debugging the file observation mechanism? The running console doesn't seem particularly helpful here

The only potentially unusual thing is that the Windows Subsystem for Linux was used for all setup and editing is being done with VSCode with the WSL connector.

[Christopher Zimmermann]

Not exactly "debugging" but it is useful to look in the "Resource files" app (at the bottom of the app launcher). It shows exactly which files have been detected by the system. So its kind of one level "lower" then the Definitions app. 

Sounds like this WSL thing could be related, TBH I have not heard about it or conversations about it yet at Magnolia.

It could be an idea to try it on Windows without the WSL on  your system.

[Michael Haufe]

On Tuesday, January 19, 2021 at 8:59:43 AM UTC-6 christopher...@magnolia-cms.com wrote:

Not exactly "debugging" but it is useful to look in the "Resource files" app (at the bottom of the app launcher). It shows exactly which files have been detected by the system. So its kind of one level "lower" then the Definitions app. 

Sounds like this WSL thing could be related, TBH I have not heard about it or conversations about it yet at Magnolia.

It could be an idea to try it on Windows without the WSL on  your system.

Trying to get this working in windows 10 directly was too painful. Luckily I was able to find a solution.

So it turns out the issue is that I originally installed the starter project in `/mnt/d/dev/<project-name>` which corresponds to `D:\dev\<project-name>`

With your suspicion that the file observation mechanism was not working, I assumed that maybe there was some timeout or some unknown bug with working across a mounted path.

I reinstalled the project under my home directory `~/dev/<project-name>`

Under this new path the CMS was able to automatically pick-up changes as advertised in the documentation.

[Christopher Zimmermann]

Ahh hah. It could then have been a simple problem of the path to the "light-modules" directory being wrong in that setup. This is configured by a "magnolia.resources.dir" property. And that path is set automatically by the CLI when your run the "mgnl jumpstart" command.

Here are some details:

https://docs.magnolia-cms.com/product-docs/Modules/Light-modules.html#_light_modules_folder_magnolia_resources_dir