Error upon saving K2 items in specific Category - Data too long for column 'xxxx' at row 1

[UIIBA]

Has anyone else been having an issue with saving K2 items possibly related to the amount of extra fields in that item's specified category? My site has three separate categories to organize the items we have. when I try to save or create any item in category id:1, I get an error: "500 Data too long for column 'title' at row 1" or sometimes it says "alias". I've narrowed the problem down to the two 'textarea' extra fields that are in this extra fields group to be what is causing the issue. when I delete these two extra fields, this error no longer shows up. Is there a possible fix for this issue? I need the two 'textarea' fields in this item's category. luckily, this error does not prevent us from adding or making changes to items, but it does make the process of doing so take much longer as we get redirected to the dashboard and then have to click back to the item we were working on. some rows' extra_fields have a length of over 9,000, but I don't see how that might be a reason for the issue as these columns are of type: TEXT and can hold up to 65,535 characters. I have tried changing the column type to "LONGTEXT" as a similar issue on stack overflow suggested, but that did not work. any suggestions or knowledge will help. Thanks

[krmrtrzv]

I had similar issues on 3 websites. Always thought it is related to titles and aliases, and made severe efforts shortening the titles and aliases, but it did not solve the error message. It happened only on select number of items and is very annoying

On Mon, 8 Jul 2024 at 19:13, Andrew Schmidt @.***> wrote:

Has anyone else been having an issue with saving K2 items possibly related to the amount of extra fields in that item's specified category? My site has three separate categories to organize the items we have. when I try to save or create any item in category id:1, I get an error: "500 Data too long for column 'title' at row 1" or sometimes it says "alias". I've narrowed the problem down to the two 'textarea' extra fields that are in this extra fields group to be what is causing the issue. when I delete these two extra fields, this error no longer shows up. Is there a possible fix for this issue? I need the two 'textarea' fields in this item's category. luckily, this error does not prevent us from adding or making changes to items, but it does make the process of doing so take much longer as we get redirected to the dashboard and then have to click back to the item we were working on. some rows' extra_fields have a length of over 9,000, but I don't see how that might be a reason for the issue as these columns are of type: TEXT and can hold up to 65,535 characters. I have tried changing the column type to "LONGTEXT" as a similar issue on stack overflow suggested, but that did not work. any suggestions or knowledge will help. Thanks

— Reply to this email directly, view it on GitHub https://github.com/eworkers/K2ForJ4/issues/89, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEE5GULVAELNNHWK6NLBVDLZLK3CRAVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TMMBUGAZTEOI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[UIIBA]

I had similar issues on 3 websites. Always thought it is related to titles and aliases, and made severe efforts shortening the titles and aliases, but it did not solve the error message. It happened only on select number of items and is very annoying … On Mon, 8 Jul 2024 at 19:13, Andrew Schmidt @.> wrote: Has anyone else been having an issue with saving K2 items possibly related to the amount of extra fields in that item's specified category? My site has three separate categories to organize the items we have. when I try to save or create any item in category id:1, I get an error: "500 Data too long for column 'title' at row 1" or sometimes it says "alias". I've narrowed the problem down to the two 'textarea' extra fields that are in this extra fields group to be what is causing the issue. when I delete these two extra fields, this error no longer shows up. Is there a possible fix for this issue? I need the two 'textarea' fields in this item's category. luckily, this error does not prevent us from adding or making changes to items, but it does make the process of doing so take much longer as we get redirected to the dashboard and then have to click back to the item we were working on. some rows' extra_fields have a length of over 9,000, but I don't see how that might be a reason for the issue as these columns are of type: TEXT and can hold up to 65,535 characters. I have tried changing the column type to "LONGTEXT" as a similar issue on stack overflow suggested, but that did not work. any suggestions or knowledge will help. Thanks — Reply to this email directly, view it on GitHub <#89>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEE5GULVAELNNHWK6NLBVDLZLK3CRAVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TMMBUGAZTEOI . You are receiving this because you are subscribed to this thread.Message ID: @.>

Were your issues ever tied to the same category or a category using specific extra fields? I'm surprised that not more people have mentioned this issue if you've had this on 3 websites. I have this problem on all branches of this website.

[krmrtrzv]

Yes the issue was related to only one specific category and I did not even associated it with the extra fields since the error was explicitly blaming the ‘alias’ and I had not associated the extra fields also have alias. Always thought it is about title alias. Only after your post I figured it out but it makes no sense. My extra fields alias are always short and handy for I call them individually by alias in my subtemplates as it was suggested by JW. Only god knows how deep K2 workings are within J. That is why I asked @eworkers to clear the future for the fork in order to plan how to handle the few remaining k2 sites in the future. And things get even more muddled with the announced plans by JW to make a fork of J

On Mon, 15 Jul 2024 at 16:16, Andrew Schmidt @.***> wrote:

