Closed (fixed)
Project:
Custom Formatters
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Nov 2011 at 10:51 UTC
Updated:
28 Jun 2012 at 13:01 UTC
The performance in the backend is very bad and get timeouts or out of memory errors. Do you try to load all nodes of a type when changeing "Bundle"?
Maybe you can use a autocomplete field for Preview?
Comments
Comment #1
digitaldonkey commentedI Added a limit to avoid custom_formatters trying to do a node_load for 10000 entities.
It's a bad sulution to hard-Linit Like this. Would be great to have a Autocomplete Field here to load a certain node.
Comment #2
deciphered commentedLimit makes sense, I'd possible consider lowering it, 300 still seems to be a lot.
Also, can you actually upload the patch instead of pasting it in? When you do that, please set the issue to 'needs review'.
Comment #3
digitaldonkey commentedFor my opinion this is too dirty to become a serious patch.
People will ask "post 301 will never get shown" if we commit this.
Comment #4
deciphered commentedTo be honest, 300 is way to many, this is purely for testing the creation of a Formatter, if you can't do it with one entity then your doing something wrong (I'm not accusing you of doing something wrong, I'm making a point).
At most I think 10 should be more than enough, and maybe some way to search or filter the entities.
Comment #5
julien.reulos commentedHi,
I use the 7.x-2.x-dev version, and what I do to limit the result number is adding a range to the query:
Comment #6
deciphered commentedFix committed to 7.x-2.x-dev.
Limited to 50 randomised nodes.
Comment #7.0
(not verified) commentedUpdated a solution proposal