But this would mean to process the image in PHP and not being able to deliver the image by the webserver directly, right?
So, instead of <img src="somehost.com/images/background.jpeg"> it would be <img src="somehost.com/show_image?img=background.jpeg"> right? This would make i18n easier, but this also would mean a "slower" webserver. Does anyone currently use this method? What are other advantages, disadvantages? Regards, Dirk On 26 Sep., 00:12, teknoid <[EMAIL PROTECTED]> wrote: > Take a look at the html helper's image() method. > > It should be relatively easy to override with AppHelper to suit your > needs. > > On Sep 25, 6:09 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > Hi there, > > > I want to give users the possibility to upload their own themes > > directly to the filesystem - similar to how wordpress does this. > > > With the current theme-sctructure in Cake, I have a problem on how to > > deal "files". CSS and JS could be handled somehow, I guess, but what > > about images? > > > When the user uploads a complete theme folder and has images in it, > > how should I render them? Having Image-URLs in the HTML of the themes > > that then need to be processed by the application to "render" an image > > just doesn't seem right. > > > Has anyone else had this problems? And how did you solve them? Only > > allowing themes through an upload method in the application which then > > could transfer images somewhere underneath /app/webroot? > > > Cheers, > > Dirk > > -- > > http://noserub.com > > http://identoo.com/dirk.olbertz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
