mclarets

@mrfm Thank you! Same here. I found that I could disable Media Cleaner in the Post type settings of Plugin Organizer for both posts and pages and logged in and not logged in and it still worked. But disabling it in the “Global Plugins” seeing of Plugin Organizer causes the problem as you noted. So you can have it disabled on the front end posts and pages in the Post Type settings of Plug in organizer. I guess disabling it the “Global Plugins” is too big a hammer. It would be great if the REST error message in Media Cleaner mentioned this because disabling plugins from the front-end using Plugin Organizer is so useful for plugins.

@andrewza Thanks so much for the rapid reply! Deactivating and reactivating fixed everything.

@andrewza Actually, pretty sure it doesn’t have anything to do with the TOS, because I just signed up a new test user, changed the membership expiry date to yesterday, and they can still access the members-only pages.

@andrewza, thanks for the very prompt reply!
Yes, they are listed in the Members List and under the column that says “Expires” is a date before today along with a whole bunch of people who signed up prior to the function that recorded the TOS. But these members accepted the TOS, it was just on an earlier version of the plugin where it wasn’t recorded.

When I select the “Expired Members” from the drop down select box, I only see one expired member listed who was one of my earliest members. No one else is listed as expired.

I wouldn’t want users to have to reconfirm that the accept the TOS, because they did that during checkout a long time ago and they have no need to reaccept the TOS or access my site. What I would like to see is the bug where an expired member who signedup before the TOS acceptance was recorded seems to be able to access members-only content even though there expiry date has past. Or a workaround where I manually change the N/A to to the signup date would be fine, but really they shouldn’t be able to access members-only content with an expired account regardless of the TOS. Thanks!

@mrpetreli No! The OP asks how to “limit the number of characters”. You can easily do this in regex, but who cares because Caldera doesn’t currently allow you to use Regex in the input mask. As you can see in your own screen shot, that’s not regex even though it uses braces { }.

An example of limiting the number of characters would be to only allow a user to enter 20 characters in a text field. You can only do this with Caldera’s limited input masks if you don’t allow users to enter spaces or punctuation intheirsentence. Please actually have a working solution before you suggest more things like regex.

• This reply was modified 7 years, 7 months ago by mclarets.

awesome! thanks for the quick response.

Has anyone found an actual way of limiting the number of characters in Caldera? The mask doesn’t use regex despite what @mrpetreli claims. For example, I can’t seem to require someone to enter “this sentence.” in Caldera field and limit it to 10 alpha-numeric characters including spaces. Seems like pretty basic functionality for a forms plugin and shouldn’t require premium add-ons or custom PHP functions when Caldera provides so much other great functionality in the basic plugin.

Update: I saw an older post in this forum that references https://calderaforms.com/doc/caldera_forms_field_attributes/ but I’m hoping there is an easier method that provides the user with some feedback on the max. characters allowed and doesn’t require custom PHP gists.

• This reply was modified 7 years, 7 months ago by mclarets.
• This reply was modified 7 years, 7 months ago by mclarets.

If on WordPress install the excellent free plugin called “WP Rollback”. Then rollback to version 1.10.9 which is the last version that seems to work on PHP 5.5.x or older.

@team-rs: what the heck, eh? Tons of excellent and secure WordPress sites are on PHP5.5.x or older.