We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

REEOrder Module (Custom ordering of entries)

Development and Programming

cityzen's avatar
cityzen
83 posts
15 years ago
cityzen's avatar cityzen

I’ve used this module/extension in the past and just run into an issue that I can’t recall whether it happened in the past or not. When I add a new entry it does not automatically get assigned a sort order # which causes a problem in my particular case. I have a weblog with limit of 3 entries showing, if I am sorting by my custom_sort_field, my newest entries do not get assigned a sort value by default and don’t end up showing up in my entries loop. Is this normal or something I should look into?

Thanks again for a great extension / module!

       
Cocoaholic's avatar
Cocoaholic
445 posts
15 years ago
Cocoaholic's avatar Cocoaholic

Hi cityzen,

This is expected behaviour. Entries need to be re-ordered to get a sort value.

       
cityzen's avatar
cityzen
83 posts
15 years ago
cityzen's avatar cityzen

Excellent, thanks for clarifying. It works great when I am listing all entries but the weird implementation I have now doesn’t work so well with that behavior. Thanks again for the prompt response.

Mike

       
Christopher Kennedy's avatar
Christopher Kennedy
44 posts
15 years ago
Christopher Kennedy's avatar Christopher Kennedy

Hey Cocoaholic,

I love the REEOrder module, it’s helped out with a lot of manual functions for clients. I’m wondering if there’s a possible bug or issue when using the XML function. I can’t imagine for the life of me why this is happening, but it’s only inside of an xml file.

My XML template uses this code:

<?xml version="1.0" encoding="UTF-8"?>

<content>
{exp:weblog:entries weblog="home_page_banner" limit="4" orderby="homepage_reeorder" dynamic="off"}<image path="{homebanner_image}"{if banner_url != ""} {banner_url}link="{address}" win="{if opens_in != ""}_blank{if:else}_self{/if}"{/banner_url}{/if} >
{/exp:weblog:entries}</content>

That outputs this:

<?xml version="1.0" encoding="UTF-8"?>

<content>
<image path="/images/banners/Sprint_Banner_2.jpg" link="http://www.sprintsave4cu.com/" win="_blank" >
<image path="/images/banners/Rewards_header_banner_3.jpg" link="https://www.uchooserewards.com/members/home.php?sid=40XXdKrlo40" win="_blank" >
<image path="/images/banners/HeaderBanner2-UltFreeCheck.jpg" link="http://198.171.234.140/index.php/banking/checking/" win="_self" >
<image path="/images/banners/HeaderBanner1-75thAnniversary.jpg" link="http://198.171.234.140/images/uploads/anniversary_calendar.pdf" win="_blank" >
</content>

That renders in the order in which the content was posted, and ignores the REEOrder custom fields entirely.

However, when I create a standard page using the exact same snippet of content like this:

{exp:weblog:entries weblog="home_page_banner" limit="4" orderby="homepage_reeorder" dynamic="off"}<image path="{homebanner_image}"{if banner_url != ""} {banner_url}link="{address}" win="{if opens_in != ""}_blank{if:else}_self{/if}"{/banner_url}{/if} >
{/exp:weblog:entries}

I end up getting this, which is the correct ordered rendering:

<image path="/images/banners/Sprint_Banner_2.jpg" link="http://www.sprintsave4cu.com/" win="_blank" >
<image path="/images/banners/HeaderBanner2-UltFreeCheck.jpg" link="http://198.171.234.140/index.php/banking/checking/" win="_self" >
<image path="/images/banners/HeaderBanner1-75thAnniversary.jpg" link="http://198.171.234.140/images/uploads/anniversary_calendar.pdf" win="_blank" >
<image path="/images/banners/Rewards_header_banner_3.jpg" link="https://www.uchooserewards.com/members/home.php?sid=40XXdKrlo40" win="_blank" >

If anyone has any suggestions or insight, I’d appreciate it. I’m going bonkers! :D

       
Ben Lilley's avatar
Ben Lilley
214 posts
15 years ago
Ben Lilley's avatar Ben Lilley

