THANK YOU , it works now. Admin could get K+5 to Tomaselli

Admin : think you should place your poll in a new topic

Admin, please don't use the jQuery UI, it's nice but it's too heavy!!!!

I have few controls already done for JDOM, I'll post them, I'll do in the next days, I have to work now.
I have created an addresspicker with googlemap+autocompletion+bootstrap+custom jquery plugin (by me), a nice tags input, and a better datetime picker

jQuery UI, I don't like. It was only a question.

Cook only implements the strict necessary from jQuery IU (Sortables, Draggable, ...)

Tomasselli K+3, and soon a lot more I guess, with your coming propositions !!! Cool !

Have any of you tried to implement Tomaselli's code in latest Joomla 3.2 using current Cook version?
I've tried, but continue to get a Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in ..../public_html/libraries/legacy/view/legacy.php on line 768

Hi @dyvel,
I'm currently using that system on several j3.x websites , I didn't experience any error yet, it seems to me a problem related to something else.
Are you trying to output a long list of items with JDOM?

I would have asked the same.

When you want memory optimization, output the JDom code in the context, and then copy/paste the HTML.
Then, apply the dynamic changes with php.

JDom is nice for developper because it abstract it all, but for long lists or pdf, you can also try the optimized way.

I have experimented such issue with PDF creation already (dompdf). PDF is using a lot of memory.
I think it is normal. Optimize the HTML avoiding JDom.

Personally, I have fixed my issue by reducing the length of the PDF to a certain amount of items.

I've tried to remove pretty much everything from the page, but still getting errors.

trying to debug, I removed the line:

from my view. Then an empty pdf was generated and downloaded... so at least the pdf generation is working. Is there anything about that line that would require a modification?

Did you tried to remove the dump of the object ?

Because the line you have removed is killing the HTML. Output nothing, so it will not overload... this is normal.
It is not solving the problem. you can do exit() at the begining of the component and it will never again report errors.... lol. Dev humour...

- Try 'return' at different places of the template. So you can try to render a part of HTML only (until return).