Import Navigation Items for navigation_all-categories

[ocpxc02]

Is there a way to import our categories along with hierarchy into the list used to present the fly-out menu?

Thanks,
Paul

[Keitho]

That would be great. Having to rekey is a pain.

[Bruce - PhosphorMedia]

Here ya go...

https://www.miva.com/forums/filedata/fetch?id=684701

[ocpxc02]

Here ya go...

https://www.miva.com/forums/filedata/fetch?id=684701

Thanks for that code and example XML. It appears that this code will read the csv and output the xml, which you can then import using the standard import Miva import feature. Is that correct?

[kayakbabe]

I found the ReadyTheme Nav Set Import instructions on several forum posts. What I want to know is...
Is there a way to update instead of just import a new set?
I see NavigationSet_Add
but I want to be able to do a NavigatniSet_Update or NavigationSet_AddMORELINKS
Can I Do that?

[pmlvalerie]

I would like to know the same. Is there a way to update a Navigation Set? Or to update, do you delete then import to add?
Thanks!

[Bruce - PhosphorMedia]

If you have a navigation system that needs to be relatively dynamic (i.e., you add, remove items on a daily or weekly basis) I'd contact a developer to have them build a 'automatic' system. Basically, what they would do is replace the 'readytheme' element with a script to pre-build the navigation links (and save them to a managed template) on a scheduled or 'triggered' basis. (We usually just tie the trigger to the IP or customer account of the store owner or staff. That way, the menu gets rebuilt on every page load for them, but customers see a 'saved' version.

[Matt Zimmermann]

In your XML file, you should be able to replace NavigationSet_Add with NavigationSet_Update.

[pmlvalerie]

Thank you for the quick response!

I couldn't find any documentation on this so I've been trying various possibilities. I am getting the error message "missing required attribute code" on line 2. Here is my XML:

<Module code="readytheme" feature="component">
<NavigationSet_Update>
<Code>primary_navigation</Code>
<Name>Primary Site Navigation Bar</Name>
<Layout>Horizontal Drop-Down</Layout>
<Items>
<Item>
<Active>true</Active>
<Name>Transmission Pans</Name>
<SubItems>
<Item>
<Active>true</Active>
<Name>Ford</Name>
</Item>
<Item>
<Active>true</Active>
<Name>GM</Name>
</Item>
</SubItems>
</Item>
</Items>
</NavigationSet_Update>
</Module>

The domain is pmlproducts.com.

Any suggestions would be greatly appreciated!
Valerie

[Matt Zimmermann]

Hi Valerie,

I looks like you are missing the link value:

<Module code="readytheme" feature="component">
    <NavigationSet_Update>
        <Code>primary_navigation</Code>
        <Name>Primary Site Navigation Bar</Name>
        <Description>Main Navigation</Description>
        <Layout>Horizontal DropDown</Layout>
        <Items>
            <Item>
                <Active>true</Active>
                <Name>Transmission Pans</Name>
                <SubItems>
                    <Item>
                        <Active>true</Active>
                        <Name>Ford</Name>
                        <Link type="Category">FORD_TRANSMISSION_PAN_CATEGORY_CODE</Link>
                    </Item>
                    <Item>
                        <Active>true</Active>
                        <Name>GM</Name>
                        <Link type="Category">GM_TRANSMISSION_PAN_CATEGORY_CODE</Link>
                    </Item>
                </SubItems>
            </Item>
        </Items>
    </NavigationSet_Update>
</Module>

[William Davis]

Here ya go...

https://www.miva.com/forums/filedata/fetch?id=684701

Wow, I had no idea this existed. Had I known that it could have saved all of us a lot of headaches.

[pmlvalerie]

Matt Zimmermann

Thanks! Unfortunately, I must be doing something else wrong. Same error, missing required attribute code on line 2.

Date/Time

Line #

Log Message

5-22-2019 14:51:03		Import of test_pan_miva_orig.xml started
5-22-2019 14:51:03	2	NavigationSet_Update: Missing required attribute code
5-22-2019 14:51:03		Import of test_pan_miva_orig.xml complete

I appreciate all the help!
Valerie

[Matt Zimmermann]

Hi Valerie,

It looks like I was missing the update code in my previous example. Try this one:

<Module code="readytheme" feature="util">
    <NavigationSet_Update code="primary_navigation">
        <Code>primary_navigation</Code>
        <Name>Primary Site Navigation Bar</Name>
        <Description>Main Navigation</Description>
        <Layout>Horizontal DropDown</Layout>
        <Template><![CDATA[Main Navigation Updated]]></Template>
        <Notes>Main Navigation Updated</Notes>
        <Items>
            <Item>
                <Active>true</Active>
                <Name>Transmission Pans</Name>
                <SubItems>
                    <Item>
                        <Active>true</Active>
                        <Name>Ford</Name>
                        <Link type="Category">FORD_TRANSMISSION_PAN_CATEGORY_CODE</Link>
                    </Item>
                    <Item>
                        <Active>true</Active>
                        <Name>GM</Name>
                        <Link type="Category">GM_TRANSMISSION_PAN_CATEGORY_CODE</Link>
                    </Item>
                </SubItems>
            </Item>
        </Items>
    </NavigationSet_Update>
</Module>

[pmlvalerie]

Matt Zimmermann
I added a "-" between Drop and Down for the <Layout> and it worked without error. Yay!

However, navigation is now GONE. Instead it says "Main Navigation Updated". Booooooo.

I've tried a couple things but don't know how to get it back. XML sounded like such a good idea a few days ago...

I'd recommend anyone trying this be very, very careful!

[William Davis]

If you have a navigation system that needs to be relatively dynamic (i.e., you add, remove items on a daily or weekly basis) I'd contact a developer to have them build a 'automatic' system. Basically, what they would do is replace the 'readytheme' element with a script to pre-build the navigation links (and save them to a managed template) on a scheduled or 'triggered' basis. (We usually just tie the trigger to the IP or customer account of the store owner or staff. That way, the menu gets rebuilt on every page load for them, but customers see a 'saved' version.

Bruce, do you still have this solution available? It beats having to develop one from scratch.