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

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

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

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

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 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

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.


3

There wasn't really a question here, but... :) If you're using Solspace Calendar, which I assume you are since you've tagged it as such, you don't have to do this calculation, it's already built into the addon. For instance, you could do this: {exp:calendar:cal date_range_start="{year}-{segment_2}-first" date_range_end="+1 month"}


3

The notification settings for each Rating form are set via the notify, admin_template and owner_template parameters. The values which admin_template and owner_template correspond to are the notifications you setup in the Rating module control panel. So, say you setup two different email notification templates called admin_notification and ...


3

It turns out the answer is to turn off "Allow HTML" for all Freeform notification templates. I believe this is because Freeform will then leave the email as plain text allowing Postmaster to encapsulate it as HTML. Benek, I'm glad it's all sorted for you! :-)


3

Wrap your {exp:freeform:form} with an {exp:freeform:entries} tag pair and use conditionals to determine if there are more than less than 40 entries for the form. If there are less, present the form, if not, show a message: {exp:freeform:entries /* your other parameters */} {if freeform:no_results} {exp:freeform:form /* your other parameters */} ...


3

This turned out to be a bug when Tag is used with other addons that add cache variables to the Sessions object before it actually exists. A workaround for the issue will be in Tag 4.2.7, which we are testing for release.


3

I'd suggest doing this via an extension - your best bet is likely to use the freeform_module_insert_end hook, with one extra form input. So in your form, add a hidden input so the extension knows the url_title: <input type="hidden" name="channel_entry_url_title" value="{url_title}" /> This is untested, but it should work: public function ...


3

Change the lines {if freeform:error:{composer:field_name}} <strong> Error: {freeform:error:{composer:field_name}} </strong>{/if} TO {if "{freeform:error:{composer:field_name}}" != ""} <strong> Error: {freeform:...


3

This should work: Add the Freeform field tag: {freeform:field:file} to your form and choose the directory you wish the files to be uploaded to. Go to your notification settings in Freeform and add the {file} tag inside (swap file for your file field name). Make sure the Include Attachments checkbox is unticked and hit save. Now when you get notifications ...


3

You can create your own custom Composer Templates in Freeform, which allows you to pass parameters and variables similar to if you used {exp:freeform:form} or {exp:freeform:composer} in a template. In the Freeform CP. Go to "Composer Templates" and create a new template. Under Template Params, you can add parameters, such as an id or class to your form: ...


3

The more recent versions of EE (I think > 2.7) use CSRF in their forms by default so you automatically get a time sensitive submitted page. If you want to be more explicit and if the above doesn't work for you (i.e. earlier version of EE), I would add a hidden form field (which Freeform allows) and auto-populate it with a unique value - either a timestamp (...


3

Look at me. Found the answer on my own by poking around in EE-settings. It seems that Member Groups > Guests does not have the power to search by default. Set to "Yes", and you don't get that error anymore. Shame on me.


3

This is a known issue with Freeform 5.1.1 (and earlier) and EE 3.4.5+. This issue has since been fixed in Freeform 5.1.2 :)


3

I can duplicate this issue on my end as well. It seems that the Welcome Email feature only works on "No Activation" and "Self Activation" methods, but not on "Manual Activation". A "workaround" for now would be that you can just use the EE notification option to send the user a confirmation email instead. The template (to adjust what it says) for it is here:...


2

I am experiencing the same problem where it seems to happen when "Is field searchable?" is enabled within the field settings containing the Matrix field-type (not sure why??!)... I found a solution by changing line 7595 from $select .= ', field_id_'.$fields[$key].' AS `'.$key.'`'; to $select .= ', cd.field_id_'.$fields[$key].' AS `'.$key.'`'; Within mod....


2

I've done this before with NSM Transplant. But I've been slowly removing it in favor of Stash. This question inspired me to finish the process with this template, so thank you! First off, I think there might be a workflow problem with your question. I'm not sure how often people will be updating events but from what it sounds like is that when someone wants ...


2

When uploading a file too big for the Avatar restrictions, the error page displayed should already display a message such as The form you submitted contained the following errors The maximum allowed size for images is 50 kilobytes If you're looking to fetch and display the maximum dimensions for avatars dynamically and before someone attempts to ...


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