- Posts: 71
- Thank you received: 0
I deleted that info while you were replying, in fact that was wrong : that occured only one time, yesterday. Not today.babynus wrote: Hi,
It is strange to get this last error only once a day... (unless you use the "remember me function")
It confirms that setting header comes too late...
NOTHING has be changed out of php area !babynus wrote: As I don't reproduce, I'm almost sure it come from one of your changes.
It is very difficult to find such issues because it can be due just to some space or line break before a <?php tag.
This sends some data to the buffer, and it is then impossible to modify headers.
It is for instance possible that you introduced some caracters before the <?php tag in the parameters.php file.
As you get this issue on connection and on disconnection whatever the actual page, I would suspect some change in a php file very frequently userd (parameters.php, projeqtor.ph, html.php,...)
… I tried with original 'model' files, still occurs !babynus wrote: I woukd recommend :
1) try with community version without any change to confirm this does not occur with community version
Please Log in or Create an account to join the conversation.
Still more weirdI deleted that info while you were replying, in fact that was wrong : that occured only one time, yesterday. Not today.
Issue is in PHP area for sure.NOTHING has be changed out of php area !
So the one you set back to original should not be suspected.… I tried with original 'model' files, still occurs !
I really don't thing this may be due to data. Forget this way.But I can’t remove updates in database. May be something in data added in migration ?
Yes.May be also a relation between these error messages and non-working "enforceUTF8" ?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
No, the errors messages still come… (and now with error in apache log due to that ob_clean, as advised in another topic).babynus wrote: Fixed it with an ob_clean after session_start.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.