Hi Mark,

It now works with hyphens in the custom field name, but doesn’t display anything if I limit the results.  Is this beyond the scope of the extension?

cheers, Jamie

That’s great it’s working with the hyphen, however it should work with the limit also.  I will investigate.

Limit will not work based on the core functionality of EE.  So I am planning on including my own limit field, something like ext_limit=“10” but for now I would (if you have the processing power) leave out the limit and put a conditional check in at the beginning to check the count: {if count < 10}{/if}

Thanks Mark, I look forward to it.

Just as an aside, I don’t think using the {count} variable is going to work in the short term either for me.  I have 12 entries, 2 of which have the custom field ‘casestudy-featured’ set to Yes.

When I run…

...the 2 entry’s count variables output as 7 and 10, not 1 and 2 as you’d expect.

I’m gonna go back to using {if casestudy-featured} for now.  thanks for your help so far though

Thanks for helping me debug a little further.

I’ve updated the extension again and instead of using limit=“10” you can use max=“10” and that should give you the entries you’re expecting.  The only thing to be careful of is to make sure max=“10” comes before any of your custom field declarations.

I’m sorry Mark.  Using…

...lists all the entries.

try the max=“1” behind the custom field call, it should always be at the end, not the beginning.  my mistake.

sorry should have said.  tried that…

...and it displays all the entries with casestudy-featured set to Yes.  So almost like it simply ignores the max parameter.

Alright, sorry this has taken so long.  I had all but given up hope for this extension, but here it is again.  Another release that should fix the max problem.  Download it again from the first post in this thread.

Mark, something not quite right going on

There are 10 entries, 3 are set to Yes on ‘casestudy-featured’. (I’m not sure if those numbers actually relate to the problem or not).

I just want to display one entry that has been set to yes.

That displays nothing.  Change the max value to anything up to 4 and still nothing displays.

Change it to 5 and 1 entry displays.  Change it to 6 and 2 display, 7 and 3 display.  Anything above 7 and 3 display (the maximum number of entries set to Yes).

Hope that helps.

I’m trying it too. The max is working for me, but pagination isn’t.

Or is it supposed to?

I haven’t looked into pagnation.  I’ll take a peak now though.

Alright, I took the extension to fat camp and came up with a much leaner, faster, more optimized extension.  The only condition is that you have to modify your ‘mod.weblog.php’ file to allow the extension hook.  You can find instructions for that in the top of the .php file.  Other than that pagination, limits, and any other {exp:weblog:entries /} should work now.  Grab the EXT at the top of the thread.

Seems to work like a charm. Thank you very much.

Would it be difficult to apply this also to exp:weblog:prev_entry and exp:weblog:next_entry?

hum, as a workaround for now you might want to try replacing exp:weblog:prev_entry and exp:weblog:next_entry with normal exp:weblog:entries tags switching the sort and limiting by 1?  I’m not sure just how well that will work, but it’s alternative.

I can’t seem to make this limit at all. I’ve tried a few different combos but it just outputs every entry in the weblog. Am I doing anything noticably wrong below?

I assume if I have an input field or drop down field (one or the other) that has “one” in it, that all those entries will show up but those without that text will not. I would use this right now if it worked for me.

Any help is appreciated. Thanks!

You’ll want to make sure you update your weblog files as described here: http://expressionengine.com/forums/viewthread/38371/P18/#187855 and in the top of the extension.  Have you done that?