8
This query should work:
UPDATE exp_channel_titles t
SET t.status = 'pending'
WHERE t.status = 'open'
AND t.channel_id = 'x'
Change 'x' to your channel id.
7
Actually, the current version doesn't allow OR modifiers to the search. I think this would be a good feature request, and I can definitely work into the release after next. (v3.2)
In theory, the markup would be:
<input type="hidden" name="status[]" value="pending" />
<input type="hidden" name="status[]" value="open" />
But currently (as of 3.0....
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
A JOIN requires an ON clause too. Also, it's exp_channel_titles, not exp_channel_entries. Try this on for size as the sql parameter:
SELECT COUNT(cp.entry_id) AS post_count
FROM exp_category_posts cp
JOIN exp_channel_titles t
ON cp.entry_id = t.entry_id
WHERE t.status IN ('Open', 'open')
AND cp.cat_id = '{category_id}'
If you want to add more statuses to ...
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
If you're displaying your categories using standard category URLs (e.g., /products/category/central-vacuum or /products/C12), then you only have to add the status parameter to your Channel Entries tag (the category will be filtered dynamically based on the URL).
{exp:channel:entries channel="products" status="Featured"}
...
{/exp:channel:entries}
So in the ...
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
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
There were some parsing issues in Matrix in 2.5 for fields that had parameters.
Seeing as how you say that when using {playa_field status="open"} causes no entries to display leads me to believe that you're affected by that one.
Upgrade Matrix to the latest version (2.5.2 currently) and that should fix your issue.
3
If you have a specific list of entry_ids you want to change, you can run a query like this with your entry_ids separated by commas:
UPDATE exp_channel_titles t
SET t.status = 'pending'
WHERE t.status = 'open'
AND t.entry_id in (1,2,3,4)
3
It's in exp_channel_titles - EE stashes its data all over the place.
3
My add-on Postmaster is already available and by far the most comprehensive email solution for ExpressionEngine. It has a series of robust API's developers can extend to do really custom stuff. But it also includes UI's and plethora of options to send emails at just about any time without writing any code. v1.3 is in beta and brings a whole new Notifications ...
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
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
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
You could use something like POSTMASTER to create a trigger that would fire with any kind of change to the status or category of any channel. Using it even allows nice html emails if it strikes your fancy to keep things branded.
2
I couldn't work out how to make PHP work, but I did realise that I could use almost EE tag in the email - so I wrote a new plugin that would expose the PHP explode function to the template via a tag.
I've submitted the plugin to Devot-ee http://devot-ee.com/add-ons/string-explode-tag but the code is below as well!
<?php if ( ! defined('BASEPATH')) exit('...
2
I don't know of a way to display system errors in a template tag.
But you can use the Custom System Messages addon to move system messages into a template. This gives you more control over customizing the errors.
If you have JS skills, there's no reason you shouldn't be able to submit your login form using Ajax and show an appropriate error on the screen. ...
2
It depends for each scenario. For member registration & login with inline error handling, we have created a free plugin called FreeMember which is quite popular.
There are also other commercial member plugins which provide inline error handling and more (e.g. custom member fields using any fieldtype) such as Zoo Visitor, Profile:Edit and Safecracker ...
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}{...
Only top voted, non community-wiki answers of a minimum length are eligible
