Thread

Hi, I have a problem with one of my weblogs. Every time I create the entry, the entry and entry list for the weblog shows up fine on the two respective web pages. When I go into the CP to edit the entry’s custom status, the entry doesn’t display on the web page after updating.

It also seems to happen sporadically. Some entrys don’t have any issue at all, where others, on the first edit of the entry, stop displaying on the page.

Any ideas?

Make sure you have a Status Group assigned to the Weblog in question. That should fix the problem.

The custom status group is assigned.
I also have in the entry tag the parameter to accept all versions of the status as well. See below:

{exp:weblog:entries  weblog="ticket_tracker"  status="new|pending|open|resolved|closed" orderby="date"   }

It also doesn’t really make sense how this one entry I have has no effect whatsoever. where all new entries are having an issue. i’m really boggled.

If it helps, here is my whole entry code…

{exp:weblog:entries  weblog="ticket_tracker"  status="new|pending|open|resolved|closed" orderby="date"   }
    <div class="title">{title}</div>
    <div class="ticket_body">
        
        <div class="ticket_info">
            {if status == "New"}
            <div class="status_new"><div class="status_inside">Status:
<span class="status_style">{status}</span></div></div>
            {if:elseif status == "open" }
            <div class="status_open"><div class="status_inside">Status:
<span class="status_style">{status}</span></div></div>
            {if:elseif status == "Resolved" }
            <div class="status_resolved"><div class="status_inside">Status:
<span class="status_style">{status}</span></div></div>
            {if:elseif status == "closed" }
            <div class="status_closed"><div class="status_inside">Status:
<span class="status_style">{status}</span></div></div>
            {if:else}
            <div class="status_open"><div class="status_inside">Status:
<span class="status_style">{status}</span></div></div>
            {/if}
            <div class="id"><div class="inside">ID:
 {entry_id}</div> </div>
            {if priority == "1"}
            <div class="priority"><div class="inside">Priority:
<span class="critical">Critical</span></div></div>
            {if:elseif priority == "2"}
            <div class="priority"><div class="inside">Priority:
<span class="important">Important</div></div>
            {if:elseif priority == "3"}
            <div class="priority"><div class="inside">Priority:
<span class="normal">Normal</div></div>
            {if:elseif priority == "4"}
            <div class="priority"><div class="inside">Priority:
<span class="low">Low</div></div>
            {if:elseif priority == "5"}
            <div class="priority"><div class="inside">Priority:
<span class="no_rush">No Rush</div></div>
            {if:else}
            <div class="priority"><div class="inside">Priority:
<span class="normal">Normal</div></div>
            {/if}
            <div class="category"><div class="inside">Category:
 {category:label}</div></div>
            <div class="type"><div class="inside">Type:
 {type}</div></div>
            
        </div>
        <div class="ticket_author">
            Created by {author} on {entry_date format="%F %d, %Y"} | Assigned to SilmarIT Staff
Customer Number:  {customer_number}
        </div>
        <div class="ticket_description">
            {ticket_description}
 <a href="/system/index.php?C=edit&M=edit_entry&weblog_id=" rel="noopener editdemo" title="Edit Entry" target="_blank">Edit Ticket Information</a>
        </div>
    </div>
            
    
    
    {/exp:weblog:entries }

What does the status of the entry change to, after you edit it the first time?

Also be sure to check the entry time. You can try to add

show_future_entries="yes"

to your EE tag, see if that changes anything.

I change the status from ‘new’ to either ‘open, resolved, pending, or closed’. it normally creates the entry with a status of ‘new’, in which the entry shows up fine after creation.

@Ingmar, I’ll try the future entries parameter now.

@Ingmar, Thank you! It looks like that future entries parameter did the trick on both the list and the entry itself.

Can you explain why it might be pushing it to think it is a future entry?

Carefully check the entry_date, it’s probably moved ahead by an hour or so. It’s a DST related bug, I think.

Hate to jump in here, but I’m testing my first EE2 site, and while I’ve seen the date bugs in EE1, never like what I’m seeing now.

The reason you need to “show_future_entries” is because the date is leaping forward by timezone offsets.

When I first noticed the issue, I set the date (more specifically, the TIME) back to the current time, resaved the entry and attempted, again, to view the rendered page.

It was missing again.

Edit.
Check Entry Date.
Reset time.
Rinse.
Repeat.

Finally I set the date back to YESTERDAY, rather than simply setting the time back to “a few minutes ago.”

EE, not to be outdone, leaped the date about 5 hours ahead of the time I recently edited the entry date, meaning an entire day + several hours.

What the heck?

SO…

I noted that the offset in time was the same as my Timezone offset from UTC: -5:00
I also note that my server timezone is the same as my local timezone: UTC -5:00
And, for good measure, I check to make sure that my User Control Panel localization is set correctly. It is. UTC -5:00

So I entered “300” in the “Server Offset (in minutes)”, figuring that, heck, at least it’s 5 hours like everything else.

Why it works I do not know. I’m almost upset that it *does* work, because it’s so completely non-intuitive.
But at this point in this nightmare of a client project (WHY did I decide that I would stick with EE2 on this one? WHY?) I’m just happy when it works.

But something seems to need rejiggering under the hood. If the server is in my timezone, and *I* am in my timezone, and my computer’s timezone is set properly, and my Control panel’s timezone is set properly, and my DST settings are set properly…

WHY do I need to offset my server time by 5 hours?

(That’s a rhetorical. I know you don’t have the answer.)

Glad it works.

WHY do I need to offset my server time by 5 hours?

It looks like this bug report applies to your setup as well.