Warning: uasort(): Array was modified by the user comparison function in module_filter_new_modules() (line 231 of /srv/bindings/799979edb88344b0b50e569d55fd51b5/code/sites/all/modules/contrib/module_filter/module_filter.module).
FYI, I am running D7.18 on Pantheon.
Comments
Comment #1
goz commentedI can't reproduce this warning.
I try with D7.19 and module both 7.x-2.x-dev and git 7.x-2.x
I also try with patheon_migrate installed but no warning.
Can you list your modules (installed and not installed) ?
Do you have custom modules ?
Comment #2
Anonymous (not verified) commentedSince upgrading to Pantheon's variant of D7.19, the warning has changed to:
Warning: uasort(): Array was modified by the user comparison function in system_modules() (line 800 of /srv/bindings/799979edb88344b0b50e569d55fd51b5/code/modules/system/system.admin.inc).
I.e., there is no reference to Module Filter. However, it is only upon refreshing admin/modules that this warning is produced; other paths do not produce it. Other than the warning, there doesn't seem to be anything amiss.
Do you really want "drush pml" output for the total of 853 modules that are in my DEV environment, installed and not, including top-level and sub- modules?
I have lowered the priority to "minor", on your behalf, since that seems appropriate.
Cheers,
Bob
Comment #3
goz commentedI don't think it's only caused by module_filter but another module on your awesome module list.
I just open free pantheon account and install drupal 7. I download and enable module_filter 7.x-2.x-dev but have no error nor warning.
You should delete unusued module and see if warning still displaying. If it displays, try uninstall and delete contrib modules to see which one cause warning. Once we will know which module display warning, it will be easier to fix it.
Comment #4
Anonymous (not verified) commentedOk. I will keep you posted. Thanks.
Comment #5
cgmonroe commentedFWiW - I started getting this error recently. Turned out that one of my modules did not have a name or description set in the module's .info file. This caused the compare routine to add a 'name' key when it was used to compare with... and generated this error.
Just proof that it's probably a bug in a site module and not this one. Technically you could prevent it by checking if the compare keys are set... but that would slow down the sort for a vary rare occurence.
Anyway, hopefully this will point people in the right direct to fixing this error message.
Comment #6
sokarcreative commentedI had the same issue. I changed UTF8 encoding to ANSI encoding for the ".info file" in my own module. It works !
Comment #7
smustgrave commentedClosing as outdated after 9 years as we transition to Drupal 10.
I'm keeping an eye on the 7.x branch of this module, reviews and majors, but active work is going toward 4.x (supporting D10)
If valid for 4.x please reopen