Matthew Schmidt wrote:
Hi guys. We're in the middle of upgrading JRoller to Roller 3.1 (and
then on to 4.0) but we're having a bit of a problem with our themes. We
have turned on the legacy theme support, but it seems that all of these
call macros which apparently don't work anymore. New blogs that are
created in the system seem to work fine as they use the new macros, but
the old blogs just don't work. In addition, most people have customized
their blogs in one way or another, making it very difficult for us to
just bulk fix these. Is there a way to make our old themes completely
work?
you'll have to elaborate more on exactly what problems you are seeing?
if the old models and macros aren't working at all then the pages would
just have lots of $etc variables and #showBlah() calls all over the place.
if the legacy models and macros are working but things just aren't
looking formatted properly then it could just be a problem with changes
made to the html/css between versions.
if you set ...
rendering.legacyModels.enabled=true
... in your config file then things should be working, at least for the
most part.
Separately I have two other issues. First, Are you guys doing a 301
redirect on the /page to /blogname? If not, I would recommend it as
Google will likely not be transferring the pagerank for these blogs if
not. Secondly, at JRoller, we have a custom file upload scheme that
stores each weblog's resources in subdirectories sorted by the first
letter of their handle. Was this code ever rolled into the core? It
was code + an update to an image macro that found the proper location.
yes, the old urls are all 301 permanently moved redirects.
no, the upload scheme you mentioned is not in the current code, so
that's a customization you'll have to handle on your own. if i
understand your comment you are doing this ...
${file.uploads}/a/aaa
${file.uploads}/a/arrr
${file.uploads}/b/blah
an easier way to keep that working in newer versions would be to
subclass or modify the FileManagerImpl and just override the necessary
code so that it appends that letter before the handle name. shouldn't
be that hard to do.
-- Allen
Thanks,
Matt
Dave wrote:
On 7/12/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
I think that's fine, but it's extra effort to do that and I don't have
time for it right now. I think just sticking with a simple html or
plain text option will be fine for now, and there won't be any issues
with expanding on that down the road and allowing admins to choose their
own content-type if they want.
So for right now I'm just going to leave things as is and provide just a
single "Allow HTML in comments?" checkbox, which is effectively the same
functionality we have right now. If HTML is allowed then the
content-type for incoming comments will be set to text/html, otherwise
it will be set to text/plain.
Cool?
Yep. Sounds good.
Thanks,
Dave
