Notice: CMSB v2.64 Beta 2 (Feb 4th, 2014)

Damon, I reviewed the v2.64 beta 1 changelog, but am not clear as to whether this release addresses the login error with v2.63 I have been seeing frequently (and at least one client has seen):

"Security Error: No _CSRFToken exists in session. Try reloading previous page."

I've followed related forum posts, implemented suggestions provided, but still have the same issue from time to time (only with v2.63). If this isn't something that was pinpointed and resolved in this beta, could one of you have a look at one of my setups?

~ Deborah

Hi Deborah, 

Yes, this release resolves an issue that was causing CSRF errors (actually the underlying problem was that PHP sessions weren't writable) , but, if you have any other problems at ever and continue to get that or any other errors please email me direct at dave@interactivetools.com and I can take a look at your server and resolve any issues.

Hope that helps!

Oh Lordy -

I absolutely love Universal Error Logging!

:0)

Perch

+1 for Universal Error Logging

Hi Dave,

I obtained this warning:
PHP Notice:  Undefined index: REMOTE_ADDR in ../errorlog_functions.php on line 151

I think that is obtained since a script in cron mode. An idea?

Thanks!
Djulia

Hi Djulia,

>I obtained this warning: PHP Notice:  Undefined index: REMOTE_ADDR in ../errorlog_functions.php on line 151

Thanks.  You're right that's because it's running a cron.  I've fixed that for the next beta/release.

>If we had the possibility of activating or of deactivating the option, it would be really user-friendly.

You can deactivate the display of errors under: Admin > General Settings > Hide PHP Errors [x] Hide all PHP errors and warnings (still logged to error log)

And you can clear them all at once in the error log section by clicking the link in the banner at the top of that section:
[ Error Log: Any PHP errors or warnings from the website or CMS will be logged here. (Clear Log) ]

So you'd want to clear them after development is complete and from time to time, but I think we'd always want to log them? 

Let me know if you think it interferes in development in some way or any feedback.

Thanks!

Hi All, 

We've just released v2.64 beta 2 (beta list members will get an email with a download link shortly). 

If you're not already on the beta tester email list and you'd like to help beta test (you must own at least 1 CMSB license) you can sign up here: http://www.interactivetools.com/news/manage.php

Please post any feedback, questions, or bugs you find! Thanks! 

PS: If there are no more major issues this will be become the official release in the next few days.

Hi Dave,

>So you'd want to clear them after development is complete and from time to time, but I think we'd always want to log them?

In fact, I would like to be able to deactivate it completely.

The option can be interesting during the development. But with a site in production, it seems really risky for the Mysql server.

I have just made this experiment. I made a mistake in my code and my server was completely slowed down (several tens of lines of recorded errors).

I would not like to make this experiment again whereas I do not have the eyes on the Mysql server.
In the best of the cases, I will be informed by Google Webmaster. But I would not like that it is the customer. ;)

I use a function which records these errors in a file on the server. This approach does not have any negative effect on the Mysql server.

Thanks again!

Djulia