My advice is to start with the base example code from the plugin and make sure your functionality is working from there. For example, I see you added show_future_entries and limit to that weblog tag, but I believe repeet sets the limit within the repeet:list_dates tag.
It’s important to make sure that base is working before you customize or there are too many variables. Just start a new set of templates and work from there.
GOOD NEWS! It was not a issue with the date or anything tried:) It was the pi.repeet.php file itself. What you were constantly having me do was rethink and relook, so thanks!:)
Here is what I found in another post (Click Here) post#8, the update to his plugin. To pi.repeet.php
{exp:weblog:entries weblog="events" show_future_entries="yes"}
{title}
{body}
{exp:repeet:list_dates from="today" to="1 year" entry_date="{entry_date format="%Y-%m-%d %H:%i"}" expiration_date="{expiration_date format="%Y-%m-%d %H:%i"}" max_list="25" interval="none"}
This event occurs on the following dates over the next year:
{repeet:include_dates}{festivals-repeat-dates}{/repeet:include_dates}
{repeet:exclude_dates}{exclude_dates}{/repeet:exclude_dates}
{repeet:display}
<li>
{repeet:start_time format="%l, %F %d, %Y %g:%i %A"}{repeet:end_time format=" - %g:%i %A"}
</li>
{/repeet:display}
{/exp:repeet:list_dates}
{/exp:weblog:entries}
Thanks again for hanging in there with me:):):)
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.