Custom Fields in {exp:weblog:entries /}

Don’t I feel stupid. 😊

Found the answer!! Found the modifications in the extension that need to be made to the mod.weblog.php file. Applied those and it does just as it says on the tin!! 😊

Absolutely fantastic!! Thanks for the brilliant extension Mark!

Best wishes,

Mark

Mark, I had this extension working perfectly on my local development server (MAMP) then when I migrated the ee installation / db to my mediatemple server, I am getting some weird php errors on parsing of my template. Here are the php errors that show up on the page:

Notice: strtotime(): Called with empty time parameter in /home/httpd/vhosts/surinahart.com/httpdocs/system/extensions/ext.custom_fields_in_ee_tags.php on line 203

Notice: strtotime(): Called with empty time parameter in /home/httpd/vhosts/surinahart.com/httpdocs/system/extensions/ext.custom_fields_in_ee_tags.php on line 205

Here is the entries tag in my template:

{exp:weblog:entries weblog="listings" status="not closed" disable="trackbacks|member_data|pagination" rdf="off" openhouse-date=">" dynamic="off"}
            
            <div class="column span-9 append-1">
                <h2><a href="http://{title_permalink=" title="Details">{address}</a></h2>
                Listing Price: <strong>{listing-price}</strong>  –  Availability: <strong>{if availability=="Sold"}<span>Sold</span>{if:else}For Sale{/if}</strong>
                Open House Date: <strong>{openhouse-date format="%l, %M. %d %Y"}</strong>

                Open House Time: <strong>{openhouse-time}</strong>
                {listing-summary}
            </div>

            <div class="column span-5 last">
                <a href="http://{title_permalink=" title="Details">_                {related_entries id="listing-pic"}_                    {medium_url}_                {/related_entries}</a>
                <div class="column span-5">
                    <strong>{address}
{city}, {province}, <span>{postal-code}</span></strong>
                </div>
            </div>

            <hr >

            {if no_results}
            <h2>Sorry!</h2>
            There are currently no Open Houses to display.
            {/if}
            
            {/exp:weblog:entries}

It may have something to do with the version of MySQL? I am not sure, I just know that on my local dev server it was version 5, and on mediatemple it is running 3.23 or something like that. any ideas as to what could be causing this error? thanks in advance!

bump?

actually when I change my tag to this:

openhouse-date="/.+/"

instead of this, which is how I had it when it was working

openhouse-date=">"

it does not give me the errors… but does not work in limiting the entries, just shows no entries. any help greatly appreciated 😊

Ato, I have split this last reply and moved it to the extension’s thread, where it is more appropriate.

Thanks Derek. I am still having the question though, and I have been reading the whole thread, and noticing that some users are using segmentation as value:

merk="{segment_3}"

My concern is that in my case doesn’t work.. do you have any idea why?!

thanks!

@atiosis - It’s kind of a hack to get the dynamic filtering working properly. I’m working on a newer version of the extension that will take this into account, however until then it’s kind of on a user-by-user basis wether it works.

BTW, I like your extension a lot. It is very useful. .. regarding my issue of the dynamic filtering, what you meant is that it won’t work :-(? How can I hack it to make it work? :red:

Thanks!

this feature is now built into EE 1.6.1 with the search parameter

http://expressionengine.com/docs/modules/weblog/parameters.html#par_search

Well, the new feature in 1.6.1 is wonderful and similar, but it doesn’t allow for > and < comparisons.

I also like Mark’s formatting better, but either one is fine.

TTFN Travis

Travis is correct, there are some differences. We would encourage all who do not require numerical comparisons to use the native feature instead of the extension, which I think Mark would himself advocate. I believe there is a feature request already placed for numerical comparisons, as well. We would mainly encourage the use of the native feature because the extension unfortunately requires a hack, and secondarily because the native feature is able to be supported by the support staff. I should note that Mark’s feedback during the 1.6.1 beta was very helpful, and his work here and great attitude are to be commended. Other advantages of the native feature, some of which resulted directly from Mark’s (and our other beta testers) feedback:

• allows for word boundary searches (looking specifically for ‘cat’ as a word instead of finding ‘categories’ and ‘vocation’ for example)
• will not conflict with other tag parameters regardless of how your custom fields are named.
• supports search for (or excluding) empty fields
• syntax is consistent with other ExpressionEngine tag parameters

We would encourage all who do not require numerical comparisons to use the native feature instead of the extension, which I think Mark would himself advocate.

I couldn’t agree more Derek. Hopefully in a few revisions there won’t even be a need for this extension and the search: will support a few more operators. Until then, I’d say, as Derek did, use this extension when you absolutely have to have but for everything else go with the built in approach (if for no other reason than you have a support team behind you instead of just me).

@Sam123 - If you’re comfortable with PHP then you could go into the extension and place a `var_dump(‘test’);` at the top of the `modify_sql()` method. Then if you see test you know the extension is running. A few things to check: (1) are you sure sermon_speaker is the exact name of the custom field? (2) Have you tries any other fields? (3) Can you turn on template debugging, is the correct weblog:entries tag shown within the template debugger? (4) Can you turn on SQL debugging, does INNER JOIN appear anywhere within the SQL debugging?

I’ve also did everything I had - added to hooks, enabled, disabled, but it just not works and: INNER JOIN doesn not appear anywhere within the SQL debugging (extension works OK)

Just upgraded EE to the 1.6.1, inserted hooks, and everything works!

Thank you, Mark for your great work.