limit to add custom fields

[Milbo]

I have just installed VM3.2.3Rev9574  (from SVN) and varchar(4095) is used for custom_value

custom_value is not the customfield_value. The custom table holds the prototypes. But we need a lot space for the product customfields.

[jenkinhill]

OK, wrong table.  customfield_value is still varchar(2500) in VM3.2.3.9577 - the latest one I am testing.



Or have I got that one wrong?

[iskye81]

@iskye81 check your server php resources. See   http://forum.virtuemart.net/index.php?topic=126888

As I already mentioned this doesn't work. I have the same issues as kona333, i.e. adding the lines to php.ini does nothing and adding them to .htaccess results in a server error.

[Milbo]

OK, wrong table.  customfield_value is still varchar(2500) in VM3.2.3.9577 - the latest one I am testing.



Or have I got that one wrong?

You are right. Yes it must be that way. The customfield_value is mainly used for VALUES, like a size. So it planned to use it as key. At the moment we have just a group by, but also ordering.

But the customfield_params are text now. As I maybe mentioned before, the textfields must be ported to use a param for the content. I could write this within 20 minutes. That is easy. The problem is the Backwardcompatibility.

I could add it next release (vm3.2.5) for a silver http://extensions.virtuemart.net/support/virtuemart-supporter-membership-silver-detail

[iskye81]

Does this mean there's no way around this issue at the moment?

[jenkinhill]

I could add it next release (vm3.2.5) for a silver http://extensions.virtuemart.net/support/virtuemart-supporter-membership-silver-detail