after I turned on this module the browser redirected to this style of address

http://www.bastardgeek.com/mynav?right_frame=http://www.bastardgeek.com/...

Now I get 404

Not Found

The requested URL /mynav was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.2.4 (Ubuntu) PHP/5.2.3-1ubuntu6.3 mod_ssl/2.2.4 OpenSSL/0.9.8e Server at www.bastardgeek.com Port 80

Comments

chrisshattuck’s picture

chrisshattuck commented

Ah, it looks like you don't have clean URLs enabled. I didn't test for that, unfortunately. I'll post back when that's fixed.

Thanks!
Chris

chrisshattuck’s picture

chrisshattuck commented

Hey, sorry for the clobbering, hopefully we can get this fixed quick. ;)

Okay, I tested with clean URLs disabled, and it didn't give me any grief, so something else must be causing the problem. Are you using CVS or the tarball? If you're using the tarball, it could be that it hasn't updated to reflect the latest changes yet. If you're using CVS, can you check what version you're using?

Thanks,
Chris

yngvewb’s picture

yngvewb commented
Category: bug » support
Status: Fixed » Active

I can confirm the bug:

http://127.0.0.1/dev/drupal-6.0/mynav?right_frame=http://127.0.0.1/dev/d...

The tarball for both Drupal 6.0 and 5.0 doesn't support clean urls. However, everything works perfectly with clean urls turned on.

Stompeers, this module is just so amazing! I am already addicted to this module, and I love it! :-)

chrisshattuck’s picture

chrisshattuck commented

Glad you like it, yngvewb!

I figured out the problem: I needed to clear my cache before testing non-clean urls. I have fixed the problem and updated CVS.

Thanks for pointing out the bug, I appreciate it.

Chris

Erikz’s picture

Erikz commented
Category: support » bug

I can confirm the bug too.

Can anyone help me out how to get out of this mess? I can't reach the config pages to remove the module.

Thanks,
Erik

chrisshattuck’s picture

chrisshattuck commented

Sorry about that, you can either update the module via CVS or download the next package, or you can remove the supernav_footer() function from supernav.module. That will prevent the redirect from happening so you can uninstall it.

Thanks,
Chris

chrisshattuck’s picture

chrisshattuck commented
Status: Active » Fixed
Compactman’s picture

Compactman commented

Thanks Stompers I'll try the CVS and then if that doesn't work I'll remove the function like you said.

Compactman’s picture

Compactman commented

K I turned on clean urls and the issue seems to be fixed

Also turning off the footer function worked so I could get back at the site. Thank you.

g76’s picture

g76 commented
Category: support » bug
Status: Active » Fixed

same problem, but 5.0 version, running v5.6, currently using javascript tools active menu. Clean urls are enabled. I didn't even enable the module, just unpacking it in sites/all/modules directory caused the error immediately. Any help would be much appreciated, it's a great module and I look forward to using it. thank you for the hard work.

-Jen

chrisshattuck’s picture

chrisshattuck commented
Status: Fixed » Postponed (maintainer needs more info)

Hello, Jen,

I haven't been able to duplicate your problem. Drupal shouldn't be including the Super Nav files unless it's installed, so it could be that something else is causing the problem, I would think.

Are you getting a 404 after you add the module files, or some other kind of error? If you could, please copy the error and paste it in here so I can take a look.

Thanks,
Chris

g76’s picture

g76 commented
Version: 6.x-1.x-dev » 5.x-1.x-dev

Hi, thanks for the help. I downloaded your latest release. It did not enable supernav automatically this time. I enabled it and this is the error:
Not Acceptable
An appropriate representation of the requested resource /mynav could not be found on this server.

Apache/1.3.39 Server at www.cvcvision.org Port 80

-thanks, Jen

chrisshattuck’s picture

chrisshattuck commented

Hi Jen,

I did a search in Google and Drupal for that error and it looks like a couple of things might be causing the issue. If you were able to check your Apache error logs, we could know for sure. It looks like it could be a mod_security issue (Read here for a fix), or it could be an error causing by trying to access a non-existent file or at least something along those lines.

If you have time, go ahead and see if you find anything that seems to fix it for you and post back here. Apparently, it's a server configuration issue, rather than an actual bug, but it would be good to have a fix posted here so other folks know what to do.

Thanks!
Chris