No Code Attached Yet
avatar mc-cm
mc-cm
29 Jun 2022

Steps to reproduce the issue

  • create an integer custom field for articles or contacts .
  • set the values to 1 (min) and 99999999, steps 1
  • try to create an article or contact.

Expected result

  • editing form should open.

Actual result

  • server error: Allowed memory size of 8589934592 bytes exhausted (tried to allocate 1073741832 bytes)
  • (importet vaules don't show in the backend, instead "1" is displayed in the forms)

System information (as much as possible)

  • local install
  • 10.8.3-MariaDB
  • utf8mb4_unicode_ci
  • php 7.4.29
  • Apache/2.4.53 (Unix) PHP/7.4.29
  • Joomla! 4.1.4 Stable [ Kuamini ] 24-May-2022 16:00 GMT

Additional comments

Hi there!
Here's the big picture: I needed a 8-digit field to store contact IDs, so I created a custom int field for contacts. First I did this without touching the settings of the field. All the contact data got imported directly to the database, no manual input.
I can see the correct values in the database, I also can see all the contacts in the list. Basically: import works.

But as soon as I try to open and manually edit a contact, the system crashes.

Same behavior for articles.

Some more details: if the int field is only 6digits (max value 999999), editing works. With every digit more it get's slower until editing crashes. If no min / max / step values are present everything works, but I only can enter a max value of "100". Imported values don't show up anyway. They sit in the database but don't show up in the backend of the contact.

Somehow I get the feeling I try to misuse the int field?

avatar mc-cm mc-cm - open - 29 Jun 2022
avatar mc-cm mc-cm - change - 29 Jun 2022
Title
custom INT field makes editing item fail
custom INT field with vaules beyond 999999 makes editing item fail
avatar mc-cm mc-cm - edited - 29 Jun 2022
avatar joomla-cms-bot joomla-cms-bot - change - 29 Jun 2022
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 29 Jun 2022
avatar mc-cm mc-cm - change - 29 Jun 2022
Status New Closed
Closed_Date 0000-00-00 00:00:00 2022-06-29 16:22:58
Closed_By mc-cm
avatar mc-cm mc-cm - close - 29 Jun 2022
avatar mc-cm
mc-cm - comment - 29 Jun 2022

OK, I thought the problem was on the human side.
Thanks for the clarification.

Add a Comment

Login with GitHub to post a comment