Forums / Install & configuration / Limitations in how many fields a content class can have?

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Limitations in how many fields a content class can have?

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
Atle Enersen	Wednesday 29 January 2003 12:01:28 pm (RC1) Are there known limitations regarding how many fields a class (in my case a content class) can have? I'm in "Class edit" btw. I have a class with 21 fields, and when I tried to add field nr. 19 (hitting the New after selecting the required fieldtype) it came out with no "Type". I ignored it, filled in the info and submitted (by adding once again a new field). It croaked, gave errors on all fields, but the new field with the correct type, and the "errorous" field - also this with correct type, where there. Filled in info for the new field, submitted by adding a new one, everything correct still, filled in the info for the last field (nr. 21 btw.) and chose to store. It worked. Did I experience a bug or a limitation or what...? I have seen the same error manifest itself like described above earlier (alson on RC1), but I do not recall if it happened on field nr. 19 then. \atle\ --
Vincent Saulnier	Thursday 30 January 2003 5:47:23 am > (RC1) > > Are there known limitations regarding how many fields a > class (in my case a content class) can have? I'm in "Class > edit" btw. > > I have a class with 21 fields, and when I tried to add field > nr. 19 (hitting the New after selecting the required > fieldtype) it came out with no "Type". I ignored it, filled > in the info and submitted (by adding once again a new > field). > > It croaked, gave errors on all fields, but the new field > with the correct type, and the "errorous" field - also this > with correct type, where there. > > Filled in info for the new field, submitted by adding a new > one, everything correct still, filled in the info for the > last field (nr. 21 btw.) and chose to store. > > It worked. > > Did I experience a bug or a limitation or what...? > > I have seen the same error manifest itself like described > above earlier (alson on RC1), but I do not recall if it > happened on field nr. 19 then. > > \atle\ > -- I had the same problem! But I think you explain it better than me! http://www.ez.no/bug/bugview/1726/ I added a screenshot but I think it didn't work.
Jan Borsodi	Wednesday 05 February 2003 4:36:09 am > > (RC1) > > > > Are there known limitations regarding how many fields a > > class (in my case a content class) can have? I'm in > "Class > > edit" btw. > > > > I have a class with 21 fields, and when I tried to add > field > > nr. 19 (hitting the New after selecting the required > > fieldtype) it came out with no "Type". I ignored it, > filled > > in the info and submitted (by adding once again a new > > field). > > > > It croaked, gave errors on all fields, but the new field > > with the correct type, and the "errorous" field - also > this > > with correct type, where there. > > > > Filled in info for the new field, submitted by adding a > new > > one, everything correct still, filled in the info for > the > > last field (nr. 21 btw.) and chose to store. > > > > It worked. > > > > Did I experience a bug or a limitation or what...? > > > > I have seen the same error manifest itself like > described > > above earlier (alson on RC1), but I do not recall if it > > happened on field nr. 19 then. > > > > \atle\ > > -- > > I had the same problem! > But I think you explain it better than me! > > http://www.ez.no/bug/bugview/1726/ > I added a screenshot but I think it didn't work. There is no limitation of number of attributes by design, the limitations are made by database, apache, php or the browser. Creating a class with 100 attributes should be no problem. However I believe the problem was in the template engine and some PHP references, this problem is fixed for the RC2 release. I just tested a new class with 42 attributes (all datatypes twice) and it worked perfectly, even creating an object with it. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Vincent Saulnier	Wednesday 05 February 2003 6:03:30 am > There is no limitation of number of attributes by design, > the limitations are made by database, apache, php or the > browser. > Creating a class with 100 attributes should be no problem. > > However I believe the problem was in the template engine and > some PHP references, this problem is fixed for the RC2 > release. > > I just tested a new class with 42 attributes (all datatypes > twice) and it worked perfectly, even creating an object with > it. Thank you!