User tests: Successful: Unsuccessful:
Change the Smart Search #__finder_links.route column from varchar(400) to ext for MySQL and PostgreSQL.
This prevents Smart Search indexing from failing when generated routes exceed the previous 400 character limit.
Supersedes #44414.
Use a site with article aliases close to 400 characters and run the Smart Search indexing process from Components, Smart Search, Index.
The indexing process can fail with a database error similar to Data too long for column 'route' at row 1.
The index is built without failing because of long route values.
No documentation changes needed.
| Status | New | ⇒ | Pending |
| Category | ⇒ | SQL Administration com_admin Postgresql Installation |
I have tested this item ✅ successfully on 07dca15
I'm not really happy with this change. The consensus is that the safe maximum number of characters in a URL is 2048. A normal non-SEF Joomla URL should not be more than maybe 100 characters and maybe there are situations where we could turn a blind eye to 200 or even 300 characters, but non-SEF URLs with more than 400 characters are simply a sign of a broken architecture. I don't want to support that to be honest.
I have tested this item 🔴 unsuccessfully on 07dca15
The length of an article alias was limited to 344 characters during my tests.
The indexing process would not fail even if the PR was not yet applied.
I have tested this item 🔴 unsuccessfully on 07dca15
The length of an article alias was limited to 344 characters during my tests.
The indexing process would not fail even if the PR was not yet applied.
"Text" columns are saved physically on another location and makes the query slower, so I would extend the varchar in this case.
better change the field to 2048 and hope that nobody finds out that get requests doesn't have a length limit.
com_finder also has its install SQL in the component folder and thus that would have to be adapted as well. Again, I don't think changing this field is a good idea and instead the affected components should change their routing, but it isn't the hill I'm going to die on.
| Labels |
Added:
Feature
PR-6.2-dev
|
||
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-11-06 10:23:57 |
| Closed_By | ⇒ | MacJoom | |
| Labels |
Added:
PR-6.3-dev
|
||
| Status | Closed | ⇒ | New |
| Closed_Date | 2026-11-06 10:23:57 | ⇒ | |
| Closed_By | MacJoom | ⇒ |
| Status | New | ⇒ | Pending |
I still think that it is a mistake to blow up this column. A text column would be way to much for something that shouldn't be more than 250 characters and in reality shouldn't be more than probably 50 or 80 characters. Lets not support broken architectures.
I still think that it is a mistake to blow up this column. A text column would be way to much for something that shouldn't be more than 250 characters and in reality shouldn't be more than probably 50 or 80 characters. Lets not support broken architectures.
its now varchar(2048)
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-11-06 11:37:26 |
| Closed_By | ⇒ | MacJoom |
I still think that it is a mistake to blow up this column. A text column would be way to much for something that shouldn't be more than 250 characters and in reality shouldn't be more than probably 50 or 80 characters. Lets not support broken architectures.
I still have a webseite with blown up aliases that fails the reindex because of the route field beeing too short. I changed this manually to text - with no issues. I don't need this PR for my website - but i can imagine other have this problem too.
So either fix the architecture or accept this bandaid.
i am in favour of varchar(2048)
I have tested this item ✅ successfully on 07dca15
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48077.