Buzz: Questions & Answers

Bookmarks issues

Follow
Answered
Aileen Sweeney

I discovered that once a bookmark was added to the parent sub-domain customization, I could not delete it from the validated customization results stored in the buzz system, even if I removed the code from the settings.xml and revalidated the configuration. This is the Rube Goldberg method that I had to use to hide the bookmarks. I readded the bookmarks that I really did not want anymore and gave them a role that we do not use in the new Buzz.  Is there an easier method? Here is the code that I used, on the parent sub-domain, to remove the bookmarks from appearing on lower level sub-domains. The child subdomains did not have there own set of bookmarks in their own settings.xml files.

<!-- give the Calendar, Admin Tools and New Course Wizard bookmarks a role that we don't use so it will not show up. there is no way to delete it from the validate configuration result once it was added -->

        <bookmark title="Calendar"

            role="reporter"

            bhcomponent="Calendar" icon="Calendar.svg">

        </bookmark>

        <bookmark title="Admin Tools"

            role="reporter"

            bhcomponent="AdminDomainDetail" icon="bookmark_admin_tools_400x400.png">

        </bookmark>

        <bookmark title="New Course Wizard"

            role="reporter" icon="bookmark_teach_course_wizard_400x400.png"

            bhcomponent="TeachACourse">

        </bookmark>

<!-- end of removing bookmarks -->

Comments (5)

Sort by
Brad Marshall
  • Agilix team member

Hello Aileen:

We have been looking into this. I should have some good answers for you early next week.

0 Comment actions Permalink
Brad Marshall
  • Agilix team member

Aileen:

Today we released an article that addresses this need. See: How do I remove inherited customization settings?

To remove the bookmarks from your domain(s), add the following code to your Customize Domain page.

<bookmark-list key="title">
     <bookmark title="Admin Tools" remove-item="true" />
     <bookmark title="New Course Wizard" remove-item="true" />
     <bookmark title="Calendar" remove-item="true" />
</bookmark-list>

I hope this helps.

0 Comment actions Permalink
Aileen Sweeney

With the ability to use the newadmin tool, we are no longer able to set and keep the key="title" in the bookmark list.

Every time I edit a bookmark that also appears with the Edit in XML Editor link and I try to modify the bookmark list to use a key, it always reverts from this

<bookmark-list key="title">

to just this

<bookmark-list>

Then if I trash the bookmark, old phantom bookmarks appear with same link that requires it be edited with Edit in XML Editor.

These bookmarks end up containing old bad bookmarks that also contained values for bhcomponents that were not intended.

contained bhcomponent="TeachACourse"  or  bhcomponent="Calendar"  

Before the introduction of the newadmin tool, we were able to remove these bad bookmarks using the code similar to the Sept 14, 2015 post above. 

Why/how are these bhcomponents getting added to new or changed bookmarks and how do we fix them?

 

 

1 Comment actions Permalink
Aileen Sweeney

Apparently these phantom bookmarks were at the top level nyboces sub-domain. I used the admin screen to trash them and then looked at the editxml screen. This is how they are showing up in the xml window and this fixed the problem of these bad penny bookmarks trickling down to lower level sub-domains.

<bookmark-list>
<bookmark remove-item="true" />
<bookmark remove-item="true" />
<bookmark remove-item="true" />
</bookmark-list>

Back in December the verified configuration was showing this for bookmark-list. 

The key was url and not title

"bookmark-list": {
"key": "url",
"bookmark": [
{
"title": "Admin Tools",
"role": "reporter",
"bhcomponent": "AdminDomainDetail"
},
{
"title": "New Course Wizard",
"role": "reporter",
"bhcomponent": "TeachACourse"
},
{
"title": "Calendar",
"role": "teacher|reporter",
"bhcomponent": "Calendar",
"icon": "Calendar.svg"
}
]
},

It would be nice if there was a screen which showed the verified configuration values, as shown above, so we could easily identify what was causing the problems. Before the new admin tool, we could see the verified configuration values.

 

0 Comment actions Permalink
Brad Marshall
  • Agilix team member

Hey Aileen, we have the support team looking into this so that we can document all of the problems that you are facing. Thank you for your patience.

0 Comment actions Permalink
Please sign in to leave a comment.