All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

Adding LE to existing channel field group returns no entries

soire 24 Jul 2012 17:24 problem, complete

Hi Low

Thanks for your recent pre-sales help. Just bought LE and am loving its potential so far! I have a bunch of existing entries that I'd like to add this field type to and adjust the start/day/time and corresponding end settings. This works fine for displaying new entries that I create, but when I attempt to display my entries via the exp:low_events:entries tag, I only get new entries that I create...not existing entries that have had the LE field type added and set to a value. As a note, all of these entries are in one channel, if that matters at all.

Any suggestions? Thanks!

Replies

  1. soire 24 Jul 2012 17:35

    Oh yeah...EE 2.5.1 and LE 1.0.2 if that helps at all...

  2. Low 24 Jul 2012 19:17

    When you add the LE field to an existing channel, no actual events are created until you save each entry. That's why you only see the new ones. You'd probably need to initiate or import the existing events, for which you'd need some sort of import script, I suppose. What are you basing existing entries on?

  3. soire 24 Jul 2012 20:14

    My existing entries are based on an event system that I derived based on EE channel entries limited by the start_on="{current_time format='%Y-%m-%d %H:%i'}" parameter. This channel has the following fields

    title
    playa
    custom textfield (x2)
    custom textarea
    channel videos
    low events

    Does that help?

  4. Low 24 Jul 2012 20:33

    So, the entry_date was the event start date, then?

    You'd still need a migration script to port the existing entries, if you can't do it manually.

  5. soire 25 Jul 2012 04:09

    Here is how my channel entries tag looked with my "events" system

    {exp:channel:entries
    channel="events"
    disable="categories|category_fields|member_data|pagination"
    orderby="date"
    sort="asc"
    start_on="{current_time format='%Y-%m-%d %H:%i'}"
    show_future_entries="yes"
    }
    {custom_fields}
    {/exp:channel:entries }

    does that answer your question? I wouldn't really know where to begin with a migration script. Would you have any suggestions on that? Thank you for your help!

  6. Low 25 Jul 2012 06:40

    Can you confirm you used the entry_date as the event start date and the expiration_date as the event end date? I'll see if I can create a migration script for you.

  7. soire 25 Jul 2012 14:33

    I used the entry_date as the start date, but did not use the expiration date for anything. I used the start_on="{current_time format='%Y-%m-%d %H:%i'}" parameter to limit what was shown. Each entry was set to 11:59 PM so that (in theory) they would show until just before midnight and then be pulled off. That was the element that did not work because EE's time and member times differed from the actual server time.

    If it is too much trouble, I can just recreate the entries...

  8. Low 25 Jul 2012 14:45

    It's worth it when you've got, say, 100+ entries to deal with. If it's just a couple of dozen, recreating them is quicker.

  9. soire 25 Jul 2012 14:47

    There was probably 75 entries...I've already begun recreating them to expedite the process. Everything is working smoothly with the new entries.

    Thanks for your great support!

  10. soire 25 Jul 2012 16:08

    One other question please! Here is my LE entries tag...what can I add to exclude events that have passed? For an example, if I have two events in a day...one from 11am to 2pm, then another starting at 7pm. I'd like the first to be automatically removed from the list at 2pm when it is finished, then the first entry in the list would be next event, starting at 7. Does this make sense?

    {exp:low_events:entries
    channel="events"
    status="Recurring"
    unit="upcoming"
    }


    {if no_results}

    No Results

    {/if}

    {event_dates:start_date format="%F %j, %Y"} - {title} {event_cost} - {event_dates:start_time format="%g:%i %A"}



    {/exp:low_events:entries}

  11. Low 25 Jul 2012 16:19

    The next version will allow for show_passed="no" to omit passed events on the day itself, and is due next week. For now, you can hide them by using the {event_dates:passed} variable as a conditional.