This is a great module so thanks for taking the time to make it. Just one quick question for you. Is it possible to update the post status within the module itself?

For example, I’m using the module to allow clients to order the features they have on their homepage, however I’d also like them to be change the status to stop displaying a certain entry at all for now? The module is so close (it’s already displaying the status) to this, so I’m wondering if you have any plans to implement this functionality?

Cheers

       
bjsteiger's avatar
bjsteiger
87 posts
15 years ago
bjsteiger's avatar bjsteiger

Do you know if this module is 2.0 compatible?

       
Interfacer's avatar
Interfacer
92 posts
15 years ago
Interfacer's avatar Interfacer

Thanks for the nice module

after installing and don’t see any order numbers in the drop down menu of the reeorder menu though - did I get something basic wrong?

I’am using categories in my weblog - could that be a reason?

using EE 1.6.8


don’t you hate that - just after I submitted it was starting to work - but still how about categories?

       
Ryan Faubion's avatar
Ryan Faubion
81 posts
15 years ago
Ryan Faubion's avatar Ryan Faubion
Do you know if this module is 2.0 compatible?

+1 for this question.

       
gamma911's avatar
gamma911
51 posts
15 years ago
gamma911's avatar gamma911

Using this module and it works great, however when a new entry is posted this entry isn’t automatically given the newest priority (1) and in the reeorder module the priority number is blank.

It sorts itself out once you give any entry a click or give the latest one a priority of 1. I have the module set to sort=asc ( so that 1 is at the top) and also in my entries tag.

Any ideas?

       
Emily Heath's avatar
Emily Heath
197 posts
15 years ago
Emily Heath's avatar Emily Heath

@gamma91 I think that is just the way it works. You have to set priority manually - until then it has none. However, I found that on the front-end this meant that items without a priority came up top of my list (which I didn’t want) so if that is what you want by default you may be in luck. This comment earlier in this thread might help http://ellislab.com/forums/viewthread/43903/P108/#611174

       
Low's avatar
Low
407 posts
15 years ago
Low's avatar Low

I’m happy to announce Low Reorder for EE 2.x is available now for a modest price.

For those of you who missed it, read this announcement about me taking over Cocoaholic’s add-ons.

       
russlipton's avatar
russlipton
305 posts
15 years ago
russlipton's avatar russlipton

I’m interested and looked over your description, which is clear. But I’m wondering whether you could add any ideas (use cases) on how this might be integrated (?) with other important addons when they come out - if it can be. For instance, Tags, Structure, Playa, your own Variables addon, etc.

For instance, could one approach the flexibility of Seeries Or do you consider that to be a different species of animal than REEOrder?

       
Oxygen Smith's avatar
Oxygen Smith
120 posts
15 years ago
Oxygen Smith's avatar Oxygen Smith

Hey Low,

Lovely work you’ve done on this. I was sort of expecting this result since I performed a data migration to a site where we’d like to use ReeOrder, but: we just imported 14000 entries into the weblog where I was using ReeOrder. When I click on the link to start re-ordering, not to my total surprise, I get an out of memory error:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 51 bytes) in /www/eh11822/public_html/vueee/modules/reeorder/mcp.reeorder.php on line 837

I’ve tried turning the module off and on again and re-setting up the preferences, but to no avail.

When Chocaholic first introduced this module, I got the impression that it was really designed for sites with a relatively small number of entries per weblog, so I’m not too disappointed. However, I’m still wondering if it’s possible to work around this out of memory error.

If not, I’ll have to find some other solution (although I have some ideas for how ReeOrder could for a weblog with a lot of records.

Cheers

R o B

       
Low's avatar
Low
407 posts
15 years ago
Low's avatar Low

You can always try and up the php memory limit in your .htaccess file:

php_value memory_limit 16M

You can up the 16M to even more if needed.

       
Oxygen Smith's avatar
Oxygen Smith
120 posts
15 years ago
Oxygen Smith's avatar Oxygen Smith

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.

       
First 8 9 10 11

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.