Problem: Unable to enable menu links within main navigation menu.
Running Drupal 5.7, i18n 5.x-2.2, and image modules. (I made sure to enable i18n modules BEFORE enabling core Menu module, as not doing so had caused problems on previous installs.)
To reproduce issue:
Go to administer->site buiding->menus.
On the List tab view, you will see a list of all menus and their menu items. Go to the Navigation menu, click on the option to "enable" the Image galleries link (link points to http://www.mysite.com/?q=en/admin/build/menu/item/edit/48).
Click on "Submit."
Result is a blank white page - menu item is NOT enabled.
NOTE: Before clicking "submit" you can try adjusting any of the settings (e.g. set Language to blank or English, set Parent item to Navigation, etc.) - the result will be the same.
I had the same issue with trying to enable the "Contact" link under the main Navigation menu as well.
I believe there is some kind of issue with how i18n is interacting with the menu module, but I don't know how to fix it. Any help would be greatly appreciated.
Contributed modules that I am using (listed in the order in which they were enabled):
poormanscron
image and image gallery
tinymce
imce
i18n (internationalization, translation, i18n blocks, i18n menu, i18n taxonomy)
Optional Core modules that are enabled:
Contact
Help
Locale
Menu
Taxonomy
Upload
Comments
Comment #1
apoc1 commentedI have the same problem. It's impossible to make my module page load (also gives a white page without any error report)
And besides that, Any 'Save' action related to the Menu.module results in a blank page;
Home › Administer › Site building › Menus
- Add a node, link name and hit save = Blank page (note: if you enter a wrong value, it will show the error, but when you fill everything in correclty like it should, you get a blank page)
Home › Create content
- Create content, fill in content name, fill in the info in 'Menu Settings', hit save = Blank page (content is saved and listed in content, but the link you gave in in 'Menu Settings' isn't produced)
This is rather weird tbh, especially because it's a core module.
This problem exists for me since my update to Drupal 6.6x
Can anyone help?
Comment #2
jose reyero commentedCannot reproduce with 6.x
Comment #3
R.Hendel commentedDeprecated - D5 is no longer supported.