7
Make sure that the member adding the entry is in a group that has access to the non-closed statuses. Before you do that, ensure a status group is assigned to the channel. Superadmins can use Open and Closed even without a status group assigned; but others can't - and that is the most common cause of what you're seeing.
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).
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
Remove safecracker_file from your third_party directory. It has been deprecated (now rolled into the standard File fieldtype).
5
If you have an Assets field called “article_images”, you can create a simple HTML upload input like so:
<input type="file" name="article_images">
<input type="hidden" name="article_images_filedir" value="1">
The first input is the actual File input, and the second tells Assets which upload directory to place it in.
In time, Assets will also ...
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
According to the docs the ENTRY_ID constant still exists and is what Rob is referring to in his reply:
http://ellislab.com/expressionengine/user-guide/modules/safecracker/index.html#return
Not positive though, one thing you may need to watch out for is required custom fields on the EE (and Safecraker) side of things. You could implement something on the ...
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
The plugin "Delete entries and comments" uses the channel API for deleting the entries so it respects the logged in member's group preferences.
It would be fine for you to set the member's preferences for deleting entries from Control Panel according to your requirements.
3
If you upgrade to the current version, 2.5.5, it is bundled within the install.
3
You can do it by using the {custom_fields} loop of SafeCraker. In case, you wouldn't like to show some specific custom fields, don't populate them using if condition.
Like:
{custom_fields}
{if field_name != "not_show_field_1" AND field_name != "not_show_field_2"}
[Custom field options]
{/if}
{/custom_fields}
Take a reference from http://ellislab.com/...
3
Because your freebie conditional uses an {if:else} statement, it is considered an advanced conditional. Advanced conditionals are rendered after module/plugin tags are rendered (see: Rendering Stages). The safecracker tag in the else condition is getting parsed and executed before the condition is evaluated. The solution is to split it into two simple ...
3
Safecracker only supports channel fields. You'll want to use something like FreeMember, Solspace User, or Zoo Visitor to update member data. (there are a few other addons that also do this, try searching devot-ee for them)
http://devot-ee.com/add-ons/freemember
http://devot-ee.com/add-ons/user
http://devot-ee.com/add-ons/zoo-visitor
3
You could check for the presence of the Safecracker library:
if (isset(ee()->safecracker))
Or check if you're in the control panel
if (REQ === 'CP')
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
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
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
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 ...
Only top voted, non community-wiki answers of a minimum length are eligible
