When ever I click on the top icons I get Access denied when I use the text menus it works fine and under Permission I do not see the rootcandy module any clues on this?

Comments

sign’s picture

It looks like the tarball isn't up to date, try downloading from cvs, or wait.
Let me know if the problem persists.

sign’s picture

Status: Active » Postponed (maintainer needs more info)
eigentor’s picture

I got the same problem, also after an update. Funnily, if you enter the correct path in the adress bar (say admin/settings) it works. Also the correct Links are shown in status bar hovering over the icons of the top Level Navigation.
Only clicking produces the "access denied" message. The path shown in the address bar remains the last that has been successfully resolved.

sign’s picture

ok, I can't replicate that,
I added few lines to that ajax callback, so if you try now, it will output hopefully some useful info about the menu item.
If you can, paste it here please. And dont forget to get the latest version from cvs or wait for tarball.
Thank you

Elmer Harris’s picture

Drupal is not in my root directory not sure if that is relevant. Looks like I'm getting same error as the others. Error is as follows:

Debugging message

Please, post this to: http://drupal.org/node/225458 if you think this is an error. Thank you.

Access denied

akahn’s picture

I'm getting the same message. This is in MAMP on OS X. There is a red box which I presume is supposed to contain the debugging message, but it's empty. This is using the March 1st release. Any ideas?

tsavino’s picture

This is strange one site on the same server does not do it and the other does... The reason that it is happen is that when you put the site in the sub-directory you get this error when its in the root you do not get the error but here in my setup:

Drupal 6.1
Access to update.php Protected
Configuration file Protected
Database updates Up to date
Drupal core update status Up to date
File system Writable (public download method)
GD library bundled (2.0.34 compatible)
Module and theme update status Up to date
MySQL database 5.0.45
PHP 5.2.5
PHP memory limit 128M
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Update notifications Enabled
Web server Apache/1.3.41 (Unix) PHP/5.2.5 mod_perl/1.30 mod_gzip/1.3.26.1a mod_log_bytes/1.2 mod_bwlimited/1.4 mod_auth_passthrough/1.8 FrontPage/5.0.2.2635 mod_ssl/2.8.31 OpenSSL/0.9.7a

Modules
Up to dateok
CCK Blocks 6.x-1.1
Includes: CCK Blocks
Up to dateok
Content Templates (Contemplate) 6.x-0.4-2
Includes: Content Templates
Up to dateok
Content Construction Kit (CCK) 6.x-1.x-dev (2008-Mar-15)
Includes: Content, Content Copy, Fieldgroup, Node Reference, Number, Option Widgets, Text, User Reference
Up to dateok
FCKeditor - WYSIWYG HTML editor 6.x-1.1-beta2
Includes: FCKeditor
Up to dateok
FlashVideo 6.x-1.3
Includes: FlashVideo, FlashVideo Amazon S3 Plugin, FlashVideo CCK, FlashVideo Views
Up to dateok
Nice Menus 6.x-1.0
Includes: Nice Menus
Up to dateok
Poormanscron 6.x-1.0
Includes: Poormanscron
Up to dateok
Printer-Friendly Pages 6.x-1.0-rc1
Includes: Printer-friendly pages, Printer-friendly pages as PDF
Up to dateok
RootCandy 6.x-1.x-dev (2008-Mar-01)
Includes: RootCandy
Up to dateok
Switchtheme 6.x-1.x-dev (2007-Aug-31)
Includes: Switchtheme
Up to dateok
Theme Settings API 6.x-1.3
Includes: Theme Settings API
Up to dateok
Views 6.x-2.0-alpha2
Includes: Views

tsavino’s picture

Well I fixed it here is what I did:
Went in to the template.php on line 60 find this '. $class .' and took it out it referred to class=rootcandy could not find it any where in the css now it works fine.....quick fix...

zachkral’s picture

On WAMP, this issue started when I enabled clean urls. If I disable clean urls, it works again.
Deleting the '.class.' bit on line 60 of the template did not solve my issue either.

sign’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

I am removing this ajax functionality from the theme, sorry.
I might publish a module which will add this functionality again later on, when the theme will be in 1.0 version.

bomarmonk’s picture

I can confirm that I only encounter this when using Drupal in a subdirectory. I do have clean URL's enabled. When I use rootcandy in the main directory for my website, there is no problem. I am using Drupal 6.2 and the 6.dev version of RootCandy.