LoginUser custom validation is not working on blog tutorial (v 4.3.1)

[aurelio1811]

Hello, my name is Aurelio Martinez, from Venezuela (South America). first all all, sorry for my bad english because my native language is spanish.
I am learning web development with php and prado framework, using php version 8.3.27 on linux mint 22.1 (xia), an prado 4.3.1.
but I have problems with blog tutorial. I installed prado using: "composer create-project pradosoft/prado-app blog", and then: "composer update", adding "pradosoft/prado-wsat": "^4" in the "require" section of composer.json. I am using mysql instead of sqlite as database.
Problem arises when testing LoginUser page: custom validator not working. Any input in the Username and Password control always generate same exception: "[Unknown Error] base64_decode(): Passing null to parameter #1 ($string) of type string is deprecated (@line 68 in file /var/www/html/blog/protected/vendor/pradosoft/prado/framework/Web/UI/TPageStateFormatter.php). (Error Code: 0)", as shown in attached file: "LoginUser_Exception.png".

I attached some other files. Any help will be appreciated. Thanks.

application.xml

other_files.zip

[ctrlaltca]

Hi, thank you for the issue. It's probably something we'll have to check in the code.
In the meanwhile, can you please check if editing php.ini to avoid errors for deprecated calls workarounds the issue?

# grep error_reporting /etc/php/php.ini
; error_reporting
error_reporting = E_ALL & ~E_DEPRECATED

[aurelio1811]

Hi. I changed error_reporting value. Older value was E_ALL, and new value is E_ALL & ~E_DEPRECATED, but now, other exception appears: "Bad Request - Page state is corrupted". I forgot to mention that same exception appears trying to input values in Contact page.

[ctrlaltca]

Yep, the underlying problem is probably a corrupted page state.
This should never happen on a production website, but it may be caused by some operations during development
You can either try to:

• delete the contents of protected/runtime/application.xml-4.3.1, so that the app starts on a fresh state
• clean your browser cache or browse the page in Incognito mode, so it won't reuse the old "broken" session

[aurelio1811]

I deleted the contents of protected/runtime/application.xml-4.3.1 and cleaned your browser cache, and problems persists (Bad Request - Page state is corrupted).