Originally I recieved errors saying that the databases were not there.

In my drupal installation it has drupal_****** as my database tag.

and I think your module is freaking out because of that.

I LOVE the module but It is pissing me off seeing the error on every single page.

Please lemme know what you can do.

***ERROR***

* user warning: Table 'roadspill_vevtest.supernav_history' doesn't exist query: INSERT INTO supernav_history SET url = "http://vevtest.roadspill.com/admin/build/modules", title="Modules | VeV-KJ", uid="1" in /home/roadspill/domains/roadspill.com/public_html/vevtest/sites/all/modules/supernav/supernav.module on line 289.
* user warning: Table 'roadspill_vevtest.supernav_history' doesn't exist query: SELECT supernav_history_id FROM supernav_history WHERE uid="1" ORDER BY supernav_history_id DESC LIMIT 7, 1 in /home/roadspill/domains/roadspill.com/public_html/vevtest/sites/all/modules/supernav/supernav.module on line 291.

CommentFileSizeAuthor
#3 Picture 1.png251.77 KBjacine

Comments

chrisshattuck’s picture

chrisshattuck commented

Hi Roadspill,

Ah, yes, sorry about that. I have uploaded an updated version that works with prefixes, you can download the latest from CVS or when the next tarball is made (in 1-12 hours). Thanks for testing it out!

Chris

chrisshattuck’s picture

chrisshattuck commented
Status: Active » Postponed (maintainer needs more info)
jacine’s picture

jacine
she/her
Location New York
commented
Category: support » bug
StatusFileSize
new Picture 1.png251.77 KB

Hello,

I think I'm having a similar issue, but wasn't sure whether or not to open another ticket since the title explains my problem. I don't have a prefix on my DB, and I'm using a fresh install of D6 & today's SuperNav tarball. A hard refresh made the menu appear, but it seems incomplete and there are errors on every page as mentioned above (undefined index & variables).

See the attached screenshot. Note: I'm running this locally via MAMP.

Aside from the errors, this is a very cool idea. Thanks for sharing :)

chrisshattuck’s picture

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

Hi Jacine,

The errors you're seeing there are notice errors, which means your error settings must be set fairly high. You can supress these by changing the the error_reporting settings in php.ini, or locally by using something like this:

error_reporting(E_ALL & ~E_NOTICE);

I'm not sure where the best place to put this would be, but sticking it in a module or settings.php should do the trick.

Chris

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.