What's the deal with Deno? We talk with a major contributor to find out. Listen now.
5

Have you tried using the {{ craft.request.url }} variable in your returnUrl setting? Also you should be able to format it like so: returnUrl: craft.request.url ~ "?success" More details about the craft.request model can be found here: https://craftcms.com/docs/templating/craft.request


4

Sorry about the trouble. We typically answer most tickets within 24 hours: Freeform: https://solspace.com/craft/freeform/support/ Calendar: https://solspace.com/craft/calendar/support/ If the Support Form isn't working for you, you can always email us directly at support@solspace.com :)


3

The issue is you don't have a variable named input. I changed the code a little by included a variable named value. To make sure the proper option is selected you would need to pass back to the template a url param name with the currently selected option value. If there is a param and it has a value it will add that value to the variable value if not value ...


3

There is an entire section here that discusses API integrations, including the ones that come with Freeform. http://docs.solspace.com/craft/freeform/v2/


2

By setting the action: "#errortag" seems to stop the form submitting if there are no errors. So instead I have added the following code and this seems to work; {% if form.hasErrors %} {% includejs %} $(document).ready(function () { $('html, body').animate({ scrollTop: $('#formErrors').offset().top-110 }, 1000); }); {% endincludejs %} {% ...


2

I was able to find a solution. It's probably not the best way to go, but it works. In the form add a new action: <input type="hidden" name="action" value="freeform/submissions/save"> which will override the standard action. It's the same form action Freeform uses to save entries in the CP. Then add the id you want to update as value=. For example: ...


2

Sorry, Calendar currently does not allow for importing of any events via ICS or other means. source: Kelsey Martens, Director of Software Operations


2

Not likely to be an issue for anyone in the future but just incase someone is looking at this... Turns out Freeform should be able to handle underscores in field handles. Just an oversight on the Solspace side and they're going to be patching in support for underscores shortly.


2

We've recently discovered that this feature is not always reliable unfortunately. However, we're working on addressing this and coming up with a better solution in the coming weeks. Sorry for any inconvenience.


2

There currently isn't any built in Location field for Calendar. We made add something like that in the future, but for now you can definitely use other third party field types such as VZ Address to handle this. :)


2

That error means that your Craft installation is choking on one of Craft's Composer dependencies that is using newer PHP 7.1 syntax and your current box is using PHP 7.0.x. Usually when that happens, someone did a Composer install/update locally using a newer version of PHP than what you have on then box you're getting the error on, then deployed the ...


2

Try contacting them on the Craft CMS Slack workspace. They have an account on there, it's worked for me in the past!


2

FreeForm actually has a Dynamic Recipients field that sounds like it will do what you're wanting. I believe you can choose to have it displayed as a select field, radio buttons, or checkboxes. Alternatively, you could probably create a little custom Twig and set up dynamic template notifications. I would think you should be able to switch the recipient ...


2

You'll want to make sure you include all of the Calendar field inputs in order for this to work. If you're trying to hide them for your workflow, you can set the fields to hidden, or wrap them in a div and hide them with CSS. :)


2

Solution for Freeform 3: Preventing duplicated field id: Set a custom field id prefix. Using the form handle might be a good id, as long as you're not using the same form twice on the same page. Preventing duplicated form id: Manually adjust the form id parameter to something unique.


2

When you're dealing with that many fields it's definitely a non-trivial undertaking but Craft does have all the tools you need to pull it off. Your plan B is probably the most solid option. Make a new section that houses the skill entries and then set up all the radio buttons on it you'll need. You can put fields on Users directly but it gets weird as they ...


2

It’s potentially possible with a custom module, but it would be far less effort (not to mention, more secure) to just apply the solspace form classes to the regular log in form.


1

Not manually but you can search for the field in your database. If the plugin uses the normal craft_fields you can copy it's settings and paste it in a new record


1

It turns out that the Calendar plugin provides a property named event.repeating that can be checked to determine if the event is repeating and then use event.readableRepeatRule property to output the last date that the event will repeat on.


1

Do you mean this? {% set eventOptions = { dateRangeStart: targetStartDate, dateRangeEnd: targetEndDate, limit: 15, search: "EndrepeatHandle:On date" } %} {% set events = craft.calendar.events(eventOptions) %}


1

From the action you are currently posting to a controller see here The example shows that in your case it would be looking for a plugin called "Freeform" with a controller named "api" and then within that controller there would need to be a "form" action. If this isn't there then the page will return a 404 or error as it cannot find the route. You may be ...


1

UPDATED RESPONSE... We were finally able to get to the bottom of this and traced the issue down to your site likely having a DateTime field with the handle date, and this was apparently something Craft was choking on. The next version of Calendar will fix this, but you can resolve this by renaming that DateTime field or patch this by looking for this code ...


1

This my solution, although it's not perfect. I set-up an entry loop within the form and included the following for a series of checkboxes: {% if loop.index == "2" %} <label> <input type="checkbox" name="{{ course2.handle }}[]" value="{{ course2.value }}" {{ course2.checked ? "checked" : "" }} /> </label> &...


1

It sounds like what you would ultimately need here is some sort of grouping of fields feature, which Freeform currently does not have. So I would lean towards saying there isn't a way you can do this purely in Composer, unless of course you had a very stripped down Formatting template, and relied heavily on HTML blocks inside Composer to simulate what you're ...


1

Unfortunately this is currently a limitation of Freeform. It expects that the option values are predefined for the field, and not dynamically loaded at template level. It's on our feature requests list to come up with a way to let users override this functionality. :)


1

There's a definitely a syntax error in your first line. ({ loadOccurrences: false }) should be: { loadOccurrences: false } Also, from their docs, the export method only shows one parameter being passed in and you've specified two.


1

If you want to do this without creating a plugin, a "cheat" way would be to use the entry id of the submitted form - that would guarantee that you have a unique number and, assuming they are being saved to the same section, they would be in sequence.


1

If you're referring to adding extra fields to what a calendar itself contains (for displaying additional content with Calendar object), then that currently is not possible. Only the built in options are available.


1

You'd do it from the Calendar's field layout page (https://solspace.com/craft/calendar/docs/calendars/), just like Craft entries, users, categories, etc.


1

The short answer is that freeform doesn't do it. The longer answer is that you can cheat with a cookie. I used a cookie. Used this plugin: https://github.com/nystudio107/cookies In Freeform's admin, I created a hidden field called "cookie validator" and added it to my form. On the page that my form lives on /form/, I added a cookie that sets a value of a ...


Only top voted, non community-wiki answers of a minimum length are eligible