Hi,

I recently moved a test site to live and everything is working fine except for one thing - I cannot edit or even access the primary menu admin pages. The site is dual language with Danish as the primary language and English as the secondary. I have created a Danish menu (primary menu) and English menu (secondary menu) and all is working perfectly but when I try to access:

mysite.com/admin/build/menu-customize/primary-links

...I receive the following error:

"Fatal error: Unsupported operand types in server_storage_path/includes/common.inc on line 1435"

Note that the menu IS working perfectly, I just can't access it to modify it.

I read about some issues with database names containing an underscore so I have migrated to a new db which doesn't have one in the name.

Another symptom (I think) is that in test, I was using clean URLs but now live they seem a bit testy. Even the Clean URLs admin page to enable and disable clean urls sometimes reports that the server was successfully tested and other times that it wasn't.

I'm unsure if these conditions are related. I have register globals disabled, PHP safe mode off and .htaccess support enabled. I've repaired and optimised the db in PHPMyAdmin - everything looks OK.

In terms of modules, it's pretty simple. I'm using 6.2 core modules:

Color, Comment, Contact, Content Translation, Database logging, Help, Menu, Search, Statistics, Syslog, Taxonomy, Throttle, Update status and Upload

Additional modules are limited to:

Poormanscron 6.x-1.0
Atom 6.x-1.0

Any suggestions gratefully received.

Cheers,

Rufus

Comments

Rufus Duffin’s picture

Rufus Duffin commented

I finally got around this (didn't get to the bottom of the actual issue) by creating a new menu mimicking the primary links I was using and disabling the primary links themselves. If anyone has any thoughts on what the issue might have been, I'd love to hear form you. I still have a copy in my dev environment and would love to test any solutions.

Thanks,

Rufus

keuvain33’s picture

keuvain33 commented

Solution is there :
http://drupal.org/node/180137

ainigma32’s picture

ainigma32 commented
Status: Active » Fixed

Problem solved so setting to fixed.

- Arie

Status: Fixed » Closed (fixed)

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

Jerimee’s picture

Jerimee commented
Version: 6.2 » 6.26
Status: Closed (fixed) » Active

Same problem here.

http://drupal.org/node/180137 does not present a solution.

Problem seemed to originate after a botched configuration of boost module, but boost has since been thoroughly uninstalled and htaccess restored.

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.