What category menus options are available for Shadows?

[William Davis]

What category menus options are available for Shadows? The baked-in menu is not is not a good fit for use due to number of base categories.

[Matt Zimmermann]

Hi Bill,

At this time, the primary navigation options for Shadows are the built-in one, porting the Colossus one over, or building your own. I do have several more planned for future release.

[William Davis]

Is there any documentation on how to "porting over" a category navigation menu?

[Matt Zimmermann]

Hi Bill,

You would need to add in the CSS and JavaScript resources for Omega Navigation and swap out the HTML for the primary navigation set: https://docs.miva.com/readytheme-col...ega-navigation

[William Davis]

Hi Bill,

You would need to add in the CSS and JavaScript resources for Omega Navigation and swap out the HTML for the primary navigation set: https://docs.miva.com/readytheme-col...ega-navigation

If I do that, would I have to reenter all the category information previously entered for the Shadows baked-in primary navigation set?

[Matt Zimmermann]

Hi Bill,

You should not have to re-enter the information, however you may need to make some adjustments depending on how it is currently structured.

[William Davis]

Hi Bill,

You would need to add in the CSS and JavaScript resources for Omega Navigation and swap out the HTML for the primary navigation set: https://docs.miva.com/readytheme-col...ega-navigation

1. Would I "...add CSS and JavaScript resources for Omega Navigation..." by creating a my own "custom.css" file and "...load it in AFTER all others..." as Bruce Golub always suggest on the forum?
2. If so, is the "css.php" file where I need to add at the end my "custom.css" reference?
3. Do I do all this CSS work manually via FTP or does Admin have the ability to edit and add css files?
4. As to adding "...JavaScript resources for Omega Navigation...", do I add that to an existing file? If so, which one and where is is located?
5. I noticed the "...JavaScript resources for Omega Navigation..." is divided in two parts, which probably means the second part is either added elsewhere, what file and where is it located?
6. Do I do all this JavaScript work manually via FTP or does Admin have the ability to edit and add these files?

Sorry, but if I do not asks these questions, I will never learn.

[Matt Zimmermann]

Hi Bill,

Shadows doesn't use a PHP file for the CSS or JavaScript; it utilized the CSS and JavaScript Resources located under User Interface. The easiest way would be to replace the contents of the "x-transfigure-navigation" and "transfigure-navigation" resources with those of Omega. The second JavaScript part of Omega is the initialization string you would use in "theme.js"; it would replace the call for transfigure.

[William Davis]

Hi Bill,

Shadows doesn't use a PHP file for the CSS or JavaScript; it utilized the CSS and JavaScript Resources located under User Interface. The easiest way would be to replace the contents of the "x-transfigure-navigation" and "transfigure-navigation" resources with those of Omega. The second JavaScript part of Omega is the initialization string you would use in "theme.js"; it would replace the call for transfigure.

I'm still lost, is this process documented anywhere? I really hate to bother anyone with so many followup questions due to my inexperience in this area -I know how frustrating that could be for everyone.

[Matt Zimmermann]

Hi Bill,

Unfortunately, there aren't any instructions beyond what is in the ReadyTheme documentation. Improved extension documentation is on my roadmap which will include how to add to specific ReadyThemes.

[William Davis]

Hi Bill,

Unfortunately, there aren't any instructions beyond what is in the ReadyTheme documentation. Improved extension documentation is on my roadmap which will include how to add to specific ReadyThemes.

I understand, "Rome was not built in a day" and Miva has come along a long way since I came along (MM3+). I just wish things would be simpler as they were back in the OpenUI (tokens and conditionals) days and I a little younger. Miva is definitely better than back then, but a lot more complicated.

Having said that and some things not being documented as we all would like, I am having a difficult time determining which parts of the Omega Navigation code goes where. Is there anything published relating to that?

[Matt Zimmermann]

Hi Bill,

1. Replace the HTML content in ReadyTheme -> Navigation Sets -> primary_navigation -> Template with the Omega HTML
2. Replace the CSS content in User Interface -> CSS Resources -> x-transfigure-navigation with the Omega CSS
3. Replace the JavaScript content in User Interface -> JavaScript Resources -> transfigure-navigation with the Omega JavaScript
4. In User Interface -> JavaScript Resources -> theme, replace

   $.hook('has-drop-down').transfigureNavigation();

   with

   $.loadScript(theme_path + 'extensions/navigation/omega/omega-navigation.js');

[harpkit]

Has anyone successfully ported over the Omega menu to Shadows? I tried the steps in Matt's last post and it didn't work for me. In addition to those 4 steps, I think some changes also need to be made in the global header to load the Omega menu. I tried and failed.

Also wondering how close we are to having more menu options available in the Shadows theme?

[Matt Zimmermann]

harpkit Unfortunately, those instructions were for Shadows v1. While the principle is similar in v2, it will actually require you to use the developer edition of Shadows [ https://github.com/mivaecommerce/readytheme-shadows ] where you will make your changes locally and push them up to the store. This process is very close to completion although the directions for porting Omega to Shadows has not been updated yet.

As for additional menu, those are in the works. If you have an example of something you might like to see, please let me know and I will see what I can do.

[harpkit]

Good to know. Thanks Matt Zimmermann!