On 7/1/07, Ryan de Laplante <[EMAIL PROTECTED]> wrote:
>>> I tested $url.resource() with shared, preview and customized themes >>> and it worked fine everytime. When customizing a theme, the theme >>> resources are automatically and correctly copied into the weblog's >>> file upload area. >> I get the impression that if you want to use a theme with graphics >> and CSS (every one of them), then after selecting the theme you have >> to click the Customize button to have it copy the files. I don't >> understand why Roller was changed to use $url.resource instead of >> $url.themeResource, but a change was not made to automatically copy >> the required files to the user's data directory? Basically this has >> broken every theme unless the user knows to click "Customize". > > I think you just have the wrong concept of how the themes work and > what is supposed to be happening. What you described is the expected > behavior. Ok so let's walk through a scenario. Lets say that I'm interested in the Yellow Theme for my blog. I choose the Yellow Theme and click the save button. I do not want to make any customizations, I just want to use it as-is. Now I go to my blog webpage and see a bunch of un-styled text, with no graphics. This is not what the theme designer intended. Why is this expected behavior?
If that is happening there is a bug and we need to find it and fix it, but we're gonna need your help because I cannot duplicate the problem you describe. When I pick a theme and click "save" all resources are available via resource/<blog-handle> style paths. The resource servlet correctly determines that the theme is shared and serves the resources from the shared themes directry. And, when I click "customize" to customize the theme, the resources are copied correctly. - Dave