I had similar issues on 3 websites. Always thought it is related to titles and aliases, and made severe efforts shortening the titles and aliases, but it did not solve the error message. It happened only on select number of items and is very annoying … <#m-552063968514836521> On Mon, 8 Jul 2024 at 19:13, Andrew Schmidt @.> wrote: Has anyone else been having an issue with saving K2 items possibly related to the amount of extra fields in that item's specified category? My site has three separate categories to organize the items we have. when I try to save or create any item in category id:1, I get an error: "500 Data too long for column 'title' at row 1" or sometimes it says "alias". I've narrowed the problem down to the two 'textarea' extra fields that are in this extra fields group to be what is causing the issue. when I delete these two extra fields, this error no longer shows up. Is there a possible fix for this issue? I need the two 'textarea' fields in this item's category. luckily, this error does not prevent us from adding or making changes to items, but it does make the process of doing so take much longer as we get redirected to the dashboard and then have to click back to the item we were working on. some rows' extra_fields have a length of over 9,000, but I don't see how that might be a reason for the issue as these columns are of type: TEXT and can hold up to 65,535 characters. I have tried changing the column type to "LONGTEXT" as a similar issue on stack overflow suggested, but that did not work. any suggestions or knowledge will help. Thanks — Reply to this email directly, view it on GitHub <#89 https://github.com/eworkers/K2ForJ4/issues/89>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEE5GULVAELNNHWK6NLBVDLZLK3CRAVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TMMBUGAZTEOI https://github.com/notifications/unsubscribe-auth/BEE5GULVAELNNHWK6NLBVDLZLK3CRAVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TMMBUGAZTEOI . You are receiving this because you are subscribed to this thread.Message ID: @.>

Were your issues ever tied to the same category or a category using specific extra fields? I'm surprised that not more people have mentioned this issue if you've had this on 3 websites. I have this problem on all branches of this website.

— Reply to this email directly, view it on GitHub https://github.com/eworkers/K2ForJ4/issues/89#issuecomment-2228482561, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEE5GUKDGFRQJM3IYHXQ7PLZMPDS7AVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRYGQ4DENJWGE . You are receiving this because you commented.Message ID: @.***>

[UIIBA]

Yes the issue was related to only one specific category and I did not even associated it with the extra fields since the error was explicitly blaming the ‘alias’ and I had not associated the extra fields also have alias. Always thought it is about title alias. Only after your post I figured it out but it makes no sense. My extra fields alias are always short and handy for I call them individually by alias in my subtemplates as it was suggested by JW. Only god knows how deep K2 workings are within J. That is why I asked @eworkers to clear the future for the fork in order to plan how to handle the few remaining k2 sites in the future. And things get even more muddled with the announced plans by JW to make a fork of J On Mon, 15 Jul 2024 at 16:16, Andrew Schmidt @.> wrote: … I had similar issues on 3 websites. Always thought it is related to titles and aliases, and made severe efforts shortening the titles and aliases, but it did not solve the error message. It happened only on select number of items and is very annoying … <#m-552063968514836521> On Mon, 8 Jul 2024 at 19:13, Andrew Schmidt @.> wrote: Has anyone else been having an issue with saving K2 items possibly related to the amount of extra fields in that item's specified category? My site has three separate categories to organize the items we have. when I try to save or create any item in category id:1, I get an error: "500 Data too long for column 'title' at row 1" or sometimes it says "alias". I've narrowed the problem down to the two 'textarea' extra fields that are in this extra fields group to be what is causing the issue. when I delete these two extra fields, this error no longer shows up. Is there a possible fix for this issue? I need the two 'textarea' fields in this item's category. luckily, this error does not prevent us from adding or making changes to items, but it does make the process of doing so take much longer as we get redirected to the dashboard and then have to click back to the item we were working on. some rows' extra_fields have a length of over 9,000, but I don't see how that might be a reason for the issue as these columns are of type: TEXT and can hold up to 65,535 characters. I have tried changing the column type to "LONGTEXT" as a similar issue on stack overflow suggested, but that did not work. any suggestions or knowledge will help. Thanks — Reply to this email directly, view it on GitHub <#89 <#89>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEE5GULVAELNNHWK6NLBVDLZLK3CRAVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TMMBUGAZTEOI https://github.com/notifications/unsubscribe-auth/BEE5GULVAELNNHWK6NLBVDLZLK3CRAVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TMMBUGAZTEOI . You are receiving this because you are subscribed to this thread.Message ID: @.> Were your issues ever tied to the same category or a category using specific extra fields? I'm surprised that not more people have mentioned this issue if you've had this on 3 websites. I have this problem on all branches of this website. — Reply to this email directly, view it on GitHub <#89 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEE5GUKDGFRQJM3IYHXQ7PLZMPDS7AVCNFSM6AAAAABKRE5HVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRYGQ4DENJWGE . You are receiving this because you commented.Message ID: @.>

I went into Global config and enabled some debug settings. This is my call stack that I have when I attempt to save. I'll post this here now and then see if I can figure out what is going on

[UIIBA]

Not a very productive update, but I have gone through the call stack and made a table of each line item and what it's doing if there was a comment provided near the code. there are two line items that mention a compatibility for J4.

I'd insert a table for the ability to copy this info, but I am not sure how. I'm hoping someone more experienced can help dissect these lines and find a possible solution. Here is the call stack from hitting "Save" (the image I posted in my last comment is a call stack for "Save & Close" and "Save & New". Notice: line item 15 on PHP 37"$this->save();" is not called when those two options are selected, but is called when just selecting "Save" so I don't believe it is part of the problem) I have my suspicions on calls 14 or 16, but I could be wrong. Any help would be much appreciated.

[eworkers]

Please check if ca26870 solves your issue

[UIIBA]

Please check if ca26870 solves your issue

I found out that the problem is related to too many extrafields being enabled in an extrafiield group, but that did not fix the issue. I'll post the new call stack and error below:

The error above the call stack is now just the JSON stored in the "k2_extrafield" column in the DB

[eworkers]

Sorry, we mistakenly forgot to remove the exception code inserted for debugging purposes, please try the last commit and report back

[UIIBA]

Sorry, we mistakenly forgot to remove the exception code inserted for debugging purposes, please try the last commit and report back

Haha yep it works now. thanks!

[eworkers]

closed by ca26870 + f53f2b3