Postponed (maintainer needs more info)
Project:
Super Nav
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Feb 2008 at 14:20 UTC
Updated:
24 Apr 2008 at 20:09 UTC
Comments
Comment #1
chrisshattuck commentedHi Monkey,
That's a bummer. Probably the best way to identify the problem would be to use Firebug, and check out the 'console' after you get the error. There should be a 'post' row that you can click to expand. When it's expanded, it will show you the output of the action you just took. My guess is that something is causing an error, and not allowing the load to complete. If you see an error there, go ahead and paste it into a post here.
Thanks,
Chris
Comment #2
chrisshattuck commentedComment #3
Viybel commentedHi,
I have the same error and the Firebug console gives me a 500 Internal Server Error in POST http://example.com/supernav_bookmarks on jquery.js (line 13).
It works great in localhost. This module is amazing!
Thanks,
Vianney
Comment #4
chrisshattuck commentedHi Vianney,
I'm not sure what could be causing the error for you at this point. Since it works on your local install but not on your remote server, I would suspect it's a server configuration issue. Hopefully you or someone else with the problem will be able to do some testing, since I haven't been able to run into that problem myself.
One thing you might be able to do is look in the server's error logs to see what is causing the error exactly.
Keep me posted as to what you find.
Thanks,
Chris
Comment #5
hrmoe commentedhi -got the same problem in both internet explorer and firefox, so its not browser related. cant access the server log unfortunately
Comment #6
Yakumo commentedI've got this same problem ("There was a problem with the search, please try again") but here it's on localhost, I haven't tried uploading to a remote server yet.
The green 'loading' flash comes up at the top of the navbar, and then the error message appears, and the green flash stays stuck there.
Comment #7
Yakumo commentedThis was fixed immediately when I enabled clean URLs !
Turning Clean URLs off breaks it again shortly after cache cleared and page refreshed.
Comment #8
chrisshattuck commentedHi folks,
I have applied the following patch to the Drupal 5 dev version, which should correct the dirty URL problem: http://drupal.org/node/244459. Let me know if you run into any other problems.
Thanks!
Chris