6
The "limit entries by status" setting for the Relationship field controls what entries are available to select in the control panel - not what entries will display in your templates.
So if you have the field set to "any status", and you've selected child entries with both "open" and "featured" statuses, then your tag will need an explicit status parameter:
...
6
SQL is the best option to bulk update the entries. But you must need to be careful as wrong execution can stress you up!
You can use below query:
UPDATE exp_channel_titles
SET status = 'created'
WHERE status = 'open'
AND channel_id = '1'
AND entry_date <= '1262332799'
Replace the date value with UNIX timestamps of the date and channel_id you want ...
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
http://zenbustudio.com/software/zenbu should work for you, it has the ability to change statuses for batches of entries
4
You need to add status="not closed" to your channel:entries tags. If you do not specify a status parameter, it will always assume open.
4
It mainly goes down to processing order. When the order is successfully placed Store then does a little housekeeping to round off the order completion process. It will look to set a default status before checking for any extensions latching on to the store_order_complete_end hook. So walking through the process with your specific extension code:
Order is ...
4
Here's a basic setup for what you're trying to achieve, with the class .biggie representing the markup for making your entry big, and the absence of that class indicating a "normal" representation of your remaining entires.
NOTE: Since the default order for channel entry output is reverse date order (newest first) you do not need to specify any order or ...
4
While firing a query in DB, No matter you pass "Open" or "open". Both are same.
Your first question's answer is: As per EE Standards, It should be "open".
EE save "open/closed" in database, it shows in list page after making "first letter" capitalized.
3
It looks like there is a problem with the logic in your extension. You don't want to change the name of a particular status when the order is complete - you want to change the status of the order. I would expect it to look something more like this:
public function store_order_complete_end($order)
{
if (ee()->session->userdata('group_id') == 10)
...
3
If you don't want to spend money on an add-on just for this purpose, I found a bit of an inelegant solution.
I recently had to change the Status of hundreds of entries and used Ben Alman's bookmarklet tool to make things a little easier. It allowed me to run a small bit of jQuery on EE's Multi Entry Editor page and set each entry's Entry Status select ...
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 can't delete those as open is a default status parameter for channel entries. What you can do is create your custom status, and only give your client access to the custom statuses. This way Open and Close never show up.
3
Yes. Take a look at the add on MX Notify Control http://devot-ee.com/add-ons/mx-notify-control which should allow you to do this.
Alternatively, for even more flexibility take a look at Postmaster http://devot-ee.com/add-ons/postmaster
3
that is perfectly normal and expected behaviour.
To view content with status completed you need to add that to the "status" parameter in the channel entries tag, like so:
{exp:channel:entries status='open|Completed'}
More info here:
https://ellislab.com/expressionengine/user-guide/add-ons/channel/channel_entries.html#status
3
Custom category field?
Which defaults to open:
Then your template code:
{exp:gwcode_categories channel="example" depth="1" custom_fields="yes" linear="yes"}
{if cat_status == "Open"}{cat_name}{/if}
{/exp:gwcode_categories}
Note the additional parameter custom_fields="yes".
2
status="not closed" will be more efficient. When the Channel module is building its SQL query, it checks to see if there's more than one status being asked for. If it's one status, it uses WHERE status =. If it's more than one status, then it'll use WHERE status IN. = is more efficient than IN.
2
You could use Stash by Mark Croxton to accomplish that without multiple channel entries loops. Here is the kind of code I would use with the dev branch of Stash.
{exp:stash:set_list name="mylistname" parse_tags="yes"}
{exp:channel:entries status="1|2|3" channel="listing" orderby="random" dynamic="no" limit="15"}
{stash:st_title}{title}{/stash:...
2
If you don't mind using Stash, you could achieve it that way.
The idea is that you output all the channel entries once, and not worry about the order.
You 'stash' the appropriate fields inside a list, where you will retrieve it later.
{exp:stash:set_list name="my_listing" parse_tags="yes"}
{exp:channel:entries status="1|2|3" ...}
{stash:the_title}{...
2
It really depends on how you're going to filter the entries. Categories would work if you're going to rigidly filter by specific months, durations, and seasons (ex: output holidays that depart in January, or that are 14 days long). Just have one category group per filter type (Departure Months, Duration, Season).
However, if you need to filter based on a ...
2
Check your permissions within the status group. Each group that is creating/editing content needs to have permission to each status. So, if the open status is only available to Super Admins and your account isn't a Super Admin, then it won't show Open as an option for you.
2
I use Better Workflow for this. It makes life much easier when handling scenarios like what you have here. Another approach I have used, while not as pretty, was to establish statuses, and build a exception to block all but local traffic through a firewall (in this case, using Big IP from f5) and building multiple templates. One of the templates will be ...
2
You can use the native entry statuses to accomplish a draft status. If you review the documentation on statuses, you'll see how you can edit the status group and add draft alongside open and closed.
Then, you'll just have to make sure your status group is assigned to the channels you're using to publish the content.
By default, the {exp:channel:entries} ...
2
I have come across an old safecracker extension that seems like it may be able to be modified for use with channel forms to handle this, as well as also protecting any other fields from being tampered with that are not explicitly allowed by the extension:
http://devot-ee.com/add-ons/safesharpener
It may be possible to just try editing the hook name to the ...
2
This is most likely caused because a "Status Group" isn't selected for the channel.
To check this, go to Admin > Channel Administration > Channels, then click on "Edit Group Assignments" for the channel having the issues. Your channel probably has "None" set for the "Status Groups". Change that to "Default Status Group" and click the Update button.
2
If you are only trying to display a single featured entry and if no featured then a single entry with the status of open. I'd do the this. Order your results by status and allow featured and open status entries and then sort it to to look for featured first then open. I think that might be sort="asc"
So heres what your code will look like.
{if ...
2
The default number of entries returned by exp:weblog:entries is limited to 100. You can set a limit parameter to whatever you like and over-ride this limit.
{exp:weblog:entries weblog="listings" dynamic="no" status="not closed" orderby="title" sort="asc" limit="400"}
Be aware that there is a also chance you may run into memory and performance problems ...
2
I would use the
entry_submission_ready
extension hook, and write a mini-extension that looks at the meta array in the api for the entry status value, and compares it to the previous value for that entry (if it exists). Quick example hook function that could work for your situation:
function entry_submission_ready_my_hook($meta, $data, $autosave)
{
// ...
2
For best performance and simplicity...
{exp:query sql="SELECT status as status_label, count(*) as total_results FROM exp_channel_titles GROUP BY status_label"}
{total_results} results for {status_label}.
{/exp:query}
You can just output a specific status using a conditional:
{if status_label == "test"}
{total_results}
{/if}
Or you can refine the ...
1
I don't think there is an easy way to accomplish this natively.
One thing you could try is saving a custom "status" item_option when adding to cart. Give it a value of "pending" or something similar.
The downside is you'd have to type the status in manually.
On the back end you could write a little add on that would replace the default order items input ...
1
Changing the status in EE's backend will not run any of those actions. At present there is no method to do what you request through changing EE's statuses.
The status itself is currently incidental to the payment collection system. The statuses are changed by outside actions, but changing the statuses manually won't reciprocally initiate those actions.
An ...
Only top voted, non community-wiki answers of a minimum length are eligible
