Did anyone else lose the navigation bar when upgrading to 2.3 and using the Seasons theme?
I am currently using a theme that I modified from the last Seasons version. I just upgraded to 2.3 and wanted to test out the new Seasons. However, when I select use this theme, the top menu navigation on public pages doesn't show. It just shows the header and then the content underneath- no main menu in sight.
Since I am still using my custom theme, it's not a pressing problem, but I am just wondering if this happened to anyone else or what I might be missing. I do want to incorporate its new exhibits layout eventually.
Does your customized theme do anything to affect the navigation, or maybe there's a plugin that uses the public_navigation_main filter floating around that changes things?
I wanted to say I am experiencing the same problem with the Seasons theme.
First thing is probably to deactivate plugins to see if one of them is the culprit.
I never figured out the problem for my site. I just now checked all the plugins and didn't see any issues with them.
I did make a lot of customizations to the CSS within the customized theme, but I didn't think that I changed anything anywhere else. I'll keep looking for things that might affect the public_navigation_main filter.
I pulled the versions you're using and was unable to replicate the problem. What plugins are active on your site(s)?
Hi,
We're having the exact same problem. Did anyone figure out a solution?
We did do a bit of customization in the css files, but not (I don't think) anything that would change the navigational bar. (We did change some things about the "Header" -- getting rid of the search box -- but that was overwritten by the new version, it seems. I'm not concerned about that, since we can just replicate what we did before, but I think it means we probably haven't accidentally removed the navigational bar ourselves.)
We have a number of active plugins: COinS, Neatline (with Simile and Waypoints), Exhibit Builder, CSV Import, SimpleContactForm, Simple Pages, and Social Bookmarking. I tried de- and re-activating all of them, without any effect.
If anyone has any ideas, we'd greatly appreciate it!
Abigail
Can someone having this problem share a screenshot showing the issue, and confirm the versions of Omeka and Seasons they're using? This should help narrow things down and reproduce the problem.
Here's a screenshot of our front page: http://frenchofoutremer.com/omeka/files/original/aa15a75a6787455d6b5e63797f52b68d.PNG
We're using Omeka 2.3 and Seasons 2.3, which updated itself automatically when we switched to Omeka 2.3.
FYI: This might just be the result of unrelated bad practice/mistakes on our part, but when I "inspect element" on our pages, the console comes up with these errors:
modernlocations:224 Uncaught ReferenceError: Omeka is not defined
cdb.js:6 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: (min-resolution: 144dpi)
cdb.js:6 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: (min-resolution: 144dpi)
cdb.js:16 cartodb.js 3.14.0
cdb.js:37 cartodbui v3.10.1 sha1: 3d9dfe79da3f1545f371f95970ee66cbce44e0a3
cdb.js:21 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: (min-resolution: 144dpi)
cdb.js:21 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: (min-resolution: 144dpi)
jquery.min.js:2 Uncaught SecurityError: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with origin "http://frenchofoutremer.com" from accessing a frame with origin "http://fordhammvst.cartodb.com". Protocols, domains, and ports must match.
I just did an inspect element / page source check and found that the Body html starts with a skipnav ID. I don't remember seeing this ID in previous CSS sheets for Seasons? Here it is the Seasons style.css
#skipnav {
border: 0;
clip: rect(0, 0, 0, 0);
height: 1px;
margin: -1px;
overflow: hidden;
padding: 0;
position: absolute;
width: 1px;
}
#skipnav:focus {
top: 0;
z-index: 9999;
clip: initial;
height: auto;
width: auto;
padding: .5em;
border: 1px blue dashed;
}
OK, I got it working now.
I think that there might have been some kind of version overlap, because it looks like the Seasons version I was using might actually have been 2.2.1.
I got rid of the old version, downloaded Seasons 2.3 anew and installed it. Now, the nav bar is visible and works fine.
I didn't figure out what the source of the incompatibility was, but I would suggest re-installing the 2.3 version just to make sure you got the right one. https://omeka.org/add-ons/themes/seasons/
Glad you got it working!
Yes, the skipnav is new - it was part of the accessibility upgrade for 2.3. Very helpful when using a screen reader!
Great - thanks for the update! We did the same and it seems to be working.