15 posts by 8 authors in: Forums > CMS Builder
Last Post: December 27, 2018   (RSS)

By KennyH - December 26, 2018

Along with the lines of "Insert Record Here" it would be great if we could Archive records with a single click.  This way, there are still in the database for historical purposes, but only show up when requested in the CMSB backend.

The plugin "Gray Hidden Records" was great until we started using it a lot. Now, there can be entire pages of Grayed-Out records showing up before you get to Active records when using this plugin. 

A working example of this scenario would go like this; A local spa/gym owner uses CMSB to keep track of memberships. When one of those members isn't active, they "Archive" the record by hiding it. It still shows up in the backend (and with the plugin we can make those records light gray) and does not show up on the front end. I would like to take it one step further and have those records hidden from both backend and frontend unless specifically asked for. This would allow them to go into the archive (or just make them appear) and make the member active again.

Now, before anyone suggests just using the Website Membership Plugin, the above example is just one of many. It's not just users I would like to archive. This feature would be great for a multitude of applications.

By gkornbluth - December 26, 2018 - edited: December 27, 2018

Hi Kenny,

Could you set the section to sort records by  'hidden' or whatever field you use to determine an expired membership, and then by 'name' or 'date', which would automatically put the expired records at the bottom of the list (this doesn't work well with dragSortOrder).

Jerry Kornbluth

The first CMS Builder reference book is now available on-line!

Take advantage of a free 3 month trial subscription, only for CMSB users, at: http://www.thecmsbcookbook.com/trial.php

By daniel - December 27, 2018

Hey Kenny,

That's an interesting feature, thanks for the suggestion! Give Jerry's solution a try in the short term, but hopefully we'll be able to add something a little more robust in the future.

Thanks,

Daniel
PHP Programmer
interactivetools.com

Hey Kenny,

Another idea would be to move the display members function to a front end report.

That way you could only show the members with active status, and show any other fields laid out in the way that best meets your client's needs, even as a spreadsheet if required.

Then using something similar to the recipe in my Cookbook called: UPDATING A TABLE VALUE WITHOUT RELOADING A WEB PAGE USING AN AJAXURL, the client could change a member's status when required.

A similar (part of) the report could show only inactive members with only a small change in code. For example, if you were using the hidden field to toggle activity, then just change:

  'where'    => " hidden = '0' ", to  'where'    => " hidden = '1' ",

Just a thought...

Jerry Kornbluth

The first CMS Builder reference book is now available on-line!

Take advantage of a free 3 month trial subscription, only for CMSB users, at: http://www.thecmsbcookbook.com/trial.php