User tests: Successful: 0 Unsuccessful: 0
Pull Request for Issue #42671 .
ALTER "name" and "title" columns to varchar(255) for #__assets table
ALTER "name" and "title" columns to varchar(255) for #__assets table
ALTER "extension" to varchar(100) for #__categories table
ALTER "extension" to varchar(255) for #__workflows and #__workflow_associations tables
code review
and or install this demo extensions
https://test5.richard-fath.de/com_testextensionwithlongname_100.zip
thanks to @richard67
Status | New | ⇒ | Pending |
Category | ⇒ | SQL Administration com_admin Postgresql Installation |
I have reviewed the code, and it seems fine. However, code review alone isn't enough for testing. We need a real test by creating a category with a long extension name to identify any additional issues beyond the one mentioned
Labels |
Added:
Code Review
PR-5.3-dev
|
yes if someone can share such extension ....
I have tested this item 🔴 unsuccessfully on 30f5be7
Though I mentioned as "code review alone isn't enough for testing", I checked by applying this patch and unfortunately it is not working.
I have tested this item 🔴 unsuccessfully on 30f5be7
how do you apply the patch ?
Status | Pending | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-03-24 21:47:13 |
Closed_By | ⇒ | alikon |
i'll not invest much more time on this
I don’t think code review is sufficient for testing. I think it needs a real test with creating a category for an extension with a long extension name. This test will then show that there will be other errors happening besides the one mentioned in the issue when using such long category titles.