[#44514] - [6.1] Custom Fields: Trigger deprecation on non-numeric item-ID
- Pending
- Medium
- Build: 5.3-dev
- # 44514
- Diff
- Hackwar:5.3-fields-numeric-itemid
User tests: Successful: Unsuccessful:
Summary of Changes
Custom fields currently allow to use non-numeric IDs for the content items. This is a huge problem, because because of that the itemid column in #__fields_values is a varchar and this dramatically slows down any access to that table. Eventually we want to convert this column to integer. This PR for now triggers an error when a non-numeric ID is used.
Testing Instructions
Codereview
Link to documentations
Please select:
-
Documentation link for docs.joomla.org:
-
No documentation changes for docs.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_fields |
This pull request has been automatically rebased to 6.0-dev.
| Title |
|
||||||
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-06-16 20:29:56 |
| Closed_By | ⇒ | Hackwar | |
| Labels |
Added:
Feature
PR-6.0-dev
Code Review
|
||
| Status | Closed | ⇒ | New |
| Closed_Date | 2025-06-16 20:29:56 | ⇒ | |
| Closed_By | Hackwar | ⇒ |
| Status | New | ⇒ | Pending |
This pull request has been automatically rebased to 6.1-dev.
| Title |
|
||||||
Only a problem on mysql and maybe mariadb