Unexpected behavior with the new setting/filter

Hi there,

I would like to report an issue regarding the new pll_admin_current_language setting/filter. It appears to have an unexpected behavior, where the filter sets the admin languages to null if the setting isn’t used and the lang parameter isn’t in the request. This is the case most of the time in our situation.

As a result, all the languages are loaded when there is a language specified in the admin menu, which is not the intended behavior.

Thought I would share this here, can’t imagine we are the only ones facing this issue. We fixed it by removing the filter for now.

• This topic was modified 1 year, 7 months ago by Duco Drupsteen.