Lately, most of our time has been spent on version 2.0 features. However, one of the top ten most highly voted features made it into version 1.07.08: Repeating Events. We hope you enjoy it. We have tried to build it with the flexibility you'll need for your form building. Here's how it works:
- Create a new form or edit an existing form. Add a date field for the event date.
- Add a dropdown or radio button field to the form. This field will be used to set the repeat period for the event. You can add values like "Daily", "Weekly", "Monthly", or "Yearly" to this field. If you want more options, just check the "Use separate values" option for this field. Then you can add text like "Every other week" with a saved value of "+2 weeks" or even just "2 weeks". Here's an example of what your dropdown/radio button field may look like:
- You may also add a date field to your form so the user can select an end date for their repeating event.
- Next, create a new Calendar View or edit an existing Calendar View. For "Event Date", select your event date field. Leave "End Date or Day Count" set to "No multi-day events", unless you want to have multi-day repeating events. For "Repeat", select your repeat period dropdown/radio button field. For "End Repeat", select the date field where the user sets the end of their repeating event.
- Voilà! Your calendar is now set up for repeating events.
Other Cool Features
Besides repeating events, we were able to fit a few other small features into version 1.07.08.
View Enhancements
The database call for Views has been optimized so it can now handle more data. We tested with 14,000 entries and it didn't have any trouble at all.
Styling Options
If you want your forms to be styled by Formidable without annoying conflicts with your theme, you now have the option to override your theme's styling. This option has been added to the Formidable Global Settings > Form Styling > General tab.
New URL shortcodes
This used to require custom code, but now you may use [server param="REQUEST_URI] in a text field to get the URL of the current page. Use [server param="HTTP_REFERER"] to get the URL of the previous page.
Shortcode Improvements
- A drafts parameter has been added to the formresults shortcode so you may easily show a list of drafts.
[formresults id=x drafts=1] - An x_order parameter has been added to the graph shortcode so you may prevent alphabetical ordering. This is helpful if you're using a checkbox, radio button, or dropdown field in your form and you want your graph to keep the same order as the field's options.
[frm-graph id=x type=bar x_order=0] - We added the != option to frm-stats shortcode options, just to give you a little more flexibility with your statistics.
[frm-stats id=x type=count value!="Red"]
New Hooks
- Added frm_csv_sep hook for changing , to a different separator for checkbox fields
- Added frm_delete_message hook to customize the message shown after an entry is deleted
Bug Fixes
- Don't enforce the max character limit on form builder page
- User ID fields now work correctly in conditional logic for emails
- Leading comma removed before values saved in an autocomplete/multi-select dropdown.
- Order correctly with scale field
- Trim field description to prevent blank, uneditable descriptions
- Allow email addresses in the user ID column for cdv import
- Update French translation
- Allow text fields to be used for email recipients
- Check if "ORDER BY" and "LIMIT" are already included in query before adding them again (Fixes Zapier getting forms)
- Delete correctly from item_metas after post is created
- Exclude child categories in regular dropdown fields
- Graphs now work correctly with checkboxes
- Allow blank userID field when entry is created on the back-end
After updating to this I started getting 500 server errors on form submits on some of my sites.
Rolling back to the last version seems to resolve it? Any other reports of instability?
Sorry for the late response. This should be fixed now for version 1.07.09. Let us know if you have any trouble with this newest version.
Hi, what is the '!= option' for? Thanks
!= means "not equal to". This just adds a little more flexibility to the stats shortcode.
Is there any way that a recurring event could be set to specify a certain day of the month (e.g. the first Sunday) rather than selecting the same exact numbered day of the next month?
Yes, this has been added to version 1.07.10, which is currently in the release candidate stage.
After installing this version, you can set the saved value to "First Sunday of [frmcal-date]". This will make it repeat the first Sunday of every month. If you have any trouble with this, feel free to post in the help desk.