After uninstalling 3.5
clearing cache
installing 3.x-dev
setting the global location of shadowbox to the new libraries location I am seeing these in my logs immediatley following saving the form

page not found Jan 2 2010 - 5:20am sites/all/modules/dh1,
page not found Jan 2 2010 - 5:20am sites/all/modules/d 1, 

For the first one dh1,

Location http://studio.verymisunderstood.com/sites/all/modules/dh1, 
Referrer http://studio.verymisunderstood.com/admin/settings/shadowbox/global 

for the second d 1,

Location http://studio.verymisunderstood.com/sites/all/modules/d%201, 
Referrer http://studio.verymisunderstood.com/admin/settings/shadowbox/global 

Comments

psynaptic’s picture

Status: Active » Needs work

Is this in watchdog that you are seeing these errors?

Can you create a new, fresh install of Drupal and reproduce this issue?

vm’s picture

yes these are in watchdog. Will set up a fresh install and add shadowbox and add screenshot of watchdog listing.

vm’s picture

Category: bug » support
Status: Needs work » Fixed

Ok fresh install does not produce these errors but on the new sandbox I did find one notice I'll post in a new issue. I'll work my way backwards to try and figure out what is masking as a shadowbox watchdog entry.

vm’s picture

ok looks like there is some conflict with dhtml_menu.module version 6.x-3.5 and your shadow shadowbox.
After switching the theme to garland I'm getting a page not found leading to the information below.

Location http://studio.verymisunderstood.com/sites/all/modules/dhtml_menu/dhtml 
Referrer http://studio.verymisunderstood.com/admin/settings/shadowbox/global 

Should I report this kind of issue to that queue?

vm’s picture

Status: Fixed » Active
vm’s picture

confirmed that with dhtml_menu disabled the page not found log entires are gone.

psynaptic’s picture

Project: Shadowbox » DHTML Menu
Component: Code » User Interface

Does anyone from DTHML Menu know what could be casuing this?

vuil’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

I close the issue as Closed (outdated) because of non activity since 2010 and it is for the outdated and non-supported 6.x branch.