6
Remove safecracker_file from your third_party directory. It has been deprecated (now rolled into the standard File fieldtype).
6
I've created an extension that'll let you do it.
https://github.com/jazonv/SafeCracker-HTML5-Attributes
In addition to data-foo="bar", it'll also lets you use autocomplete="no" and novalidate="novalidate".
(Inspired by this gist by Objective HTML)
Disclaimer:
I'm by no means a PHP/Add-on dev. I just wanted to 'have a go' too. Hopefully there's nothing ...
6
Easy to forget, but make sure you give the member group you want to edit the safecracker form the ability to edit that channel in member group prefs. "Can post and edit entries in: [your_channel_name]" selected for that member group (Edit Member Group > Channel Posting Privileges).
5
The {options:field_name} tag pair is actually a Safecracker tag, which only works with Field Pack 1.x out of the box. You can add Field Pack 2.x support by opening up system/expressionengine/config/config.php and adding these lines:
$config['safecracker_option_fields'][] = 'fieldpack_checkboxes';
$config['safecracker_option_fields'][] = '...
5
Tim,
currently this is not possible, but we do have some interesting ideas that would allow you to accomplish this in the next Assets release, which is currently in active development.
I don't have an ETA for you, but we are working on it
5
Your question is not very specific, so we can't give you specific answers... however EE can handle all of this stuff, but it does take some planning. Here are a few comments in no particular order that may help...
Firstly I'd recommend ditching Structure, as you'll be fighting it at every step for control of your URLs and you could also find that it hinders ...
5
{exp:channel:entries
channel="personal_trainer_directory"
limit="1"
dynamic="no"
author_id="CURRENT_USER"
status="open|closed"
}
{if no_results}
***DISPLAY IF NO RESULTS***
{/if}
{if status=="closed"}
***DISPLAY IF STATUS IS CLOSED***
{if:else}
***DISPLAY IF THERE IS A RESULT***
{/if}
{/exp:channel:entries}
Is that what you mean?
5
I've also been struggling with this exact same situation for quite a while, it seems to be an EE bug.
Here's what I did to resolve it. Your markup is fine, your member settings are also fine. The only member setting that is vital to this operation is the "Can edit entries authored by others" under "Channel Posting Privileges" in the Member Group settings.
...
4
It appears to be stemming from an error in the JS preventing the global EE object from being created.
Digging deeper I was able to identify the culprit:
{
"name": "Link in this site",
"key": "",
"openWith": "<a href=\"http://farpoint.fcs.uga.edu/facs/template\\" > ",
"closeWith": " < \/a>",
"className": "btn_Linkinthissite"
}
Note the ...
4
It's a known bug and will be fixed in the next version of Low Search. To fix yourself, open up /low_search/libraries/Low_search_index.php (v3.0.2), and look up line #79, which reads:
die('No collections found');
Change that to:
return FALSE;
...and you should be good to go.
4
Well, There are two ways to do so.
Server side:
In your {exp:channel:form} tag, Add parameter rules:captcha="required"
Client side:
Use jquery.validate.js to make field required.
Include this js library: http://cdn.jsdelivr.net/jquery.validation/1.15.0/jquery.validate.js
Put the class required in input field.
Use jquery to run the code before form ...
3
Bug fix mentioned here
http://support.ellislab.com/bugs/detail/20084
Please make sure these seemingly unrelated settings are set:
The original author’s group has to have “Include Members in PUBLISH page multi-author list?” set to “Yes”
The person attempting to make the edit must have “Can change the author name when > posting channel entries” ...
3
You might see this article http://www.sidd3.com/get-entry-revisions-in-expressionengine/. I hope, it would help you.
3
So, I've found a way to achieve this, which seems to work in the reduced test case that I created (Grid fieldtype with one column of text type and only one entry being entered in at a time). In the future, I'll create test that's a bit more complex and see if it becomes more involved. The code for this is:
<input type="hidden" name="field_id_9[...
3
You're likely looking at the new docs that just went up, for EE 2.7 (released yesterday).
Under EE 2.6.1, the parameter you want is called safecracker_head, not include_assets.
3
Try this inside your hook:
print_r($cf); exit();
This will let you inspect the structure of the object passed by the hook, and find where entry_id lives.
3
To output the information this worked for me:
<p class="grid-row"><em>Fav Style:</em><span>{options:member_favourite_drinks}{if selected}{option_name},{/if}{/options:member_favourite_drinks}</span></p>
... and to have this in a select list:
{custom_fields}
{if field_name=="member_favourite_drinks"}
<...
3
Turns out this was a bug. The bugreport (https://support.ellislab.com/bugs/detail/19837) says to do this, which has resolved it:
In the file system/expressionengine/fieldtypes/file/ft.file.php at line 147 replace:
container.find("input[type=hidden]").val(function(i, current_value) {
with
container.find("input[type=hidden][name*='hidden']").val(function(i,...
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
For developers:
Not easy, the display_field() method from wygwam gets its settings early on. However you maybe able to pluck apart the toolbars in the hook "wygwam_config".
See https://github.com/pixelandtonic/wygwam_super_admin_source for an extension that adds a "source" button for super-admins. You could use that as a basis to remove / set other config ...
3
I've had this same problem. I solved it by simply using {if segment_1 == "abc"} statements to not include my jQuery on any page (segment) that had Channel Forms loading it's own jQuery.
You can also overwrite the jQuery file that EE/Channel Form includes with your version of jQuery -- I have found EE's version to be slightly different to what I download ...
3
In this case, the POST submission would be rejected not due to XSS, but CSRF. It's not an appropriate API to use for continuous submission from an external source.
I haven't used Reinos' add-on, but depending on the third-party's flexibility, their aptitude, and your custom field requirements, it's possible that your needs would be covered by the native ...
3
You could use the Instructions for your question text:
<label>{instructions:my_field_name}</label>
v2: https://docs.expressionengine.com/v2/add-ons/channel/channel_form/index.html#instructions-my-field-name
v3: https://docs.expressionengine.com/latest/channel/channel_form/index.html#instructions-my-field-name
2
I think, you need to look into that channel preferences under "Channel Posting Preferences". You can see "Default HTML formatting in channel entries" and set it to "Convert HTML into character entities".
I hope, it would work for you.
2
I know it's a bit old but for someone looking to change some parameters (like the return value) on submit by JavaScript - the reason it's not possible is that EE uses the meta tag which is an encrypted string containing some of the information. So, to change the value you would need to recreate that encryption. Look in the file Channel_form_lib.php for more ...
2
Matt, two options for you.
1) Easy: pass a segment variable to the safecracker form, then use 2 if statements (rather than an if else) to set the return values you need. That means youll need two different links pointing to the safecracker form.
2) More work: create an extension and use the safecracker hook - channel_form_submit_entry_end to redirect to ...
2
You'll want to actually use multiple hidden fields, each adding to an array:
<input type="hidden" name="cf_playa_field[selections][]" value="123">
<input type="hidden" name="cf_playa_field[selections][]" value="456">
You could also potentially write an extension to rework the POST data if you absolutely must submit the values in one field.
2
I don't think the {username} global variable is parsed early enough for it to be used within a parameter as you have there.
A couple solutions:
1) You could use Rob Sanchez' Mo' Variables add-on, which adds early parsed member variables.
2) Is the username really necessary within your return URL? Since you are redirecting to the ENTRY_ID, you should be ...
2
Ben Croker of PutsYourLightON has been working on an API specifically designed for CRUD functionality. You should take a look at it here... http://www.putyourlightson.net/open-api
And here is the repo for it... https://github.com/putyourlightson/open-api
I have messed with this some and it has some great potential.
2
Safecracker (and Safecracker File fieldtype) is deprecated for EE 2.7+. Read about it here: http://ellislab.com/blog/entry/expressionengine-2.7.0-released
You have to use the native File fieldtype (instead of Safecracker File fieldtype) with the new native Channel Form module.
Then, you need to make sure your Guest member group has permission to post/edit ...
Only top voted, non community-wiki answers of a minimum length are eligible