REEOrder Module (Custom ordering of entries)
Development and Programming
Thanks Low. I checked, but memory_limit’s sitting at 64M right now. Also, I’m not even sure if the hosts (EngineHosting, who we really want to use!) let you up your memory.
Heh, well I guess 14.000 entries in one go is a bit much anyway. You might want to rethink the strategy; do you really need custom ordering with that amount of entries? Isn’t it more useful to create more structure first, for example by categorizing the entries?
I think the whole point of REEorder is having all relevant entries in a list to reorder. A list of 14.000 entries wouldn’t be manageable, even if the memory limit wasn’t an issue.
Heh, well I guess 14.000 entries in one go is a bit much anyway. You might want to rethink the strategy; do you really need custom ordering with that amount of entries? Isn’t it more useful to create more structure first, for example by categorizing the entries?
Yes, that’s exactly it. The plan has never been to number them all from 0-15000, though. I just really like your drag and drop interface as opposed to the usual strategy I give to clients, which is to multi-edit the entries they want to re-order, then change part of their entry_date timestamp, to get them in a different sequence.
What I was hoping that, in the near future, Reeorder might let you filter and order ‘groups of entries’ to reorder, much like you use the edit screen to filter down entires through category, status, etc. I think that someone in the discussion on your site had a similar idea. I see that updates have ceased on the 1.6x version, though… totally understandable.
Cheers,
R o B
Using the pagination sql query code flying around, I’ve got it working, but instead of Next and Previous, I’d prefer to show the title of the item. Anyone care to provide the SQL knowledge on getting access to this.
Here’s the code as it stands:
PREV
{exp:query sql="SELECT url_title AS ut FROM exp_weblog_titles ewt INNER JOIN exp_weblog_data ewd ON ewd.entry_id = ewt.entry_id WHERE ewd.field_id_29 < {reeorder_index} AND ewd.weblog_id = {weblog_id} AND STATUS = 'open' ORDER BY field_id_29 DESC LIMIT 1"}
<a href="/index.php/exampletemplate/{ut}/">{entry_title}</a>
{/exp:query}
NEXT
{exp:query sql="SELECT url_title AS ut FROM exp_weblog_titles ewt INNER JOIN exp_weblog_data ewd ON ewd.entry_id = ewt.entry_id WHERE ewd.field_id_29 > {reeorder_index} AND ewd.weblog_id = {weblog_id} AND STATUS = 'open' ORDER BY field_id_29 ASC LIMIT 1"}
<a href="/index.php/exampletemplate/{ut}/">{entry_title}</a>
{/exp:query}A plus would be some way of working out whether there’s is both a next and previous returned, but I’d be happy to just get a title.
Cheers Brendan
OK, managed to get a mate of mine to help me out with the SQL used to fo pagination (paging) with Reeorder including restriction to specific category id. You’ll notice that I’m also checking to make sure that the items returned are a part of a specific category as the weblogs in my case are shared across multiple categories. I’m using LowSeg2Cat to hack the URL in my case to get nice SEO friendly URLs.
Should be relatively easy to modify to your needs.
{exp:weblog:entries weblog="{segment_2}" url_title="{segment_3}" dynamic="off" disable="member_data|trackbacks|pagination|categories|category_fields"}
{if reeorder_index}
<div id="productpaging">
{exp:query sql="SELECT title AS item_title, url_title AS item_url FROM exp_weblog_titles ewt INNER JOIN exp_weblog_data ewd ON ewd.entry_id = ewt.entry_id INNER JOIN exp_category_posts ecp ON ecp.entry_id = ewt.entry_id WHERE ewd.field_id_29 > {reeorder_index} AND ewd.weblog_id = {weblog_id} AND STATUS = 'open' AND ecp.cat_id = {segment_1_category_id} ORDER BY field_id_29 ASC LIMIT 1"}
<a href="http://{site_url}{segment_1}/{segment_2}/{item_url}/" class="page-prev">{item_title}</a>
{/exp:query}
<!-- show separator only if both next and previous are present -->
{exp:query sql="SELECT count(*) AS prev_count FROM exp_weblog_titles ewt INNER JOIN exp_weblog_data ewd ON ewd.entry_id = ewt.entry_id INNER JOIN exp_category_posts ecp ON ecp.entry_id = ewt.entry_id WHERE ewd.weblog_id = {weblog_id} AND STATUS = 'open' AND ecp.cat_id = {segment_1_category_id} AND (ewd.field_id_29 < {reeorder_index})"}
{exp:query sql="SELECT count(*) AS next_count FROM exp_weblog_titles ewt INNER JOIN exp_weblog_data ewd ON ewd.entry_id = ewt.entry_id INNER JOIN exp_category_posts ecp ON ecp.entry_id = ewt.entry_id WHERE ewd.weblog_id = {weblog_id} AND STATUS = 'open' AND ecp.cat_id = {segment_1_category_id} AND (ewd.field_id_29 > {reeorder_index})"}{if {prev_count} > 0 AND {next_count} > 0} | {/if}{/exp:query}{/exp:query}
{exp:query sql="SELECT title AS item_title, url_title AS item_url FROM exp_weblog_titles ewt INNER JOIN exp_weblog_data ewd ON ewd.entry_id = ewt.entry_id INNER JOIN exp_category_posts ecp ON ecp.entry_id = ewt.entry_id WHERE ewd.field_id_29 < {reeorder_index} AND ewd.weblog_id = {weblog_id} AND STATUS = 'open' AND ecp.cat_id = {segment_1_category_id} ORDER BY field_id_29 DESC LIMIT 1"}
<a href="http://{site_url}{segment_1}/{segment_2}/{item_url}/" class="page-next">{item_title}</a>
{/exp:query}
</div>
{/if}
{/exp:weblog:entries}You can see this in action on the following page/s: http://www.stormwatches.com.au/mens/watches/noxer/
Cheers Brendan
The module itself works great but im getting an error with the hide in control panel extensions:
document.getElementById("field_pane_off_0") is null
[Break on this error] document.getElementById('field_pane_off_0')[removed].style.display='none';Iv disabled it at the moment and also not shown as default but i guess in an ideal world id like to get it working. If anyone has ideas ideas it would be appreciated.
Thanks.
Howdy….is this Reeorder plugin still functional and supported?
https://devot-ee.com/add-ons/reeorder
It sounds like the exact thing I need but am wondering if it is dead at this point. I’m going to try it and see, but is anyone out there? 😊
Jason
Howdy….is this Reeorder plugin still functional and supported? https://devot-ee.com/add-ons/reeorder It sounds like the exact thing I need but am wondering if it is dead at this point. I’m going to try it and see, but is anyone out there? :-) Jason
It isn’t, but Low made a great replacement, long ago: Low Reorder