I've been running into this problem when creating new Vocabulary in the Taxonomy structure.

Warning: Missing argument 2 for taxonomy_options_list() in taxonomy_options_list() (line 1375 of /srv/www/htdocs/modules/taxonomy/taxonomy.module).
Warning: Missing argument 3 for taxonomy_options_list() in taxonomy_options_list() (line 1375 of /srv/www/htdocs/modules/taxonomy/taxonomy.module).
Warning: Missing argument 4 for taxonomy_options_list() in taxonomy_options_list() (line 1375 of /srv/www/htdocs/modules/taxonomy/taxonomy.module).

This error is further explained when reading the system logs:
For all the warnings - I receive the following error:

Notice: Undefined index: localized_options in menu_navigation_links() (line 1857 of /srv/www/htdocs/includes/menu.inc).

When creating new content for a content type containing Hierarchical Select, I also receive this error:

Warning: explode() expects parameter 2 to be string, array given in menu_node_submit() (line 722 of /srv/www/htdocs/modules/menu/menu.module).

So far as I can tell, the Taxonomy and Views are created correctly with no data loss - I just receive errors which tend to be offputting - or could result in larger problems down the road.

Comments

LongShot902’s picture

LongShot902 commented

Further reading of the "Missing Argument" warning has been noted here #1559410: Taxonomy module - Warning: Missing argument.
Otherwise - I'm unsure if this affects my other two error notices.

kars-t’s picture

kars-t commented
Assigned: LongShot902 » Unassigned
Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed"

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

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