The command component filters for all valid commands. This means that when you are logged out, and the ownership is properly set, only the login button is available. I did not add all commands, since I only need a few: Add, Move, Edit, Remove, Reorder children, Login and Logout.And what is the problem exactly. Do they not work, is the appearance wrong, or do the wrong buttons show up?Something that is not mentioned in my recipe, is that there is an initialisation bug in the security of pier, that you need to set the owner of all things to the “admin" user. To do this, you need to select the root node, and then change owner, select the correct user, and apply recursive.Also when deploying, you probably want to deploy it under a newly created user, instead of the default “admin” / “pier” user.Does this help? Otherwise, you can contact me on google plus and you can share your screen, so I can take a look at your image.Cheers,DiegoOn 30 Jul 2014, at 17:22, sergio_101 <sergio.rrd@gmail.com> wrote:how did you go about getting the 'login' to appear on the bottom left of your screen?still trying to get the command links to work, but to no avail. i can't see anything wrong with the actual links, either.. hmm...._______________________________________________On Wed, Jul 30, 2014 at 6:16 AM, Diego Lont <diego.lont@delware.nl> wrote:
Hi Sergio,
There are two different children here. There is a children (context) that allows to see the children of the node you are currently viewing, and there are the children (dynamic) that allows to see the children of the node that you select. But having set lvl 1, the difference should not be that big.
> Hi, all.
>
> I have been working on getting this going for awhile, and I am having little problems here and there. I think the easiest thing to do would be to go over the spots where i am getting hung up..
>
>> navigation (Children (dynamic)). Change the navigation and set the level to 1 and recursive to true. This will give us better navigation.
>
> just a quick point.. mine says children(context) .. rather than dynamic. i selected that.. but that shouldn't be a big deal..
This button appears when you make your browser small enough. This is one of the bootstrap tricks: if you have enough screen, you get the links displayed, and when your screen is smaller you get a toggle button to save space.
>> And then the collapse looks like this:
>> {{{<button type="button" class="navbar-toggle" data-toggle=“.fcollapse" data-target=".footer-collapse">
>> <span class="se-only">Toggle footer</span>
>> <span class="icon-bar"></span>
>> <span class="icon-bar"></span>
>> <span class="icon-bar"></span>
>> </button>}}}
> this button (and all buttons) shows up on my non styled version just fine.. but when i add the bootstrap parts in, it is no longer visible.
Ok, it looks like I forgot something here … yes, this should be a commands structure, and on the list class you should set "nav navbar-nav navbar-left”, to make them look good. But the links should work without those tags…
>> {{{<div class="footer-collapse fcollapse">}}}
>> +Menu+
>> +Commands+
>> {{{</div>}}}
>>
> the text doesn't say anything about the commands structure.. so, at first i tried it, and i ended up with a dead site.. oops.. next, i added a commands component, and i ended up with the attached. The biggest problem is that non of he command links work.. i can't log out or anything..
Cheers,
Diego
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
------
peace,
sergio
photographer, journalist, visionary
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki