I'm upgrading from Drupal 4.7, i18n to Drupal 5 and when I enable the i18n core module my menus won't work and are not displayed in menu settings (where you pick primary and secondary menus).
As long as I disable the i18n module, I can see the menus again.
Even if I create new menus, they don't appear if the Internationalization module is enabled.
This behavior is not related to the i18n-menu module, doesn't matter if it's enabled or not.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | i18n-menu-debug.sql_.txt | 17.01 KB | imerlin |
Comments
Comment #1
jose reyero commentedI fixed some issues in the latest commit, may be related to this. Please let us know whether this is fixed.
Comment #2
jose reyero commentedAlso, I forgot, make sure you run update.php after you enable the new i18n 5
Comment #3
wonderland commentedI have the same issue, but I'm using Drupal 5.1 with the latest i18n version. I *think* the issue appeared somewhere in between the upgrade from Drupal 5.0 to 5.1 and the upgrade to the latest i18n module. I was able to fix the issue by manually adjusting the database and assigning the correct language code to the relevant menu and item entries in the menu table. Not sure what causes this error, as it used to work in older versions.
..- Wonderland
Comment #4
imerlin commentedStep 1:
I've upgraded to the latest i18n but with my old Drupal 5.0.
I still can't see the menu's in 'en/admin/build/menu/settings'. Only 'Navigation' or 'No menu' (which kinda sucks).
Step 2
I've also upgraded to Drupal 5.1 and the situation is unchanged.
Step 3
I have no idea what is causing this. I'll include a dump of my menu db table.
Comment #5
imerlin commentedI've upgraded to the latest 5.1 version without success.
Comment #6
imerlin commentedFound the source of my problems.
The way menus were handled changed so I had alot of menus and menu items that had no language while my 'Multilingual' settings were set to 'only current language'.
After changing that settings I was able to see the menus.
Changing status to 'by design' because I'm guessing this is working as intended while I just had no idea my migration would turn out this way.
Hope my problems will serve others in the future :)