Yes, that is correct.
But I guess to answer the question florian asked… no, the module will not do any type of sorting automatically. It’s only purpose is to manually adjust display order. And with 800 entries, manually sorting that would be such a pain! So at least ordering by title gets you a closer approximation.
I think I will add a custom field and enter the title number in the cutom field. then adjust the database field of the custom field to be numeric and then i should be able to sort=”asc” and orderby=”title” and it should order it starting with the smallest number …
thanks for your help.
According to this post, version 1.0.1 should have fixed the bug where reverse related entry orders don’t get update because they’re cached. However, caches are still messing up REEOrder as of 1.2.
This is happening because REEOrder isn’t clearing the relationship caches (just all other caches). To fix replace line 569 in mcp.reeorder.php with either:
$FNS->clear_caching('relationships');
Or to clear all caches including relationships:
$FNS->clear_caching('all', '', TRUE);
Hi,
Again just to reiterate what others have said, thanks for this great module I’ve used it a few times on other sites and it all works great .. however ..
I have installed 1.2 on a new site and for the life of me cant get it to work. It shows up in the modules but It does not appear to save any preferences when I try to set it up, I also tried to uninstall reeorder but each time I do this when I go back into the module tab it still shows as installed.? Sorry to be a pest but is there anyway I can remove all references to reeorder and start again?
I’ve tried all sorts such as deleting from my server and re-installing fresh copies etc .. I’m feeling dumb and am definitely stuck. Any pointers from anyone? thanks in advance.
Hi Cocoaholic. This is a great module and extension.
Does anyone know if the extension part is compatible with Brandon Kelly’s Gypsy Extension.
When both are used the order field is only hidden for the original weblog the field group is assigned to. All the other publish pages display a javascript error and still show the order field.
Any ideas for a fix?
Feature Requests - 1. Ability to view category/ies that are assigned to each entry you are sorting. (Useful for sites that utilize category-based navigation) In an ideal world, you would be able to select which category you want to REEorder so you’re not loading the screen with all entries from all categories. 2. Option in Preferences that allows you to view/hide expired entries. Thanks! Love the module!
+1 for being able to select which categories should be REEordered. This would make it a lot easier to use when you only want to sort entries assigned to a specific category.
Great module thanks!
Is there any way I can stop new entries which have not yet been ‘ordered’ from appearing at the top of the list?
This causes a problem for me, as when new pages are added to a section and the site is live, they temporarily appear as the first page in that section which is unlikely to be the desired position.
I thought I could work around this by allowing a Draft status to be reeordered - then I could set the position of the item while it is a draft and then change status to Publish. However, I have found that when you change the status of an item, the position is lost. So it becomes un-reeordered!
Summary of problem/Bug?: Changing status of reeordered entry removes order
Is there any way I can stop new entries which have not yet been ‘ordered’ from appearing at the top of the list?
Yes, you could prevent the entries from showing using a conditional on the custom field you use for ordering. If the order field is empty, don’t show the entry. Something like this around your entry tags, inside the weblog tag:
{if order_field != ""}
entry tags
{/if}
Summary of problem/Bug?: Changing status of reeordered entry removes order
I’m pretty sure it doesn’t ‘remove order’ because that would mean it actually empties a custom field! That would be very bad 😉
When you add a status like ‘Draft’ to the weblog, make sure you allow that status to be re-ordered by checking the box in REEOrder Preferences as well. I just tested this and this seems to be the behaviour you are seeing. (if you don’t check it the entry will not be shown in the list of entries to be re-ordered.
Hope this helps, Elwin
I suppose you could do something like this:
{exp:weblog:entries weblog="test" orderby="order_custom_field" sort="asc"}
{if order_custom_field != ""}
{title}
{content}
{/if}
{/exp:weblog:entries}
{exp:weblog:entries weblog="test"}
{if order_custom_field == ""}
{title}
{content}
{/if}
{/exp:weblog:entries}
Thanks Pushloop and Cocoaholic - I should’ve thought of that! Problem solved 😊
I’m pretty sure it doesn’t ‘remove order’ because that would mean it actually empties a custom field! That would be very bad
Yeah, that doesn’t seem to be happening anymore, so it must’ve been some setting that I was overlooking that made that happen.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.