Ordering oddity- selected items??

Ok, I think I know what’s going on with the current situation. SelectedItems is re-ordering these after the switch code is written. So, basically, I don’t think you can use switch with that module.

BUT, it still doesn’t explain the first bit about why, when I was using display_order field to order them, the 100 was showing up behind 200-700.

Ideas?

To use the switch statement with the SelectedItems extension, you can replace it with {selecteditems_switch="blank|clear"}.

Sweet! That worked. Don’t know why I didn’t see this option before. RTFM, right?

Thanks for the pointer, Andrew. jtnt, not sure why the order was goofing with 100- it makes no sense. To debug, I’d probably start by running some queries- see what they return. That would help us narrow down the issue. Not sure you’re up for that, but if you are, say the word and we can start hitting it.

I have two usages of Selected Items extension on the same page and one works, but the other one does not. It seems to list entries in the order of the edit tab in back end.

Here is the code (not working) (this page is embedded in a full-page):

<table id="featured" cellspacing="0" cellpadding="0" border="0" width="100%">
    <tr>
        <td align="center" valign="top">
            {exp:selecteditems name="paintings_display_order"}
            {exp:weblog:entries weblog="paintings_weblog" entry_id="{selecteditems_id}" orderby="selecteditems" limit="1" status="open"}
                <div class="featured-painting">{painting-img}</div>
                

                {entry_id}

                {selecteditems_id}
                <div class="featured_stats"><strong>{title}</strong>
                    


                    {painting-medium}  {painting-width} X {painting-height}  {painting-year}
                    


                    {painting-status} {painting-holder}</div>
            {/exp:weblog:entries}
            {/exp:selecteditems}
        </td>
        <td align="center" valign="top" width="200">
            {embed="site/thumbs"} <<<<<-- THIS IS THE PAGE BELOW >>>>
        </td>
    </tr>
</table>

And here is the site/thumbs embedded page within this one highlighted above. The selected items extension ordering here works, but not above! Go figure…scratching my head.

<div id="paintingthumbs">
    {exp:selecteditems name="paintings_display_order"}
    {exp:weblog:entries weblog="paintings_weblog" entry_id="{selecteditems_id}" orderby="selecteditems" dynamic="off" status="open" disable="trackbacks|member_data|pagination"}
        <div class="thethumbs">
        <a href="http://{url_title_path=site/paintings}#{url_title}">{painting-thumb}</a>
        </div>
    {/exp:weblog:entries}
    {/exp:selecteditems}
</div>

Does anyone know if it’s possible to use the selecteditems module twice on one page??

I found why it was not working. Apparently I am not able to use the limit=”” parameter with selected items. When I take it out, it lists the entries in the correct order. When I add, with limit=1, =2 or =20 it does not order correctly (or seems to default to the order in the back end (date).

Anyone else have this problem? I really need some way of ordering entries. I’ve tried reeorder and it’s great, but not going to work for what I need.

I don’t know the selected items plugin/module or what it does- but looks like that’s where the issue comes into play. Might be a better question for the author- or I can move this down to the plugin/module forum?

Thanks Robin,

Move anywhere you feel appropriate. I went back to creating a custom field and type in a number manually, then use that in the templates to custom order.

Thanks, Joel.

I think I’ll shift it to modules and tweak the title- I suspect someone who is up on that module might have an idea of what’s up.

Hi Joel,

Due to the way that the SelectedItems module works, you cannot use the limit parameter.

You might be able to limit the entries that show using something like:

{if selecteditems_count < 5} … {/if}

If you try this and it does not work let me know. There was a bug (that has been fixed), but I’m not sure whether it was in the last ‘release’.

Andrew

Hi Andrew,

Thanks. For now I’m just resorting to using a custom field. This seems to work, though as mentioned too many times on these forums, it’s not the best way.

Thanks for your help all the same.

Joel.