New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EE v7.2.10] Entry Manager Table Column Select Menu missing "Comments" option #3047
Comments
@PDXMan1 in EE 7.2.4 we added a check that if Comment module is globally turned off (in Content & Design system settings) then it does not display as a column The list of columns is being cached, so there's a chance it showed up initially until you performed some actions with the Entry Manager setup - however I wasn't able to replicate that |
Hm... perhaps the table columns are being cached also, and both should get cleared when an update is run? We had to add a column we didn't need to get the Comments column removed, and then remove the one we just added, but didn't need. |
I'm still seeing inconsistencies on this. EE 7.2.11 (fresh install starting with EE 7.2.9). Comment module is disabled. Some entry listing are showing the comment column and some are not. I've cleared all EE caches, and no change. Can't seem to control it. |
EE v6.x.x includes the Comments column menu option so that it may be deselected and removed as a column in the Entry Manager Table at /cp/publish/edit
That menu option is missing in EE v7.2.10 but the column for Comments still shows up. The menu opens over that column, so you can't see it in the screenshot, but it is under there.
If I add a new column to the table, the Comments column will go away, but it's not listed in the menu, so there's no way to add it back later if I change my mind.
It could be that EE is not listing Comments it in the menu because we have Comments off for all channels, but if that's the case, then the Comments column shouldn't have been displaying in the table either.
If this isn't a bug, it's very confusing behavior.
The text was updated successfully, but these errors were encountered: