All Versions
DSpace Documentation
Unreleased Documentation
This documentation is unreleased and still in development. It may describe features which are not yet released in DSpace.
Looking for another version? See all documentation
This page provides some basic guidelines for debugging issues that may occur in the User Interface when following the User Interface Customization guide or similar.
HINT: This is very similar to our Troubleshoot an error guide.
If you want to determine what action the User Interface is taking when you click a button/link, you can find that information in your browser's Developer Tools.
Every DSpace Angular component has a corresponding <ds-*> HTML-like tag. The HTML tag is called the "selector" (or CSS selector), and it is defined in the "*.component.ts" tag using the "@Component" decorator (see Angular's Component Overview for the basics). The key point to remember is that if you can find the "<ds-* >" tag, then it is easy to determine which component generated that tag!
So, supposing you are trying to determine which component is generating part of a DSpace page.
Continuing the example, if you view the source of the "Communities in DSpace" heading, you'll see something like this (all HTML attributes have been removed to make the example more simple):
<ds-top-level-community-list>
<div>
<h2> Communities in DSpace </h2>
<p>Select a community to browse its collections.</p>
</div>
</ds-top-level-community-list>
Continuing the example, if you search the ./src/app/ directories for "ds-top-level-community-list" you'll find a match in the "src/app/home-page/top-level-community-list/top-level-community-list.component.ts" file:
@Component({
selector: 'ds-top-level-community-list',
...
})
top-level-community-list.component.ts" file or it's corresponding HTML file at "top-level-community-list.component.html"