No more changes beyond ROL-2039. Give me another day, if I'm not finished by tomorrow morning I'll punt it to you. I hate working on the database, however necessary it is.

The 5.0.4 to 5.1.0 migrations won't work because the templates weren't getting copied from webpage to custom_theme_rendition as they need to, and hence changes to them aren't being saved. As part of the migration script, the data in the webpage table needs to get copied into custom_theme_rendition so Roller 5.1 will work out of the box. That's what I'm working on now.

Glen

On 07/19/2014 09:26 AM, Dave wrote:
Also, I'd like to start doing migration testing on my site's database, and
the one from blogs.apache.org, but I don't want to do that until we freeze
the schema for the 5.1 release.

Are we ready to do that yet, or do you have more changes to suggest?

- Dave



On Sat, Jul 19, 2014 at 9:24 AM, Dave <snoopd...@gmail.com> wrote:

At this point the UI allows a user to set the content type for a page
template and the PageServlet respects that choice. We do not have a way to
set the content type for each rendition of a page template, and I'm not
sure we really need that feature. So, for now I'd recommend removing
content type from custom_template_rendition, since it is not used.

- Dave





On Sat, Jul 19, 2014 at 9:08 AM, Glen Mazza <glen.ma...@gmail.com> wrote:

But isn't that the contenttype value in custom_template_rendition?

Glen


On 07/19/2014 08:58 AM, Dave wrote:

Please do not remove outputtype either.  Page templates can be used to
generate XML, JSON and other types of output and you need to be able to
set
the content-type when you produce those types.

- Dave


Reply via email to