7
I don't know why this didn't occur to me before, but you can use {absolute_results} inside the Super Search tags. So, the lesson here is, if you need to use the channel entries style "search:field=" parameter to filter entries (NOT the Super Search "search=" parameter) and you need an accurate number of items returned, use {absolute_results} in place of {...
6
The recipient_email field accepts encoded recipient email values (see an example here), using the {freeform:recipient_value} variable in the field's name="" attribute along with a set list of recipients using recipient1="", recipient2="", etc parameters.
If you want your field's value="" to be an regular, non-encoded email address (as you have it above), ...
5
Having dug through the archived forums on Solspace I found this gem: http://www.solspace.com/forums/viewthread/11282/P15/
Basically it appears that adding the id="" parameter in the Channel Form/Safecracker form tag somehow breaks things. Removing that parameter seems to have fixed the issue.
Thanks to Anna for the really useful suggestions, though :)
5
Yes, if you replace {composer:field_output} with {freeform:field:{composer:field_name} attr:placeholder="Your Name"} in the Composer Template.
If you're using the Freeform channel custom field (i.e. using the field in {exp:channel:entries}), you'll have to select your custom Composer Template (containing the above code) in the top left dropdown of the ...
5
Just simple conditionals are parsed before the modules and plugins. Simple ones are the conditionals using just if and just early parsed variables. segment_N are early parsed variables, but your conditionals have an if:else.
So, try this:
{if segment_2 == ""}
{exp:calendar:cal date_range_start="today" date_range_end="today" show_days="1" pad_short_weeks="...
4
Any custom member fields you create in the admin should be available for use as fields on the registration form: http://www.solspace.com/docs/user/register/#form_fields . You can also use their select tag pair for custom fields:
<select name="your_custom_field">
{select_your_custom_field}
<option value="{value}">{value}</option>
{/...
4
For those who may not wish to spend $65 on Postmaster, you would probably be able to achieve this for free by generating an RSS feed of your entries, and then using something like Zapier (or ITTT) to push to Facebook and Twitter every time there's a new entry published. Just a thought.
4
Did you consider using Postmaster in place of MX Notify? I belive it supports variables in subject.
4
This works for logging into ExpressionEngine with ajax and showing the appropriate error, you would just modify the code where it checks for the error messages it returns to display to the user. You will need more conditions for the required fields.
function displayAjaxMessage(message, response_id)
{
if(typeof(response_id)==="undefined") response_id = "#...
4
The short answer is to just pass in either the entry_id or the url_title for this calendar entry, either of which should be easy enough to do on a detail page.
To know which would be best in your case I'd need to see key parts of your template(s), but here are a couple examples.
Option 1: Use the entry_id for your event from the URL:
{exp:seo_lite ...
4
This has been a common gripe with ExpressionEngine for years.
Here's a hack that I find works:
<input type="hidden" name="custom_fieldname" value="n" />
<input type="checkbox" name="custom_fieldname" value="y" {if custom_fieldname == "y"}checked="checked"{/if}>Bla bla</input>
The first value sets the field to "n". If the user checks ...
4
The XID (csrf_token in EE 2.8+) is used in POST forms to secure form submissions. A quick test shows that the XID isn't required for GET form submissions, so you can remove this from your GET form without running into issues.
If you're using {exp:super_search:search} in your search form, the XID field is provided for you (it's a hidden field), and the only ...
4
The best thing to do is have Tag convert to lowercase. There is a setting for that under preferences.
3
I might be missing the goal here (you mentioned a plugin so this might be too simple), but you can very easily add a jQuery UI Datepicker widget to any custom form field in Freeform Pro. Just create a custom text field in the Freeform Pro control panel, lets call it Start Date:
Field Type: text
Field Label: Start Date
Auto-generated Field Name: start_date
...
3
I've done it on a site I worked on a while back. My memory isn't fresh, since it's been handed off to the client and my hands are completely off it, but I can tell you that it does work — it's just a bit tricky.
As powerful and awesome as Zoo Visitor is, you have to remember that you are basically duplicating data from EE's native member database into its ...
3
Testing Mo'Variable's {if ajax} and {if not_ajax} conditionals in a User error template showed that the content of these conditionals do not parse, or rather parse as empty. This is the code that was used in an error template:
{if ajax}AJAX{/if}{if not_ajax}NOT AJAX{/if}
The above parsed to nothing in the error template.
Error templates bypass the native ...
3
You could do this by using the inline_error_return="" parameter:
http://www.solspace.com/docs/freeform/form/#inline_error_return
For example, you could craft a special URL when inline errors are encountered, eg:
return="template_group/template/errors_found"
Then, in your template, use a simple conditional to display your "has errors" message:
{if ...
3
Instead of limit="10", try using event_limit="10". From the {exp:calendar:events} documentation:
http://www.solspace.com/docs/calendar/events/#event_limit
3
fond the issue, when using an index.html file as a site offline page causes the form to now work.
Removing the index.html and making the site live with the index.php file allowed the form to work
3
Calendar events do not use regular entry entry_date and expiration_date values, but rather specialized event data stored in Calendar itself. Since the EE simple search form uses the regular EE channel entries library, it won't be able to filter for upcoming events based on entry_date and expiration_date.
Further, occurrences of an event are not necessarily ...
3
Try capturing the entry_ids to set a stash value then use that value to define the calendars tag.
Grab the entry_ids for the events.
{exp:stash:set parse_tags="yes"}
{exp:channel:entries channel="education" disable="categories|member_data|pagination"}
{stash:event_ids}0{exp:playa:children channel="calendar_events" limit="5"}|{entry_id}{/exp:playa:...
3
For the first issue try changing <option val="">Select Category</option> to <option>Select Category</option>... specifically removing the val="".
I took a look at the Solspace Supersearch docs and I don't see that keyword is required. So try taking it out.
3
If you're going to be using a form submission to track your project requests all the way through and updating status along the way, I'd think the channel form would be the way to go. With Freeform Pro, you can't really do any editing from the front-end after the initial form is submitted. Users of the control panel can definitely access the form submissions ...
3
The error happens because, sometimes, the conditionals brakes after a stage of parsing. Example:
{if {x} != ""}
If, x is empty, the conditional will be turned into:
{if != ""}
Which doesn't make sense.
So, you can use:
{if "{x}" != ""}
Or the what the Template Class calls "short conditionals":
{if x}
I suggest you to try:
{if "{...
3
Actually, I would strongly suggest to upgrade add-ons first, then EE. This isn't only for Solspace add-ons, but any add-on for EE. Make sure you update your add-ons to the latest version available for EE1 first, then upgrade to EE2. Sometimes, you need to then upgrade the add-ons to the latest version available for EE2.
This usually gives you the smoothest ...
3
The User:Edit tag only allows updating of the fields mentioned in the documentation:
http://www.solspace.com/docs/user/edit/#form_fields
notify_how_email is not a valid option. Are you sure this is even a valid EE option (natively)? If so, what is it supposed to do?
3
Not sure this approach is going to work.
FreeForm expects you to define recipient1 and recipient2 as a parameter of the exp:freeform:form tag, they are then encoded on the server side and the html source only shows a hashed value for the recipient, not the value you are inserting dynamically.
If the method you described here were to be permitted then it ...
3
I don't believe so, no. Rating stores its data in its own database table, indexed to each entry via entry_id only, so the channel that entry lives in should not matter.
3
<input type="text" id="email" name="{email}"/>
This is why - you're posting an item whose key is an email address. EE treats this as malicious data (as it contains the @ character).
What you meant to write was:
<input type="text" id="email" name="email" value="{email}" />
Same goes for all your other inputs - you have name confused with value,...
3
Adding entry_id="{entry_id}" to {exp:primary_category} fixed it. This is not required in channel:entries but is required in Super Search results.
Only top voted, non community-wiki answers of a minimum length are eligible
