Here’s an interesting thing about the public advanced search interface. When the screen is reduced enough that the default theme switches to mobile mode, the simple search box spreads across the width of the screen. As a result, it’s easy to set the advanced search parameters and then miss that the search button is at the bottom of the form and hit the search icon for the simple search instead.

The title and logo are being "pre-calculated" in a sense in the header of the layout view, but those variables aren't actually being used.

The logo is also being manually created and lacks an alt, which should just be the text title.

Variations of this probably apply to other themes.

Default is only offering a "Main" region on item sets, but on the public page everything is displaying in, like, a right sidebar.

Titles breaking awkwardly. Using media block and html block. Happens in Chrome and Firefox.

In 4.1, the breadcrumb is loading with a really big margin-top and getting hidden under the page title.

The removal of the Omeka object breaks code later trying to use Omeka.jsTranslate in the theme.

See https://forum.omeka.org/t/error-on-omeka-s-default-theme-1-6-2/14746

Default now comes with the following block templates and classes, designed to provide more page building options for attractive landing pages. Test that these block templates and classes display as intended and scale well at both mobile and desktop widths.

Asset block template: 3-column grid

This template is best used for displaying page links with asset images. It lays the assets out in a 3-column grid for widths greater than 800px, then scales down to 2 for widths greater than 400px, then a single column for anything smaller.

Media block template: 2-column cards

This presents media attachments as white cards with the media on the left and metadata on the right, each taking up half the card width. At widths above 800px, it shows as 2 columns. Each card should be a uniform height in its row. This template ignores the vertical vs horizontal layout setting. It looks best with an even number of attachments, each set with a short caption.

HTML class: "spotlight"

Available paired classes: "left-image", "light accent", "dark accent"

This is intended to pair a user-assigned decorative background image inline with text content. The user must set a background image using the block configuration. By default, the background image is aligned to the right. Users can pair this class with "left-image" to move the background image to the left. There are also options to set a single color accent background using "light accent" and "dark accent".

Again, not sure if this is an issue but on a page with no blocks at all, the menus appear very close together. Happens in Chrome and Firefox.

Is this expected behavior?

When I add an logo in the theme settings, the site Title does not display:

Looking at the HTML, it seems the site title is given as the logo alt-text, but does not render on the page.

When I add a banner instead (no logo), I get the site title and the nav bar, but above the banner. I'd expect the title & nav to be below the banner (like it is for logo).

Thanks

So, I'm tinkering with ways to add content based on a URI value for a property by pulling in additional content using the rep.value.html event.

In default theme, doing this code, the little signal I add that the link goes to data gets offset in this theme, but not in others (Cozy and Center Row).

The added content -- "(Full Data)" -- looks like it's bumped up a little higher than the default content that comes in when I add it.

The basic code of my module goes like this:

                $html = "<div>" . $event->getParam('html') . ' ' . $translator->translate('(Full Data)') . " </div>";
                $property = 'dbo:abstract';
                $abstract = $resource->getLiteral($property, 'en');
                $html .= $abstract->getValue();
                $event->setParam('html', $html);

To reproduce, install LodConnect, and add URI property to something that refers to a DBpedia resource (e.g., http://dbpedia.org/data/Swindon )

This might just be that my module needs to deal with theming better. Dunno whether this is an issue on my side or not.

Use cases we're testing for:

Browsers

Chrome
Firefox
IE 11
Modules

Mapping
Collecting
MetadataBrowse
Other

Mobile devices
Multiple levels of navigation
Logo upload
Please make separate issues for any found bugs or unexpected behaviors.

I noticed an error caused by this commit 003f6e3. It causes jsTranslate to break, "Uncaught ReferenceError: Omeka is not defined."

"An accent color to be used on links. The default value is #089494."

Should be #920b0b

See forum post for details: https://forum.omeka.org/t/default-theme-navigation-bar-jumping-when-item-is-selected/10539/3

The problem was spillover behavior from mobile submenu navigation. The mobile navigation itself wasn't working, as it relied on unreliable hover behavior using a pure CSS approach. I've revised it to use jQuery generated buttons that should behave more consistently.

This test issue is looking for the following:

• On desktop, selecting a navigation item no longer causes the nav bar to jump left.
• Mobile navigation now uses buttons for toggling submenus open and closed.

The fix is on the mobile-nav-button-toggle branch.

See omeka/omeka-s#710 and omeka/omeka-s#721.

We don't appear to have any styling to distinguish links except for hover.

Not sure if this is an issue, but there isn't much room on the bottom margin of the prev | next links at the bottom of the page.

Looks like the break to top and bottom links for the pagination aren't happening around the list of item sets in the browse item sets block, at least for a simple one item set example.

The initial bug is documented in omeka/omeka-s#1453. The solution in the flex-fix branch constrains navigation to a single row on the desktop so that the hover menu is never vertically separated from its parent.

I predict users will ask about wrapping, but I'd like to think it's a reasonable request to pare the navigation down to something that works on one line...

There is now a theme setting that allows users to select a banner image to appear across site views. In additional settings, they can control:

• the maximum height of the banner for both mobile and desktop widths
• where to position the image within the banner container when the container ratio has a much greater width than height

Note: we're testing this setting across a bunch of themes, and I decided to omit the contained width setting for Default, as it doesn't really fit the look of this theme.

This is on the master branch and should be tested on desktop and mobile browsers.

The text size for item titles seems to differ, based on the number of images per row.

Demo page has multiple showcases, some with more items than others. All of these showcases are set for "Large" thumbnail sizes. These are standardized in rows with two or more images. The text size for item titles is also different based on number of images per row- one image in a row is large, two or more are all the same size.

The result is that showcases with one image have a title font size that is significantly larger than the font used in any of the other showcases.