Template routes disappearing when (re-)saving a template (EE 3.0.4)

I couldn’t replicate the routing one on 3.0.4- so weird! Keep an eye on it, as you may have done something specific to trigger it on 3.0.4, given I can’t.

As for the PHP errors on the publish page- we have some bug fixes in for a future release related to saving layouts and I suspect the problem came in when you saved the layout or added new fields and will be moot in 3.1.

How did you get rid of the errors- did just resaving the layout do the trick?

Now- I did replicate the comment issue. Looks like it’s fixed for 3.1, though. But if it’s jamming you up, let me know and I’ll see if I can pull out a patch.

> How did you get rid of the errors- did just resaving the layout do the trick?

Deleted the layout and made a new one. It seems that editing the layout did something… btw: Layouts could really use a 2-column option. 😉

> But if it’s jamming you up, let me know and I’ll see if I can pull out a patch.

Nah, don’t worry. As long as it’s working, I don’t care.

Something else: Maybe I’m just too stupid, but I can NOT get commenting for Super Admins to work.

I’ve got an entry with a comment form. Tested with member-account (logged in @ backend - opened the frontend), works. Tested as guest without logging in, works. Logged in with my Super-Admin, went to the frontend -> “You are not allowed to post comments”

Did I miss something? AFAIK a Super Admin should be allowed to comment everywhere? And it seems there is nothing i can config at the member options?

I think all of the layout issues should be fixed in 3.1, so we should be good there.

And I ran into that commenting bug as well- reported it in the tracker. Pedro doesn’t replicate, but something about how/when we installed must be in play.

The short term fix- go to the database, edit the exp_member_groups table, make sure can_post_comments is set to y for the superadmin group.

That fix it for you? It did for me.

> I think all of the layout issues should be fixed in 3.1, so we should be good there.

Good to hear. Having nice entry forms was always appreciated by the users.

> That fix it for you? It did for me.

Yes, it did. Thx for the hint.

Edit: Deleting Entries with comments seems to cause PHP errors. See attached screenshot. Tried to delete dummy entries with comments. Deleting worked, but threw errors.

Also (hope I’m not spamming here…), setting datetime to 24-hour dd/mm/yyyy seems not to have any effect on the entry date when creating an entry.

Keep ‘em coming- we don’t want Seth to run out of things to do 😉

I confirm the issue with comments and put in a new bug report. Tried it on 3.1 and it still had the problem, so it’s not fixed yet. Let me know if it’s mission critical, otherwise I’d subscribe to that bug and we should post back when we have a patch.

And I shall poke the date issue next!

Also: It seems I can’t get the statistics working properly with the channel-parameter.

{exp:stats}
   {total_entries}
{/exp:stats}

Gives a total of 28, which is correct.

{exp:stats channel="news"}
   {total_entries}
{/exp:stats}

however returns “0” … which isn’t correct. The {total_comments} however return the correct value. Also the {last_entry_date} does not work with the channel-filter.

I’ve never used the statistics before, maybe I’m doing something wrong. I wanted to get the total_entries for a specific channel, so i can ‘Stash’ it and use it sitewide.

Next one:

Backend, Edit View: When changing the show-parameter [ show (25), show (50) … ] the dropdown/submit-section that shows whenever the checkbox next to an entry is selected … doesn’t show. When you change the show-parameter again (even if you select the same one again) it works again.

Same seems to be true for all the other filters i just found out.

Seems it stops working every 2nd time a filter until another change happens.

It seems the Rich Text Editor does not save when they are enclosed by an H-Tag.

BLA
BLA works.

<h6> blabla 
 blabla </h6> does not save the 
.