Publish layout hidden field causing PHP error
Developer Preview
On a few publish layouts I have the comment expiration field hidden. I’m getting the following errors:
A PHP Error was encountered Severity: Notice Message: Undefined index: comment_expiration_date Filename: content/publish.php Line Number: 145 A PHP Error was encountered Severity: Notice Message: Undefined index: comment_expiration_date Filename: content/publish.php Line Number: 151 A PHP Error was encountered Severity: Notice Message: Undefined index: comment_expiration_date Filename: content/publish.php Line Number: 152 A PHP Error was encountered Severity: Notice Message: Undefined index: comment_expiration_date Filename: content/publish.php Line Number: 157 A PHP Error was encountered Severity: Notice Message: Undefined index: comment_expiration_date Filename: content/publish.php Line Number: 159 A PHP Error was encountered Severity: Notice Message: Undefined index: comment_expiration_date Filename: content/publish.php Line Number: 166 A PHP Error was encountered Severity: Notice Message: Undefined index: comment_expiration_date Filename: content/publish.php Line Number: 171
Thanks for all your testing today, Erik. I’m unable to reproduce this one. I tried on a 2.3.1 install, hid the comment expiration date field, then upgraded to 2.4 and all seemed normal. Also tried simply hiding it in 2.4 without the upgrade process. Is there anything else specific I can try to reproduce this? The serialized layout array must have gotten mucked up somehow.
Kevin
Strange indeed. I always hate reporting errors that aren’t cut and dry 😊
For what it’s worth, I went from 2.1.3 to 2.4. I’ll dig a bit more and see what I find. Worst case scenario I’ll just wipe the layout entry from the db for the sake of time.
I’m glad to at least hear the installer was able to go from 2.1.3 to 2.4 with no problems (I assume). Yes usually in these cases, we tell users to reset their layouts, there must be some strange edge case where that array gets messed up that we’ve been unable to come across on our own.
I’m glad to at least hear the installer was able to go from 2.1.3 to 2.4 with no problems (I assume).
Correct. No issues at all. 😊
FWIW I just had this issue on a site that we’ve moved from 1.6 up to 2.4 at different stages.