Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Blog Module /

Discuss the Blog Module.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

SiteTree vs DB inconsistencies with multiple BlogHolders in SS 3


Go to End


1322 Views

Avatar
cmc

Community Member, 33 Posts

30 September 2012 at 12:12am

When multiple Blog Holders exist within a the site tree -

Blog Entries appear in CMS Site Tree under the Holder to which they were assigned, but upon checking SiteTree_Live in the database the ParentID for these pages is actually a different BlogHolder. In this case, a completely different branch of the Site Tree. The Site Tree is something like this -

SiteTree

     -BlogTree 1
          --BlogTree 1a
               ---BlogHolder 1a-1
                    ----BlogEntry(s)
               ---BlogHolder 1a-2
                    ----BlogEntry(s)
          --BlogTree 1b
              <--- similar to BlogTree 1a --->

     -BlogHolder 2
          --BlogEntry(s)

So, for example, Blog Entries added to BlogHolder 1a-1, show up in the correct place in the SiteTree in the CMS, but in the DB some have the ParentID of BlogHolder 2. I've tried numerous flushes to see if I can get the SiteTree to match the DB, but the inconsistencies persist.

One, fairly simple solution would be to create separate Blog classess for BlogTree 1 node, but I'm wondering if SS3 and/or the Blog module is not intended to work with multiple Blog Holders or if this is a bug?

Thanks,
Cathy