LP1760160: Search bar has a different CSS class when on the home page To test: 1. In templates/opac/css/style.css, add some highly noticeable CSS that applies to .searchbar-home or an element within .searchbar-home, e.g. .searchbar-home .search-box { background-color: purple; height: 4em; } 2. Go to the home page of your public catalog. The .searchbar-home .search-box CSS should have taken effect. 3. Go to another page of your public catalog, such as a search results or login page. The CSS should not have taken effect here. Signed-off-by: Jane Sandberg <sandbej@linnbenton.edu> Signed-off-by: Bill Erickson <berickxx@gmail.com>
LP#1507845 SEO home.tt2 template repair Ensure all TT code lives within the [% ... %] blocks. This fixes an issue where TT code "ctx.metalinks.push('');" was appearing in the catalog as bare text. Signed-off-by: Bill Erickson <berickxx@gmail.com> Signed-off-by: Kathy Lussier <klussier@masslnc.org>
LP#1507845: Improve search engine optimization Back in bug # 1414033 , we added rel="nofollow" attributes to many of the links that led to search results or call number browsing. This was the right idea, but a bit overzealous as it turns out. We actually want search engines to follow those links; we just don't want search engines to index them. Therefore, we can tweak the <meta> tag in the results and browse page headers to say "follow,noindex", and remove many of the inline rel="nofollow" attributes from the other pages. In addition, add a rel="canonical" link to the catalogue home page. Signed-off-by: Dan Scott <dscott@laurentian.ca> Signed-off-by: Ben Shum <ben@evergreener.net> Conflicts: Open-ILS/src/templates/opac/parts/record/subjects.tt2
LP#1268636 TPAC initial navigation headers Added a screen-reader only CSS class ("sr-only") for adding content which should only be read by screen readers and is otherwise invisible. Added hidden generic <h1> and page-specific <h2> entries to improve web accessibility navigation. Additional content-specific headers (h3 and down) are recommended for content grouping, but not included in this commit. Signed-off-by: Bill Erickson <berick@esilibrary.com> Signed-off-by: Dan Scott <dscott@laurentian.ca>
Fix issues with multiple divs having the search-wrapper id. Basically, remove the extra <div> from all the files that INCLUDE searchbar.tt2, and leave the <div> that searchar.tt2 uses alone. Signed-off-by: Jason Stephenson <jstephenson@mvlc.org> Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
TPAC: Avoid leading / trailing space on pages Use the [%- -%] whitespace-chomping directives to remove the leading space on pages. Signed-off-by: Dan Scott <dan@coffeecode.net> Signed-off-by: Ben Shum <bshum@biblio.org>
TPAC: Remove the printnav bar from all screens Signed-off-by: Dan Scott <dscott@laurentian.ca> Signed-off-by: Thomas Berezansky <tsbere@mvlc.org>
Remove /default/ from template paths The original goal of having a /default/ component to the template path was to support alternate skins. However, Template Toolkit supports alternate skins through a more elegant mechanism of providing template overlays via template path configuration. In other words, skin files will be differentiated by the location of their root path and not because they live in a different skin directory inside the main template root. Because of this, the /default/ component in the template path serves no purpose and generally just gets in the way. As a part of this, EGWeb.pm no longer inserts the skin name into the template file path. Signed-off-by: Bill Erickson <berick@esilibrary.com>