Hi Dennis,

Thanks for the reply. Could you tell me what you mean by the children not being the same DocType as the parent?

The DocType of each of the blog posts pages is different for example:

Whereas the parent has a DocType of 'blogs'

I cannot change the DocType of the children as they are each their own page? Can I? If so, how can I change them?

Thank you for you help

Alexis

Does every blog post have its own doctype or are they all of a same doctype like "blogpost"? You'll need to create the tabs and properties for every doctype you'd want to use them.

What version are you using? If your using 7.4+ or could upgrade, then you could use compositions to add tabs and props for doc types without having to re-create them for every doctype.

Hi Dennis,

Here is a screenshot of all the different DocTypes

As you can see, they are all different

This is the DocType dettings of the main blog page, it has all the blog pages checked in 'allowed child nodetypes'

As I mentioned, I did not create this site so I am unsure how these pages were created.

Thanks, again

Alexis

Hi Dennis,

In the end, I decided to delete the pages that were made previously because they were created in such a way that they had no parent docType other than master which meant that every time we want to add a new blog page (which will likely be weekly), we'd have to create a new page, create generic properties and content tabs on the this page, fill in the template with the correct code as well as assign the blog post pages to the main blog splash page's code, individually by name/id.

I thought it would be best and would save efficiency in the long run to start again. (sorry guys)

So, I created a master docType for my blog pages called blogMater

From here I created the content properties which will be common to all blog pages

Now, all the child pages of this document type will be able to use these properties.

To make these visible in the content tab, I assign every new blog page as a child node of 'Blogs' (this is the main blog splash page)

Now I can create a new page for any of these, as long as there is a docType correctly assigned as a child node of the Blogs page.

And, within the blog splash page code, I can reference my common properties without worrying about making a spelling error on one of the pages' content properties

 <div class="blog-item">
                  <div class="row ">
                      <article class="rsk-article">
                          <div class="small-12 medium-5 large-3 columns">
                              <div class="article-thumbnail" style="background-image: url(@imgSrc);">
                                  </div>
                           </div>
                           <div class="small-12 medium-7 large-9 columns">
                                <h6 class="normal-heading-light">@item.GetPropertyValue("title")</h6>

                                <p class="basic-paragraph">@(item.GetPropertyValue("shortDescription") == null ? "" :item.GetPropertyValue("shortDescription").ToString() )<a href='@item.Url'>...read more</a>
                                </p>
                                <span class="posted-by">Posted By @(item.GetPropertyValue("author") == null ? "" :item.GetPropertyValue("author").ToString() ) on @(item.GetPropertyValue("postedDate") == null ? "" :item.GetPropertyValue("postedDate").ToString() ) </span>
                            </div>
                       </article>
                </div>
             </div> 

And, even better, I can simply copy and paste the template code for each blog page:

<article>
            <header>
                    <h3 class="normal-heading-light">@Umbraco.Field("title")</h3>
                    <div class="posted-by">Posted By @Umbraco.Field("author") on @Umbraco.Field("postedDate")</div>
            </header>
            <div class="large-6 columns">


                @Umbraco.Field("opening")

            </div>
            <div class="large-6 columns">
                <img src="@Umbraco.Field("blogImage")" alt="" class="align-center">
            </div>
            <div class="small-12 columns">
               @Umbraco.Field("middle")

               @Umbraco.Field("conclusion")
            </div>

        </article>

And just update the contact from the front-facing CMS! Happy times :)

Thanks for all your help, let me know if this is the solution you would've chosen.

Alexis