Bug #23572 Bug Fixed

Using the new “edit” feature on multiple entries generates an error

Version: 4.2.0 Reporter: Ottenhoff Consulting

Using the new “edit” feature on multiple entries generates an error:

404: Item does not exist Sorry, we could not find the item you are trying to access in the system.

URL: cp/publish/edit/entry&S=b996bee54e38e7d28daeecaba7353a40/48&entry_ids[]=48&entry_ids[]=47&modal_form=y

  • Sorry you’re having trouble with this new feature, can you provide steps to reproduce, and verify that you do not have any add-ons or browser extensions interfering?

    Derek Jones
    16th April, 2018 at 4:11pm
  • I simply selected 3 entries in the entry list in the CP, selected “edit” from the dropdown at the bottom of the list, and clicked “submit”.

    The only add-on is “Wygwam”.

    This is an “old” site that has been upgraded through the years from EE 2 through EE 3, then EE 4. (it’s a super basic site… just our internal marketing site. Nothing fancy.)

    No other errors that I’m seeing anywhere else.

    I tested on a new site in dev that was installed with EE 4.1. I just did the 4.2 update, and the mass edit is working on that one.. Same “Wygwam” add-on installed on it. So, it’s not the add-on.

    I had done the self update through the CP on both. So, to try and troubleshoot, I just downloaded EE 4.2 and replaced the system/ee and themes/ee directories in the problem site. Didn’t make a difference.

    Just to be thorough, I also replaced the Wygwam files.

    .htaccess files are the same on these two sites. They are hosted in the same (our own) hosting environment (as with 50 other EE installs)..

    When this error happens, the blue bar at the top of the browser that should show the entry title displays: %placeholder%

    I don’t get the “close modal” link on the error page.. So, that blue bar at the top never goes away. It now stays at the top of the CP as I click through different areas. If I change the URL to go back to the my CP login page, I’m logged out… Hmm.. I see the session ID being passed in the error message….

    ===== Ok. Figured it out. The site that was not working (the one upgraded from EE 2, EE 3, and to EE 4 over the years), had CP session type set to “Cookies and session ID”. The working site had it set to “Cookies only”.

    I changed the not-working one to “Cookies only” and the mass edit works now.

    Ottenhoff Consulting
    16th April, 2018 at 4:43pm
  • Thank you for the debug! Yes “Cookies and session ID” seems to be the ticket, we’ll have a fix for this in the next release.

    Kevin Cupp
    16th April, 2018 at 5:11pm
  • Great! Question on this.. The EE 4 docs say that for “CP session type” the “Cookies and session ID” option is the default, and the most secure.

    But, it seems that my latest EE projects (that start with EE 4, rather than upgrades) automatically selects “Cookies only” for the CP session type. Has that default behavior changed? And, should I be changing my EE 4 upgrade sites to Cookies only?


    Ottenhoff Consulting
    16th April, 2018 at 5:17pm
  • Ah yes we did change the default to Cookies Only but did not update the documentation, we’ll fix that. There’s no need to change to Cookies Only unless you want to, it’s the default now just because it allows for more convenient logging in, but Cookies & Session ID is still the most secure.

    Kevin Cupp
    16th April, 2018 at 5:57pm
  • Ok. great. Thanks!

    Ottenhoff Consulting
    16th April, 2018 at 6:11pm

You must be signed in to comment on a bug report.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases