Dadabik 12.2 - issue with public user

deep64blue

DaDaBIK Guru
In dadabik v12.2 if you have a public user defined ($username_public_user) then the language and login buttons no longer appear in the top right hand corner.

Tested on a 12.1 -> 12.2 upgrade and on a fresh 12.2 install, both show the same behaviour.

dadabik12-1.png


dadabik12-2.png


If you disable the public user everything works as expected.

Code:
Your current DaDaBIK version
You are using DaDaBIK version 12.2-Aveto platinum, installed on 07-29-2024 (installation code: 1986766a7b197d8232), the latest version of DaDaBIK is 12.2-Aveto released on 07-25-2024

System info
PHP Version: 8.2.12
mysql version: 10.4.32-MariaDB
Web server: Apache/2.4.58 (Unix) OpenSSL/1.1.1w PHP/8.2.12 mod_perl/2.0.12 Perl/v5.34.1
Client: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
 

eugenio

Administrator
Staff member
Hi,
thanks for submitting this.
I can't replicate the language selector issue (it appears in my tests), you are right that there is no login link and you have to manually type login.php in the address bar. I'll investigate more.

Best,
 

deep64blue

DaDaBIK Guru
I can't replicate the language selector issue (it appears in my tests)
If I have $languages_ar = array set in config_custom.php the language selector doesn't show.

Commenting out $languages_ar = array restores the language selector.

This is probably the correct behaviour but not how it worked previously!
 

eugenio

Administrator
Staff member
Hi,
I can't replicate this issue. Could you paste your $languages_ar? Starting from V 12.2, if you set in languages_ar only one language, the menu doesn't show up, but this is the intended behaviour. If your languages_ar as at least two languages, the menu appears.
 

eugenio

Administrator
Staff member
Ok, yes, it was more a bug in 12.1, fixed in 12.2:
When only one language is allowed in config_custom, the link to language selector in the header now disappears.

About the lack of login link, you are right it actually looks like a 12.2 bug but I'll investigate more before moving to the bugs forum.
 
Top