On lines 860 and 871 in the file entityreference.module, #maxlength is set to 1024. This causes serious problems for site owners who create fields with unlimited settings. Once that limit is set and met, you're screwed for adding more references to nodes within the respective field, which is the case I just ran into with my configuration. I currently have a field called "field_pro_assoc_products" (which I can modify settings to at admin/config/people/accounts/fields/field_pro_assoc_products) -- it's a field I use on users' profile pages to allow them to note what products they're associated with, which was a business requirement for my particular project. On the settings page for this field, I set the field to have "unlimited values". Unfortunately, entityreference doesn't care if this is set because 1024 is hard-coded into entityreference.module.
In order to "treat the symptom", I increased this hard value in the file to 2048, but obviously this stinks and creates a maintenance headache.
Has this been parametrized in a newer version? I'm currently using 7.x-1.1 and would love to see this be fixed.
Despite my little gripe, I think your module is amazing. Keep up the great work! Any insight is appreciated!
Comments
Comment #1
ebenfarnworth CreditAttribution: ebenfarnworth commentedI know this is an old thread, but I just ran into the same problem. I need the ability to have lots of auto created references in one entity reference field. I'm planning to manually set the value, the same way as Wolf_22 is doing. I'm also using 7.1.1 version of the module. If I set the value to a much higher number say 3000 or more, are there any performance implications?
Thanks for creating such a useful module.
Comment #2
Wolf_22 CreditAttribution: Wolf_22 commentedebenfarnworth -
I know you probably directed that question to the author(s) of the module but for whatever it's worth, I never experienced any negative side effects and I was able to finally add more entries, too. I might be wrong but I'm betting that the settings for that input are done the way they are due to it being a basic text input--not because it somehow translates over into determining processing throughput or whatever of the data being received from within the input (if that even makes sense). Then again, I'd love to hear from the authors to validate this theory...
Comment #3
quotesBro CreditAttribution: quotesBro commentedI've just faced the same issue and had to hack entityreference.module because changing #maxlength via hook_form_alter() didn't help.
Comment #4
quotesBro CreditAttribution: quotesBro commented