When using the extension I get a big whopping 2.5 seconds jump in template processing time:
(0.090625) Calling Extension Class/Method: Custom_fields_in_ee_tags/modify_sql (2.605126) -> Data Returned
Is this normal for the extension? If so, I think it should come with a warning. If not, any ideas why it should be doing this?
And yet, when I disable the extension, I get this:
(0.072874) -> Method Called: entries (3.559487) -> Data Returned
Same template, same site.
I’m using version 2.1.7 on EE 1.5.2, and I can’t get it working.
Here’s the page: http://208.69.123.116/site/test
Here’s the code:
{exp:weblog:entries weblog="articles" article_type="=Hop" limit="35"}
<tr>
<td width="100" align="left" valign="top" class="text"><a href="http://{title_permalink=articles/item}">/{article_thumbnail_old}</a>
{article_type}</td>
<td align="left" valign="top" class="text">
<a href="http://{title_permalink=articles/item}">{title}</a>
<i>{article_subtitle}</i>
by {article_byline}
<div align="justify">{article_summary}</div></td>
</tr>
{/exp:weblog:entries}
As you can see, it should only show article_type = Hop, but instead, it’s showing all article types.
Ideas?
TTFN Travis
I’m about to give this a whirl on my 1.6 install. I’m using the repeet extension, and hoping the two can play nicely together.
I wish that the important info from this thread was contained in a WIki or a doc. I don’t look forward to flipping through 9 pages to make sure I have the right files and the right instructions.
Is the attachment in the first post of this thread the most current?
Got, thanks Mark.
Here’s what I’m dealing with. The filter I’m using is very simple, but I’m just not sure if I’m using it correctly with the repeet calendar code.
I have a field called event_type, and I want to list just one a certain group of events. Here’s the code:
{exp:repeet:parse date_header_interval="month"}
{repeet:date_header}%F %Y{/repeet:date_header}
{repeet:no_results}No events are scheduled at this time.{/repeet:date_header}
{exp:repeet:get_ids weblog="calendar" parse="inward" end="1 year"}
{exp:weblog:entries weblog="calendar" event_type="/Commodore Club Event/"} entry_id="{repeet:entry_ids}" dynamic="off" show_expired="no" show_future_entries="yes"}
{repeet:item}
{repeet:entry_date}{entry_date format="%Y-%m-%d %H:%i"}{/repeet:entry_date}
{repeet:expiration_date}{expiration_date format="%Y-%m-%d %H:%i"}{/repeet:expiration_date}
{repeet:interval}{repeat_interval}{/repeet:interval}
{repeet:include_dates}{include_dates}{/repeet:include_dates}
{repeet:exclude_dates}{exclude_dates}{/repeet:exclude_dates}
{repeet:display}
Sorry for posting ALL my repeet code, I just want to make sure I have the syntax in the correct place.
a few things,
event_type="Commodore Club Event"
let me know what happens when you remove those slashes.
Yep, I was working on just that. And, it’s sort of good news that it doesn’t work for me without repeet.
{exp:weblog:entries weblog="calendar" event_type="Commodore Club Event" show_future_entries="yes"}
It shows everything.
If that syntax should work, I’ll go back through everything.
Now for the mod.weblog.php hack, I only added what UltraBob indicated in his instructions here. I gathered that those were a replacement for what was in the extension file, but maybe that’s where I goofed.
Capt’n Morgan – the update instructions ultrabob posted should be nearly identical to those in the extension. is there any way you could PM me a txt file of your sql output? Go to Admin » Sys Pref » Output and Debugging and turn on SQL Debugging. Then at the bottom of the page where the custom field limiter should be working (without repeet) copy and paste the sql log into a text file.
thanks.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.