We've released the final version here: 
http://www.interactivetools.com/forum/forum-posts.php?CMSB-v2.64-Released-Sep-3rd-2014-79933

There were a few (minor) bug fixes, so be sure to upgrade your betas (Build 1115 is the final release).

Thanks!

For everyone who wants to help test a responsive CMSB UI, we'd love to have your help!  Can you make sure you're signed up on the beta tester list if you are not already? http://www.interactivetools.com/news/manage.php  We'll take on the UI in the next major release.

For everyone beta testing the features in this release, we just released beta 3 (email sent to beta testers with download link).

Here's what's new: 

Email alerts on emails - Enable "Email PHP Errors" under Admin > General and get instantly notified of any PHP Errors you may have missed on ANY page that loads the CMSB libraries.  Be sure to enable this option and update the To: address in the email template to try this feature out.  Note that emails aren't sent more than once an hour and are only sent for NEW errors.

New Config Files - We've updated the generic PHP config files we include with CMSB (.htaccess and php.ini) and added PHP's new .user.ini config file.  These help address common configuration issues on many servers but aren't required.

Improved Error Logging - We now don't log more than 25 errors at a time, so if you have a page with an infinite loop or a LOT of errors it won't overload your mysql database.  

And a few more bug fixes (thank you for all the great feedback!) 

We're looking to close off development on this version, release it, and start on the next.  Please post any feedback, questions, or bugs you find!

Thanks! 

~ Deborah

However, a quick hack to CMSB would be to wrap the existing "data-sortable" table in a container, and make that container 100% wide, and overflow. ie.

.table-container{ width:100%; overflow:auto;}

<div class="table-container">

<table class=''data sortable'>....<table>

</div>

I don't think I'd much like the scrolling window!

However I'm with Jerry with regard to the improvements to the UI.  The layout is a bit too regimented. That's one of the reasons why I've started to do all my interactions through the front-end. It allows me to design the (form) layout however I want to suit each editor.

:0)

Perch

Just my two cents, I'd be happy if the page always scaled to the viewport as the default. In my situations (desktop, 26", 1920 monitor) the action column is never off by that much, just enough to require scrolling to see and use it (and maybe the last data column or two).

If you're really into redesigning the UI, I'd love to see the ability to stack fields horizontally, so we can make the UI a bit more intuitive for us and our clients.

For example, fields like city, state and zip would be cool to put next to each other, as would short number fields for things like max columns max images, days for grace periods, images to show, etc.

I'm sure that you can think of a scad of other things that don't necessarily benefit from being horizontally challenged.

I'd also love to see the ability to hide of groups of fields an easy, built in function. somewhat like the menu groups.

Many times there are lots of optional fields in between some mandatory ones, and that would help us clean up our acts.

If I think of any more, I'll let you know.

Maybe some of the folks that came to CMSB after using other platforms could weigh in as well.

best,

Jerry Kornbluth

I'll have a new beta out shortly with a max errors logged per page of 25.  On my development machine 25 mysql inserts takes less than 0.3 seconds.  

Could you give the new beta a try and see if you CAN get it to crash your MySQL server or even slow things down? I think this will resolve the issue.

Here's some sample code I wrote for our test plans:

require_once "lib/viewer_functions.php";
header("Content-type: text/plain");
$max = 1000;
foreach (range(1,$max) as $num) {
trigger_error("Simulating infinite loop ($num of $max)", E_USER_WARNING);
}
print "\n\n" .showExecuteSeconds(true). " seconds\n";
exit;

Thanks!

My (first) guess is that the code in the URL/Page would always trigger an error with the mod_security settings on your server, and maybe your host previously whitelisted "admin.php"?  Because the error doesn't occur when the file is named admin.php, right?

