Offhand, it looks like we can remove it, once I clean up the code a bit. This column isn't getting populated when I do a custom stylesheet alone; however, when I switch to a complete custom theme, it then copies the name of the stylesheet into weblog.customstylesheet. But it doesn't need to do that, that value is already in weblog_custom_template, and I don't think it does anything with that value anyway.

Anyway, all the other columns in the list were removed, if I can't get to this remaining column it can wait until 5.1 is out.

Glen


On 07/23/2014 10:08 PM, Glen Mazza wrote:
No, in *that* case, we just get a single row in the custom_template_rendition table for that CSS holding the stylesheet text (instead of several rows holding also the theme templates.) It's just that weblog's customstylesheet column is still being written to and read from for some reason (still necessary? I don't know...), which I'll investigate. Apparently it's being used as a path value from the user's resources folder (custom stylesheet path), but that shouldn't be necessary as the CSS text is in the CTR table. Stay tuned...

Glen

On 07/23/2014 09:57 PM, Dave wrote:
On Wed, Jul 23, 2014 at 9:38 PM, Glen Mazza <glen.ma...@gmail.com> wrote:

Hmm...Weblog's customstylesheet column is perhaps still in use, I'll look
more into it tomorrow.

As I remember, custom style sheet is a way to allow a blogger to add CSS
for their blog while still using a shared theme, and not having to edit
page templates. I think it is totally separate from the custom templates.

- Dave



Reply via email to