Umbraco 8 Content App | Issue creating new pages (only with no content fields)
Hi Guys,
I am not sure if this is a bug with Umbraco 8 base code I have stumbled upon or if it is something I need to be doing extra to get around.
So I have created a ContentApp and it seems to work fine for editing existing pages and also when adding new pages with at least one property in the content section.
The error exists if I try and create a content node / page which does not yet have any property editors added in the content section.
So what happens is when I am trying to add one of these pages the Name is grayed out so I cant enter the new node name and then save.
I'm guessing that because there are no content properties to fill out the content icon is not there and the user is automatically presented with my ContentApp. Since we are looking at my content app then the name is not editable.
I tested adding some properties to the content section and they re-adding and this worked fine. I removed the properties again and re-tested. The issue was back.
Is there something I need to be doing in my content app. Maybe say only display for nodes with properties?
I think you may have found a bug here with regards to the Content Apps as I am seeing this same behavior in other Content Apps from the scenario you described -- an inability to save a new document that contains no properties.
Could you describe to me a scenario where you would want to a create and implement a Document Type with no properties? I'm trying to think of the use case and I'm not able to able to envision the scenario.
The only reason I ask is because I think a bug report is likely needed with what you've described, but based on some of the reasoning here, the bug could be in the handling of no property Document Types or it could be in preventing Document Types with no properties.
I thought as much. Thanks for confirming. I should have really tested other content apps myself too.
I think it is a common practice to create content nodes with no properties. Well at least it is with me. Pretty much every website I create.
The main scenario I find myself doing this is.....
When I can create content nodes to act as containers or folders. Most of the sites I build code with a content repository where I store all the content nodes shared across the site. Some examples might be testimonials, clients, partners etc. I store these in a global content repository which means I can reference these from any other nodes through modules like client testimonials, our telecom clients, our most recent clients etc.
Please see the screen shot as an example.
There's other times I have had to do this for similar reasons but this is the best example.
I could find a way around it by adding at least one property (label) then saving it. I am guessing I could then go ahead and delete the label but that's not ideal.
That makes total sense and I realized, soon after I had responded, that I have done something like that in the past. Over the last year, I've been including a composition on a folder setup like you describe and I had forgotten how I had done what you described -- sorry about that.
I was thinking this through a bit more and after some more playing with this setup - trying to create a new, no property document type with a package based Content App, I believe I discovered that you can save the new page if you switch over to the Info Content App.
I've just tried it out on two local Umbraco setups where I experienced the same issue you described in your original post, and I found I could save a that new document with no properties using that Info Content App.
As it turns out, I'm also working on a Content App and I hadn't even tested this scenario so I'm grateful you brought this up. I'm planning on doing a bit more investigation because I'd like to see if this can be worked around.
Please let me know if trying to name and save from the Info Content App works with your current setup.
Click into the info tab then the save becomes available. A simple work around but I think this should be flagged as a base code bug. I am sure it will confuse a few other people down the line.
I completely agree that this should be addressed in some manner and, as the issues get reviewed by the team, I'll be curious to hear what the initial response is.
I wanted to review why the initial Content App that would display the document type properties does not display in this scenario. I was thinking that there's a check in that app that maybe should be included in the custom package content apps.
As an alternative, this could probably be resolved by changing the weight of the Info Content App so that it would always come before a custom package content app.
I'll keep an eye out for the issue if you post it. I'd be happy to provide additional information to the submission.
Umbraco 8 Content App | Issue creating new pages (only with no content fields)
Hi Guys,
I am not sure if this is a bug with Umbraco 8 base code I have stumbled upon or if it is something I need to be doing extra to get around.
So I have created a ContentApp and it seems to work fine for editing existing pages and also when adding new pages with at least one property in the content section.
The error exists if I try and create a content node / page which does not yet have any property editors added in the content section.
So what happens is when I am trying to add one of these pages the Name is grayed out so I cant enter the new node name and then save.
I'm guessing that because there are no content properties to fill out the content icon is not there and the user is automatically presented with my ContentApp. Since we are looking at my content app then the name is not editable.
I tested adding some properties to the content section and they re-adding and this worked fine. I removed the properties again and re-tested. The issue was back.
Is there something I need to be doing in my content app. Maybe say only display for nodes with properties?
Please see the screenshot attached.
David --
I think you may have found a bug here with regards to the Content Apps as I am seeing this same behavior in other Content Apps from the scenario you described -- an inability to save a new document that contains no properties.
Could you describe to me a scenario where you would want to a create and implement a Document Type with no properties? I'm trying to think of the use case and I'm not able to able to envision the scenario.
The only reason I ask is because I think a bug report is likely needed with what you've described, but based on some of the reasoning here, the bug could be in the handling of no property Document Types or it could be in preventing Document Types with no properties.
Hi Adam,
I thought as much. Thanks for confirming. I should have really tested other content apps myself too.
I think it is a common practice to create content nodes with no properties. Well at least it is with me. Pretty much every website I create.
The main scenario I find myself doing this is.....
When I can create content nodes to act as containers or folders. Most of the sites I build code with a content repository where I store all the content nodes shared across the site. Some examples might be testimonials, clients, partners etc. I store these in a global content repository which means I can reference these from any other nodes through modules like client testimonials, our telecom clients, our most recent clients etc.
Please see the screen shot as an example.
There's other times I have had to do this for similar reasons but this is the best example.
I could find a way around it by adding at least one property (label) then saving it. I am guessing I could then go ahead and delete the label but that's not ideal.
David --
That makes total sense and I realized, soon after I had responded, that I have done something like that in the past. Over the last year, I've been including a composition on a folder setup like you describe and I had forgotten how I had done what you described -- sorry about that.
I was thinking this through a bit more and after some more playing with this setup - trying to create a new, no property document type with a package based Content App, I believe I discovered that you can save the new page if you switch over to the Info Content App.
I've just tried it out on two local Umbraco setups where I experienced the same issue you described in your original post, and I found I could save a that new document with no properties using that Info Content App.
As it turns out, I'm also working on a Content App and I hadn't even tested this scenario so I'm grateful you brought this up. I'm planning on doing a bit more investigation because I'd like to see if this can be worked around.
Please let me know if trying to name and save from the Info Content App works with your current setup.
Thank you!
Hi Adam,
I can confirm your solution works.
Click into the info tab then the save becomes available. A simple work around but I think this should be flagged as a base code bug. I am sure it will confuse a few other people down the line.
Any ideas how to log bugs other than on here?
David --
It's my understanding that we can log issues off of the repo on Github here, https://github.com/umbraco/Umbraco-CMS/issues
I completely agree that this should be addressed in some manner and, as the issues get reviewed by the team, I'll be curious to hear what the initial response is.
I wanted to review why the initial Content App that would display the document type properties does not display in this scenario. I was thinking that there's a check in that app that maybe should be included in the custom package content apps.
As an alternative, this could probably be resolved by changing the weight of the Info Content App so that it would always come before a custom package content app.
I'll keep an eye out for the issue if you post it. I'd be happy to provide additional information to the submission.
Thank you!
Hi Adam,
I submitted a bug request. https://github.com/umbraco/Umbraco-CMS/issues/7415
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.