In any case, renaming the admin.php isn't required, so you can skip that step if it's causing problems on your server.  And feel free to email me steps to reproduce if you'd like me to take a look, we've been working on adjusting our config files to better support/work-around/disable some of the mod-security extensions that are too sensitive or cause problems.  My email is dave@interactivetools.com (email, don't post login details to the forum).

Thanks!

So you'd like it so that on the CMSB record list page the columns had a horizontal scroll bar if they were too wide?  But the actions columns were always visible?  

I'm not sure quite how that could work, can you let me know if you have seen an example anywhere else that works the way you want? 

Redesigning the UI is a top priority so that might be a good time for us to revisit that.

First of all, Universal Error Logging - LOVE it!

One feature I'm having trouble with is renaming the admin.php file, as suggested in the security settings.

After the admin.php is renamed, when I use the code generator for the Detail Page, Single Record sections, I see the following error page. It also trips ModSecurity on my server.

"Forbidden. You don't have permission to access /cmsdomain/admincustom.php on this server..."

The page URL looks okay to me:
http://www.domain.com/cmsdomain/admincustom.php?menu=_codeGenerator&_generator=cg2_detailpage&_showCode=1&tableName=about&whichRecord=first&recordNumCustom=1&showUploads=all&showUploadsCount=1&_null_=Show+Code+%3E%3E+

If I accidentally choose the wrong viewer type in the code generator, I also see the error then. I have no plugins installed.

I'm wondering if anyone else experiences the same, or if it's just my server security kicking in.

~ Deborah

I agree with Jerry. On the same note is there any way we can fix (hack) the width of the "Record Number" column in the list view of the editor? It's way too wide and takes up valuable space. Even on a big site it only ever going to be around 4 digits wide. I'd prefer to rename the column "Num"!

:0)

Perch

it's a rather small issue, but is there a way to address the viewport width of a record list so that it always fits the width of the browser?

I'm using Firefox (PC), and have always found (up to 2.63) that if I have a number of ListPage fields that display as columns in a record list, I have to scroll to the modify/erase for each record.

Same in IE, Safari and Chrome.

If it can't make it into this release, is there a hack that can be applied?

Thanks,

Jerry Kornbluth

>And if you like, I can put a plugin hook around it for a future version so you can disable it with a plugin.

Yes ! :)

>Maybe we could add a safety feature to not write more than 10 errors at a single time.

That can be a good solution with a loop which would not be coded correctly (infinite loop).

The slowdown occurred with variables which I had modified and which were used in a script which carried out a reading of the totality of the recordings (+3000).
Your proposal could in this situation limit the recordings in the errors log ?

Thanks again!

Djulia

You can manually disable error logging by commenting this line out at the top of: /lib/errorlog_functions.php:

// enable error logging
errorlog_enable();

And if you like, I can put a plugin hook around it for a future version so you can disable it with a plugin.

That said, it's designed to be used in production to help us catch errors that are triggered through live use.  It also logs a lot of debugging information such as the current user, form data, the symbol table, etc.  And in future we're going to add the option to have it email the developer/admin to warn of errors on the live site.  

It really shouldn't slow down your MySQL at all and even a couple dozen MySQL inserts shouldn't affect performance.  I'd be curious to know more.  Maybe we could add a safety feature to not write more than 10 errors at a single time.

And, of course,  if you'd like to keep using a different logging method that's totally fine as well!

Hope that helps.  Can you send me some details about what cause the server slowdown (or what was logged?) to dave@Interactivetools.com?  Thanks!

>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

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.

>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!

>Universal Error Logging

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

That can be useful during the development of the sites...

Thanks!

Djulia

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

I absolutely love Universal Error Logging!

:0)

Perch

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!

"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

*UPDATE Feb 4th* We've just released beta 2

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

The major new feature are:

• Universal Error Logging - A new admin menu "Error Log" logs errors from the CMS and on EVERY page on your site that loads CMS viewer libraries.  This is a major new feature and will make it incredibly easy to monitor, track and resolve even the smallest PHP error anywhere on your site.  
• Flash Uploader Code - We updated how the flash uploader works to address some compatibility issues people were having with some browsers and servers.  
• Dozens of bug fixes and improvements - Many minor bugs, issues, and annoyances have been addressed.  See the changelog for more details.

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! 

Thanks! :)