Thanks for the feedback.  I agree a mobile responsive backend is a good idea and logical next step, and I know it's been a while since we've had a release.  We're working on some big new features (a field library that is as flexible as the plugin system) but I'll see about getting a maintenance release out with whatever has been completed to date.  We know that people like to see progress in the form of frequent releases.

Also, I'm going to lock this thread, keep it for reference, and start a new one once we get the next release out.  We've completed a lot of things since this thread started and I'll re-assess current priorities and user requests.  Feel free to post a new thread yourself if you want to suggest or inquire about anything in the meantime.

Thanks again for all your feedback.  Cheers!

The "Development Plan" thread hasn't been updated in over a year and the last version release was over 9 months ago.

i would like to add myself to the requests for a responsive back end. For me it is becoming crucial as all of my front ends are responsive and clients are sometimes disappointed that the backend isn't.

Just a thought but have you thought about crowd sourcing the development costs. I know that a lot of plugins are a result of custom consulting. I can't afford to pay for you to custom design a backend specifically for me but I would be prepared to make a contribution. I was thinking in the region of $50. Anyone else agree that this is a good idea? Dave would this model work for you guys?

Thanks for the offer, but you've got enough on your plate.

I'll wait til the next release.

Jerry Kornbluth

Regarding a CSS backend, yes we agree that's where it needs to go.  We took on a few too many new features on our last update and it has slowed down the next release that is due.  But yes we need a responsive  design rewrite.

Jerry, if there's some specific places in the code where you want me to add a space I can do that as a short term fix.  Then future releases will either have that or improved CSS.

Thanks!

I've created a post here on how to fix the broken spellchecker issue:
http://www.interactivetools.com/forum/forum-posts.php?CMSB-2.53---Fix-for-broken-Google-Spellchecker-79165

Can you give that a try and let me know if it works? (Post any feedback on that thread).

Thanks!

The backend area of CMSB is functional but starting to become an issue as more clients are expecting to use mobile devices to maintain their content. Would love to see a move away from tables ... and/or even just hanging some style classes on elements so we could customize the backend a bit. I seem to recall creating a dummied up set of style guides with classes for this a year or so ago.
J.

What do you think about adding a default space to the end of any field prefix labels and info field labels, so we don't have to remember to do that each time?

Also for upload details (image attached)

Best,

Jerry Kornbluth

After seeing numerous spelling errors on client sites, I discovered that the TinyMCe spellchecker is no longer working on some sites. According to this archived forum post, we have Google to thank:

http://www.interactivetools.com/forum/forum-posts.php?postNum=2231560#post2231560

My question is, has there been a determination of how best to integrate spell checking again either now as a temporary fix, or for the next CMSB release?

Thanks.
~ Deborah

The function is

htmlPurify();

not

htmlPurfiy();

Thanks for catching that and pointing that out. I updated the post from Jason to fix the typo.

The function is

htmlPurify();

not

htmlPurfiy();

Thanks for posting!  htmlPurify() is a CMSB function that was added in version 2.51 which allows you to strip out unwanted tags from any HTML string.  You can use it like this:

$cleanHTML = htmlPurify($dirtyHtml);



When you do it like this, the default functionality is to strip out all tags except for

• a
• b
• strong
• i
• em
• strike
• br
• p

You can change this list by passing in a $config array that specifies which tags you would like to keeps  An example would look like this:

$config                 = array(); // Config options: http://htmlpurifier.org/live/configdoc/plain.html
$config['HTML.Allowed'] = 'a[href],b,strong,i,em,u,blockquote,code,strike,br,hr,p,span[style],ul,ol,li,blockquote,code';

$cleanHtml = htmlPurify($dirtyHtml, $config);


As for the next release, we have a number of new features in the works, but as these are still under development, we don't yet have a finalized features list.  Stay tuned!

Hope this helps

...we've got a cool new feature we're using in the forum called htmlPurify that filters only allowed tags through no matter what you submit.

Is this something on the near horizon for CMSB? And while I'm asking, any hints you can provide as to new features for the next release?

Thanks.
~ Deborah

Thanks! We've made this change and it will be available in future versions of CMS Builder.

Just to help eliminate some user confusion, would it be possible somewhere down the road to hide the "Tip: hold <Ctrl> to select multiple files" that appears with upload fields under "Add or Upload Files" link when the max number of uploads is set to "1"?

Thanks,

Jerry Kornbluth

I'd like to log my request for adding the ability to filter Newsletter subscribers so that emails can be sent to segments of the subscriber list rather than the current approach, which is all or nothing.

Thank you,

Greg

You can customize the wysiwyg interface in /lib/wysiwyg.php (just save it as wysiwyg_custom.php so it doesn't get overwritten when you upgrade), and we've got a cool new feature we're using in the forum called htmlPurify that filters only allowed tags through no matter what you submit.  So there's some options.  It seems lots of people want redactor so we'll likely add that as an option in the future.  We want to greatly simplify how the field library system works as well.

Unless of course Dave Edis has some HTMLArea easter-egg goodness back from the days of yore.

J.