On Wed, Feb 9, 2011 at 10:37, Leslie P. Polzer <[email protected]> wrote: > Hey Slobodan, > > sorry I didn't reply to your earlier message. > > I've had lots of work (still do) and your messages got longer and > longer. ;)
Ah, well, I tend to get carried away... :-) Sorry about that. When I'm solving a problem, I'm always trying to explain the situation, especially to myself. It is fascinating how different the problem becomes when you try to explain it to yourself aloud. It forces you to think about the problem and try to be exact in formulating it. > But I am determined to help you solve this. And it would be great if > we could have a result at the end that would make it easier for > newbies to use this approach to login/authenticated nav. > > Now, do you see the nav content after login when you reload the page? Hm. I'll try that when I get home. I've only reloaded the page when I made reset-sessions. >> BTW, I'm using jquery (or trying to in any case). Is there an >> possibility that there lies my problem? That jquery in some way >> conflicts with default weblocks js libraries? I have read about it in >> this newsgroup. I guess this probably isn't the case since js >> manipulates existing html elements, and there are no menu elements... > > Do you see error message in the Firebug console? If you don't then you > probably won't have any problems. > > I did notice in my work with JQuery that its default alias $ conflicts > with Prototype. Use jquery.noconflict() to make sure this isn't a > problem. Yes, that is that issue that I have been reading about. But, like I said, in the html code there are no elements of navigation, so that would mean that my app didn't generate any. It was just a thought. -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
