LG Navigation - Feature Requests!

Nice! I’m just about to start three page-heavy sites. That would be great timing. 😊

Ok who wants to try this bad boy out?

It should be ready in about 30 minutes for the first run.

Send me a PM 😊

Oh, pick me! Pick me! (I believe you’ve got my mail address from last time 😊)

PM sent.

A way of ordering the page content visually would be nice.

How soon until the first release?

A way of ordering the page content visually would be nice. How soon until the first release?

I’m looking into sortable trees at the moment… jquery seems to have one but its a buggy…. time will tell

Ah excellent. I’ll keep an eye open. Thanks LG

I’m looking into sortable trees at the moment… jquery seems to have one but its a buggy…. time will tell

This looks promising http://plugins.jquery.com/project/NestedSortable

This looks promising http://plugins.jquery.com/project/NestedSortable

Tut tut, finding more work for Leevi to do. Whatever next!! 😉

You really are a train though aren’t you Leevi when it comes to new ideas and creating them! 😉

You must have a spare thinking head lying around somewhere though. Could I borrow it one day!! 😉

Best wishes,

Mark

I’m looking into sortable trees at the moment… jquery seems to have one but its a buggy…. time will tell

This looks promising http://plugins.jquery.com/project/NestedSortable

I think its best to stick to the latest ui branch of jquery…. not much has been happening on the interface side of things for a year or so

Hi Leevi,

Will this work with your LG Multi Language ext/pi? e.g., will a person be able to create an English and a French nav?

Hi Leevi, Will this work with your LG Multi Language ext/pi? e.g., will a person be able to create an English *and* a French nav?

Hmmm in its current state no… but its an interesting idea and I see how it would be of benefit… Maybe we could do something funky like:

{exp:lg_navigation:build_nav depth="3" parent_id="113" translate="fr"}

which would work like the plugin. You would still need a translation in the language file so its not perfect but it would allow you to create multi-language navigation.

New pages that did not have a key would just use the default language.

Hey guys… progress on this module is going really well….

To give you a sneak peak here are the params you can pass to the template tag that builds the nav…

target: either the entry_id or url title. If the target is found in the tree a special class will be applied to the <li> element

parent_id: only render children of this parent

include_ul: render the list in a <ul> tag

exclude: a pipe delimited list of pages to exclude form the nav

add_unique_to: each nav item has a unique class applied to it. This allows you too decide if it should be applied to the <li> or <a>

id: adds an id attribute to the root <ul> element if include_ul is set to ‘y’

class: adds an class attribute to the root <ul> element if include_ul is set to ‘y’

style: adds an style attribute to the root <ul> element if include_ul is set to ‘y’

lang: if LG Multi Language is installed menu titles will be translated to the required language if available or the default language.

That’s probably the release feature set which I’m happy with. I’m just testing the LG Multi Language functionality and then we should be good to go

😊

So Leevi - I just want to check - you are in fact just one of seven identical twins, all called Leevi, who work alternating shifts, right?

Otherwise, I’d like the number of your pharmaceutical advisor. Or the exact caffeine brew you use.

Or both.

So Leevi - I just want to check - you are in fact just one of seven identical twins, all called Leevi, who work alternating shifts, right?

Dam you got me.. 😊