user warning: Duplicate entry 'garland-jump-menu:menu-gewerbliche-stellen-me' for key 2 query: INSERT INTO accublocks (module, delta, theme, status, weight, region, custom, throttle, visibility, pages, title, cache) VALUES ('jump', 'menu:menu-gewerbliche-stellen-menue', 'garland', 0, 0, '', 0, 0, 0, '', '', 1) in /Applications/MAMP/htdocs/accu01_drupal/includes/common.inc on line 3324.

What kind of info do you need more?

Comments

marcp’s picture

marcp commented

It looks like the region isn't getting set properly on the garland theme. Also looks like you're using a database prefix -- I've never tested that before. Can you test this on a site without using a database prefix? Or try a different theme when you add the jump menu?

quixxel’s picture

quixxel commented

I's no difference wether using garland or another theme.
But your prosumption is right:
by testing the module on an other site (without db prefix), the module does'nt create that warning
and the double block-entrys anymore.

quixxel’s picture

quixxel commented

Now I'm a little bit irritated.
I've tried these following steps.

I deleted all the prefixes in the db.
The result: the same warning (without prefix):
user warning: Duplicate entry 'garland-jump-menu-menu-gewerbliche-stellen-me' for key 2 query: INSERT INTO blocks (module, delta, theme, status, weight, region, custom, throttle, visibility, pages, title, cache) VALUES ('jump', 'menu-menu-gewerbliche-stellen-menue', 'garland', 0, 0, '', 0, 0, 0, '', '', 1) in /Applications/MAMP/htdocs/accu01_drupal/includes/common.inc on line 3324.

In the next step I deinstalled the module »Jump«.
Result: no warnings on admin/build/block

I installed »Jump« again (after running update).
Result: the warning is shown again.

marcp’s picture

marcp commented

I wonder if the block was still left in the blocks table even after you disabled the jump module. I know that there's no code in the jump module to remove any rows in the blocks table.

It works on your clean site. Great - we can get it to work on the other site too.

Try this on the site that used to have db prefix that is still broken with jump:

1. Disable jump module
2. Delete any rows in the blocks table that have 'jump' as the module
3. Re-enable the jump module

Hopefully this will fix your problem. We'll still need to figure out why it's broken on sites with prefixed tables. There are probably some missing {curly braces} around a table name in a SQL statement somewhere.

3dloco’s picture

3dloco commented

+1

same here...I am using a db prefix as well, although I am getting this error whenever I visit the admin/build/block page.

nicholas.alipaz’s picture

nicholas.alipaz commented

I am curious if this bug persists with the latest dev release from the 6.x-1.x branch? Could one of you guys test it. I am guessing it might be related to the ':' in the block's delta, but it seems far fetched. The latest version of dev has that removed.

nicholas.alipaz’s picture

nicholas.alipaz commented
Status: Active » Postponed (maintainer needs more info)
nicholas.alipaz’s picture

nicholas.alipaz commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Cleaning up queue, cannot reproduce, so please reopen if you figure out how to consistently cause this error.

shaneonabike’s picture

shaneonabike commented
Status: Closed (cannot reproduce) » Active

This is still happening for me in 6.x.1-1 ... should i be testing this with D6 - 1-dev?

vholden’s picture

vholden commented

When I enable the module on D7.8 I encounter an error message and are unable to access the blocks section. jump 7.x-1.x.dev is installed. Need a fix?