You should be able to trigger image generation at any time you want 
programatically. Magnolia does so only when image is requested to avoid 
generating images again and again after each update even if they are not used. 
If you have site w/ many images, to generate all  desired variations from them 
just because they were all updated could keep your server busy for while and 
you still don't know if all those variation are going to be requested before 
next update.

Regarding deprecated code, as of Magnolia 4.5 all Content API was deprecated. 
This was done mainly to advise users to use new Node API, however Magnolia 
provides tools to convert Node into Content and vice-versa. Content API is 
going to stay around for while.

HTH,,
Jan

On Aug 28, 2012, at 5:37 AM, SenthilNathan S (via Magnolia Forums) wrote:

> Hi,
> We are planing to use the imaging module for image resizing in our 
> project.But we need to do this programatically during a backend job.Currently 
> the image gets resized only when we hit the imaging module url in the 
> browser.Is there any way I can achieve this resizing programatically without 
> hitting the URL.
> I also analyzed the Imaging servlet which is actually instantiating the 
> ImageGenerator class to trigger the chain of operations.But I could see a lot 
> of deprecated code.
> 
> -- 
> Context is everything: 
> http://forum.magnolia-cms.com/forum/thread.html?threadId=4a05c09e-67b1-40d1-80fc-1a020cac468a
> 
> 
> ----------------------------------------------------------------
> For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
> Alternatively, use our forums: http://forum.magnolia-cms.com/
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------




----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to