On 6/15/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
More comments below ...
Dave Johnson wrote:
> Comments below...
>
> On 6/15/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
>> Dave Johnson wrote:
>> > Thanks for the feedback. Lots of good suggestions there.
>> > On 6/14/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
>
>> My biggest concern with this is doing it on a weblog by weblog basis, if
>> we make this decision on a site-wide level then i think we will be in
>> better shape.
>>
>> > 2 - Turn on Atlas, but continue to support old model
>> > site.macromodel=roller_3.0
>> > Velocity context loaded with either OLD or NEW model stuff,
>> depending on
>> > blog
>> > Create weblog page shows NEW themes only
>> > This is the default for upgrades
>>
>> Again, doing this on a blog by blog basis has me *really* scared. I am
>> okay with this option as a site-wide option, but I see a lot of
>> potential problems doing it blog by blog.
>
> I don't understand your concern here. What problems do you think we'll hit?
Well, take BSC for example. We've been using Roller since pre-1.0 days
and we have a lot of old blogs and a big pile of users. When we upgrade
to 3.0 we are going to have to maintain some backwards compatability for
old themes, so we are going to have to keep them around using the old
templates.
What happens if a new user signs up, creates a blog with macromodel=3.0,
and then tries to use one of the old themes? I don't see any (or
reason?) for Roller to try and decide what themes a user has access to
based on this setting, so it's entirely possible that a weblog with
macromodel=3.0 will attempt to use some pre-3.0 template code.
If we do things right we can completely avoid the problem you mention.
Here's a slight adjustment to the options I presented before. With the part
I added about the theme chooser, I don't think there is any room for a
theme/model mix up here.
1 - Turn on Atlas, completely turn off old model
site.macromodel="roller_3.0_only"
Velocity context loaded with only NEW model stuff
Create weblog page shows only NEW themes
*** Theme chooser shows only NEW themes based on website.macroVersion
This is the default for new installations
2 - Turn on Atlas, but continue to support old model
site.macromodel=roller_3.0
Create weblog page shows NEW themes only, defaults to new model
Velocity context loaded with either OLD or NEW model stuff, website.macromodel
*** Theme chooser shows OLD or NEW themes based on website.macromodel
This is the default for upgrades
>> > One Roller site can support both classic and Atlas themes, but I
>> > really want to avoid having themes that use a mix of classic and Atlas
>> > macros. A weblog MUST pick which macro/model it will use. I was going
>> > to use website.pageModels as a flag to indicate which macro/model, but
>> > perhaps that is too confusing. Instead, we could force weblogs to
>> > declare which version of macros should be used.
>> >
>> > website.macrosVersion=2.0
>>
>> To be honest, I don't think this is realistic. I agree that this is the
>> ideal way it would work, but I don't see it happening. We don't have
>> any real way of ensuring that upgraded installations don't do something
>> to make old template stuff available to weblogs that are set to use the
>> 3.0 macros only.
>
> I'm more concerned about this one. I'd hate to see weblogs with a mix
> of both schemes.
I hate that thought as well, but I'm not sure we can prevent it. Maybe
it's possible, i'd need to think about it more, but right now it seems
problematic to me.
Yes. Do think about it some more. Anybody else want to weigh in?
- Dave
