Strange exp:low_events:entries issue after EE upgrade to 5.1.3

I have just upgraded to EE 5.1.3 and an using Low Events 2.1.0

I have a strange problem with the exp:low_events:entries tags since the EE upgrade from 3.5.17.

I have a table that lists events. The calendar channel includes a low_events field, plus a number of additional fields. I’m finding since the upgrade that the low events field does not display if some of the other fields are present.

So in the code below, the ‘event_level’ field, which is a simple select field always displays, and the title always displays, but the event_date does not display, when the ‘district field’ is present. BUT, if I remove the ‘district’ field, which is just another select field, the date suddenly shows us. I put the district back, and the date doesn’t display anymore. This happened with many of the fields in this channel. The event_level doesn’t effect the issue, and another textarea field does not effect it, but most of the others do. This also effects the heading code below. What could be the cause of this?

{exp:low_events:entries channel="calendar" unit="custom" date_from="01/01/2019" date_to="12/31/2019" sort="asc" limit="400" dynamic="no"}
{if '{event_date:first unit="month"}' == 'y'}
<tr class="calendar-heading">
<th colspan="9"><a name="{event_date:start_date format="%F"}">{event_date:start_date format="%F"}</a></th>
</tr>
{/if}
<tr class="mid-small table-row">
<td>{event_level}</td>
<td>{event_date:start_date format='%M %j, %Y'}</td>
<td>{district}</td>
<td>{title}</td>
</tr>
{/exp:low_events:entries}


Thanks
Susan
1 person has
this problem
+1
Reply
  • Additional information. I created a new Low Events field, and entered a few dates in the same calendar channel. It is not causing the same problem. To simplify further, the first Low Events tags below does not display the date with the 'district' field included, and the 2nd one does. I also tried creating a new district field, but the results were the same. So I think the problem is with the Low Events field.

    With original Low Events field - Doesn't work

    {exp:low_events:entries channel="calendar" entry_id="14908"}
    <br>{event_level}<br>
    {event_date:start_date format='%M %j, %Y'}<br>
    {district}<br>
    {title}
    {/exp:low_events:entries}


    With new test Low Events field - Works

    {exp:low_events:entries channel="calendar" entry_id="14908"}
    <br>{event_level}<br>
    {event_date_test:start_date format='%M %j, %Y'}<br>
    {district}<br>
    {title}
    {/exp:low_events:entries}
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Low (Official Rep) February 23, 2019 18:50
    Cannot replicate this locally, so I'll need to take a look myself. Please send SuperAdmin and FTP login credentials to hi at gotolow dot com if you can.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • This turned out to be a problem during the EE upgrade. This is what I found out from EE support:

    The problem is the exp_member_data table.

    All of the member fields should look like m_field_idx - they should have a m prefix on them.

    There are some old leftover fields just named field_id that weren’t removed.

    What’s happening, when the member data is joined into the existing channel data, if there happens to be a channel field with the same id as one of those field_id_x member fields, the member field data is replacing it.

    What needs to happen is the removal of all of those old field names from exp_member_data.

    You’ll need to be careful, make sure and backup, then manually remove any field_id_x or field_ft_x column. Make sure you’re not losing any data and that each of those has a corresponding m_field_id_x and m_field_ft_x.

    The m prefixed fields should be the ‘correct’ ones, but be careful and make sure to keep a backup of that table.

    Once the data is normalized, you should be ok.

    This should have been fixed during the upgrade - and it looks like the m_ prefix fields do exist. So I’m not sure how the bad fields got left. But the solution is to get rid of them.


    I followed the suggestion provided, and it fixed the problem with the date.

    So it's not a Low Events issue, but thanks for taking a look at it.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited