By laken on

We're having a vexing problem with the menu module and the menu table. Every time we access the menu administration page, and also when editing ans saving content, we get an extra row inserted into the menu table, always the "blog" menu entry, like so:

mysql> select * from menu where path='blog';
+-----+-----+------+-------+-------------+--------+------+
| mid | pid | path | title | description | weight | type |
+-----+-----+------+-------+-------------+--------+------+
| 109 |   1 | blog | blogs |             |      0 |   16 |
| 175 |   1 | blog | blogs |             |      0 |   16 |
| 176 |   1 | blog | blogs |             |      0 |   16 |
| 177 |   1 | blog | blogs |             |      0 |   16 |
| 178 |   1 | blog | blogs |             |      0 |   16 |
+-----+-----+------+-------+-------------+--------+------+
5 rows in set (0.00 sec)

Furthermore, when I access the "administer | menus" page, the link to enable the 'blog' menu has a link with a negative ID number in it, i.e.:

http://mysite.org/admin/menu/item/edit/-19

There is certainly no such mid in the database.

We had the menu on_the_fly installed, but have removed it in case it was causing problems. However these problems persist.

We are hoping to launch the site tomorrow, so please help!!

CivicSpace 0.8.1.3, 2005-08-19
Using Drupal 4.6.3
MySQL 4.1.12
PHP 4.3.9
Apache/2.0.52
CentOS 4 (Red Hat Enterprise Linux clone) with kernel 2.6.9-22.0.1.EL

⋅ Categories: Drupal 4.6.x

Comments

laken’s picture

laken commented

We're still having this problem - no solution yet. Please, someone take pity and post a response!

Thanks!

venkat-rk’s picture

venkat-rk commented

Try clearing the cache table of your drupal database. It is known to help in such situations.

If you have a database backup *before* you installed the menu_otf, perhaps you could try restoring the site from that backup? I would still advise doing this on a test site first and then on your production site.

Marc Bijl’s picture

Marc Bijl commented

Upgrading to Drupal 4.7 I thougth there was something terribly wrong with the upgrade script, as the menu table had loads of empty/unused rows with the word "blog" in it.

However, it proved to be a 4.6.6 problem already, as the backup sql file showed that these rows existed before in the 4.6.6 database. See this post: http://drupal.org/node/62514

Did you guys find out how this is caused? Any solutions? Best way to clean up?

Some else on this, may be? Thanks in advance!

___________________
discover new oceans
lose sight of the shore