Thread

I’m running Expression Engine 2.2.1 build 20110705
For some reasons (which I cannot explain), I cannot edit entries in one channel. I can edit the entries fine in the other channels.

The channel was originally created on EE 1.x and migrated to 2.x. It has only 2 custom fields: urllink and urldescription, both text, formatting set to None.

I use the channel to highlight a few items, i.e. I have 7 entries, each entry has a link to one article (on the site or elsewhere) that I want to hilight in the homepage. I never create new entries, instead I always edit one of the existing 7, replacing the old links with something fresh.

It worked until I upgraded to 2.2.1 where it suddenly stopped working: when I edit the entry, I’m returned the edit form (not shown the page that demonstrates the entry was successfully edited), my changes are not saved but there is no error message. Typically when I’m returned to the edit page, it’s because an error is displayed but not here.

Help!

Hi, Benoît Marchal.

Are you logged in as a SuperAdmin when attempting this? If you modify one of the entries and put in test for both parts of the entry, does that work?

I am logged in as SuperAdmin.
If I put “test” in both it does not work.

What I have noticed is that if I edit through the Channel entries (by checking them and choosing “Edit Selected”) I only have access to the title and date but I can edit them (would not work from the regular editing page). Obviously that hardly helps as I need to edit the actual data (custom fields) as well…

That’s a clue right there. I suspect something went awry with the import. If you aren’t setting any custom fields, did you set up a custom field group for the channel? That’s the first thing I’d look at.

Just to make sure we’re on the same page: the multi-entry editor never shows the custom fields for any channel (at least it never shows them for me) so it’s not unusual that I can’t edit them in that screen. It’s the fact that it fails (without an error message) in the entry editor that bothers me.

To answer your question, yes the channel has field group. It also has the default status group and the category group.

I have run some more tests. I have another channel that uses the same custom field group… and it suffers from the same problem. Can’t edit it. So yes, something probably went wrong with that custom field group in the upgrade from 2.1.x to 2.2.1 but I have looked through the obvious parameters and there’s no obvious errors that I can see.

Oh and one more thing that I cannot understand.
I have turned on the debugging information and on the entry edit page, there are quite different if I edit another channel than if I edit this channel.

In the other channels, they display no POST data which I assume means that the data was inserted and then there was a redirection. With the channel that causes the problem, I see the POST data in the debug information… and it has been ignore (no UPDATE in the SQL queries).

I have the same problem in one of my channels after upgrading. Information I can add: In my setup, the field group of the affected channel is used for different channels, but editing works ok in the other channels using the same field group. And the channel affected is a very old one, I doubt I have touched it since upgrading from 1.x.

Benoît and chronistin,

After you submit a change and are returned to the edit screen, check each tab to make sure there are no error messages shown for any of the fields. It’s possible an error is occurring on one of the other tabs.

Thanks Brandon, with your tip, I found the error. For some reason, the entries of the channel are all being associated with a forum post id=0, which is invalid. Easy fix.

I hope it’s as easy for Benoît.

Glad that worked, chronistin, and I believe that’s a known bug that is being worked on.

Any luck, Benoît?

Some story here. The forum post id was at zero (no idea why and since I did not changed, I guess it was OK before).

Suggestion: put a message on the first screen (or using the message area in the top bar) that says “error on one field, check all the fields in all the tabs” or better yet, point to the faulty tab… The current behavior is not friendly at all.

—ben

Hi Ben,

Agreed, and this is a confirmed bug. Thanks for your patience while we get it sorted!