Slartibardfast
Junior Member   Posts: 20 Registered: 1/8/2009 Status: Offline
|
posted on 1/8/2009 at 08:47 PM |
Postnuke 0.7.6.4
Autotheme Lite 0.87
Firstly, thank you for a bit more friendly Theme Manager!
My problem/issue involves trying to make drop down menus work in Autotheme.
Having scoured Forums/FAQ's/etc., the most common problem seems to involve
the code not finding the object(s) it is looking for. I had thought this
was my problem, and many a happy and frustrating hour has been spent
banging away at this (and the dog is suffering too...)
The setup is straightforward:
A bit of code (Javascript) in the <HEAD></HEAD> section of
theme.html, and a bit of code in the BODY.
The Theme Defaults has the Strip out head content set to No.
When the Site is loaded, no errors appear anywhere, until the mouse is
placed over one of the menu items, and you get the error in the Browser
(IE7) status bar 'Error on page' which gives more detail 'Menu is
undefined' followed by 'Error object expected'. Mmmm I thought, this
smacks of the classic 'can't find the object problem', hence a lot of
mucking around with that.
But no, this is what I am now experiencing:
IF I Log On as a User (whether Admin or not), the Menus work fine!
IF I just view the Site as an Unregistered visitor, the Menu's do not
work.
Needless to say I have faffed around with Permissions etc, but to no
avail.
Although I have been working with Postnuke and Autotheme for some years, I
am by no means an expert.
How can I get what works for a Logged on User to work for an Unregistered
visitor? I have been going around in circles for a while, and I wondered
whether anyone can help me bust out of this loop?
Cheers all.
|
| |
| |
Shawn
Administrator   Posts: 4608 Registered: 10/7/2002 Status: Online
|
posted on 1/8/2009 at 09:29 PM |
Do you see the correct javascript in the head section when you view source
as a user who is not loggedin?
-Shawn
|
| |
Slartibardfast
Junior Member Posts: 20 Registered: 1/8/2009 Status: Offline
|
posted on 1/9/2009 at 12:57 AM |
Thanks for the quick repsonse.
When comparing the View Source from both logged in and unregistered views,
there is a big difference, basically, the unregistered view shows no HEAD
content at all.
They are both identical up to the point:
Author:
Contact:
********************************
-->
In the logged on view, the next line is:
<!-- Head from template -->
Followed by the scripting.
In the unregistered view, the next line is:
</head>
There is only one other difference between the 2 source views (as far as I
can see), and that relates to a Menu Block which should be visible to a
logged in User, but not to an Unregistered visitor (this is set in
Permissions). So that seems to be as it should be.
Does that shed any light? I am still puzzled as to why the unregistered
view should not process the HEAD apparantly...
|
| |
Slartibardfast
Junior Member Posts: 20 Registered: 1/8/2009 Status: Offline
|
posted on 1/10/2009 at 01:06 PM |
Any clues as to why this is happening and how I can get around it?
Thanks in advance...
|
| |
Slartibardfast
Junior Member Posts: 20 Registered: 1/8/2009 Status: Offline
|
posted on 1/10/2009 at 05:05 PM |
I don't know if this helps any, but I asked on the PostNuke Forums
(http://community.zikula.org/index.php?module=Forum&func=viewtopic&
topic=55852)for clues as well, and got this response:
"I expect that something about your AutoTheme configuration is causing the
issue, but I am no expert on AutoTheme. In fact, there are very few experts
on AutoTheme left here now - everyone uses the core theme system in Zikula
1.x, and even in PostNuke .76x most people used Xanthia.
I can say that there is nothing in the code of PostNuke that would cause
Javascript written into your HTML theme files to disappear (a module is a
different matter)."
This would seem to indicate that it could be an Autotheme Module issue? Is
there anything in the installation and configuration that I can check?
Everything that should be writable is writable as far as I can tell for
example, but I would appreciate some pointers...
Cheers.
|
| |
Shawn
Administrator Posts: 4608 Registered: 10/7/2002 Status: Online
|
posted on 1/10/2009 at 05:08 PM |
Send a copy of the 2 view sources to 'autotheme AT mckenzies DOT net'.
-Shawn
[Edited on 1/10/2009 by Shawn]
|
| |
Slartibardfast
Junior Member Posts: 20 Registered: 1/8/2009 Status: Offline
|
posted on 1/10/2009 at 05:38 PM |
Hi Shawn,
I am pleased to say that I (think) I have resolved this. Remember that I
am only a part-timer, so am not always aware of everything that might be
important or relevant...
The response from PostNuke Forum made me return to the Autotheme theme in
question, and take a look in more detail. To be honest, I wasn't sure what
in particular I was looking for, but I am reasonably relentless when in
need, and you never know what might pop out of the woodwork if you
persevere.
I took a look at the source file theme.cfg (in the theme folder). This
obviously follows the entries that are made in the Admin of the Theme (ie.e
Default settings etc).
I then noticed that there were 2 entries for 'striphead'. One was
'striphead' => '0', and the other 'striphead' => '1',. This only
goes to illustrate my limitations...
I changed the 'striphead' => '1', to 'striphead' => '0', and voila!
It now seems to work ok for the Unregistered view as well.
I had not spotted this in the Autotheme Admin Panel, which I guess I should
have.
I am further amazed because I am in the middle of a stinking flu, so how I
managed to spot anything is a miracle.
Have a good weekend (what's left of it), and thanks for sticking with this.
|
| |
Shawn
Administrator Posts: 4608 Registered: 10/7/2002 Status: Online
|
posted on 1/10/2009 at 07:19 PM |
Glad you figured it out. There should only have been 1 striphead for
default. The theme.cfg must have been corrupted somehoe. Was this a
free/paid theme or one that you built?
-Shawn
|
| |
Slartibardfast
Junior Member Posts: 20 Registered: 1/8/2009 Status: Offline
|
posted on 1/13/2009 at 11:21 AM |
Still suffering from this stinking flu...
It was a modification of the atSeaBreeze Theme available here on your site.
The second striphead entry refers to the Custom Page *HomePage, not Theme
Defaults, so was there from the start. It was something I did not track
rather than a corruption per se. Only goes to demonstrate my
limitations...
|
| |
Web Hosting & Domain Names!
