⚓ T192575 `asort()` and `array_unique()` expects parameter 1 to be array, object given in "PF_ValuesUtils.php"
`asort()` and `array_unique()` expects parameter 1 to be array, object given in "PF_ValuesUtils.php"
Do you know what in the form definition is causing this error to occur?
I'm guessing it's one of either "values from namespace=", "values from category=", or (maybe) "values=". Could you see if removing any of those causes the error to go away?
Affirmative, removing "values from namespace=" makes the issue go away while "values from category=" and "values=" are still in there.
I believe it is "input type=text". Since $wgPageFormsSimpleUpload = true; is used only a button is shown as expected.
I guess you are right. :) This is actually not a form I created. I just happened to be the first one who happened to notice it.
Do you have access to the server that this wiki is running on? If so, could you put in a "print_r($f->mPossibleValues);" right above that line to see what is being passed in?
Hm, that seems fine... so maybe that's not the line causing the problems. In that case, I don't where the error is coming from.
Fair enough. Let's wait until others perhaps stumble on this with different clues or if it gets a serious issue at some point. There are currently indeed serious issues around with much higher priority I think.
@Jaideraf I guess it will be nice to add you findings to this issue report? No?
On the respective wiki I was reporting this issue for the configuration parameter $wgPageFormsUseDisplayTitle is not explicitly set. So I believe it is set to true.
So, changing it to false will vanish the warnings (but you will lose the benefits of using DisplayTitle, wich in my case is not desirable).
Well, you added the print_r() statement to PF_FormField.php, which I thought would be helpful but turned out not to be. I'm asking about the results for print_r() statements in PF_ValuesUtils.php, where the error messages are originating from.