3 High Priority Bugs Left!

[Phil Haack]

Hi all,

 

Only 3 high priority bugs left!

http://code.google.com/p/subtext/issues/list?can=2&q=priority=High&colspec=Stars%20ID%20Attachments%20Type%20Status%20Priority%20Milestone%20Owner%20Summary

 

Let me know if there are any other bugs that you think should be high priority for this release. This is going to be a great release! But I need your help to test and help perf tune this one.

 

Also, the upgrade is going to be the most challenging because of the changes to how skins work. I’m drafting a blog post on the topic. I’d love to automatically fix up skins for the users, but that would require write access to their web directory and I generally recommend against allowing that.

 

Phil

[Simone Chiaretta]

>
> Let me know if there are any other bugs that you think
> should be high priority for this release. This is going to be a great release! But
> I need your help to test and help perf tune this one.
>

Do you think we could wait to release till Lucene is integrated into
Subtext? I know I didn't have the chance to work a lot on this, but if
you say we want to include it, then I work on it.

>
> Also, the upgrade is going to be the most challenging
> because of the changes to how skins work. I’m drafting a blog post on the
> topic.

Would you send a list of changes that need to be done so we can fix
all the core ones?

> I’d love to automatically fix up skins for the users, but that
> would require write access to their web directory and I generally recommend
> against allowing that.

We already ask to make the db user a DBA for the install: we can ask
to allow write as well.
Or maybe make a small utility that processes the files offline.

Simo
>
>
> Phil
>
>
>
>
> >
>
>
>
>

--
Simone Chiaretta
Microsoft MVP ASP.NET - ASPInsider
Blog: http://codeclimber.net.nz
RSS: http://feeds2.feedburner.com/codeclimber
twitter: @simonech

Any sufficiently advanced technology is indistinguishable from magic
"Life is short, play hard"

[Simon Philp]

I will go through the issues list today and verify, report anything I
find.

I think it would be good to have Lucene implemented, does this efffect
the related posts usercontrol functionality aswell? Simo feel free to
grab me on msn/wave if you'd like a hand :)

List of changes would be a good insight as my new skin is nearly
complete but stopped with the significant changes coming up. I can go
through one of the default skins and do a post about converting it
from current to new :)


Si



On Nov 1, 7:10 am, Simone Chiaretta <simone.chiare...@gmail.com>
wrote:

[Phil Haack]

Yes, let's get Lucene in. How much time?

I already fixed all the existing skins and the ones in the gallery.

I think making user have write access is trickier for hosted sites. A
tool would be great. Or even a page that shows the upgrade steps if we
detect. Problem.

Phil

Sent from my mobile phone

On Nov 1, 2009, at 12:11 AM, "Simone Chiaretta" <simone.c...@gmail.com

[Simone Chiaretta]

Yes, let's get Lucene in. How much time?

Technically it's not that much... just have to find the time to :)
But I'll try to commit a working copy in a week or two
 

I already fixed all the existing skins and the ones in the gallery.

Awesome :)
 

I think making user have write access is trickier for hosted sites. A
tool would be great. Or even a page that shows the upgrade steps if we

detect problem.

Are the changes just a matter of find&replace? Or are they more complex?
If they are just find&replace probably the tool will not take long... otherwise, from experiences I had with automatic code migration, it usually takes a lot of time since code formatting and other stuff make simple find&replace procedures ineffective.

Simo

 

[Phil Haack]

Unfortunately, not as simple as a find/replace. The short version is that I’ve removed the central Skins.config that used to be in the Admin folder. Now, each skin has its own skin.config file that’s located in the directory of the skin. This will make skins much easier to share and deploy.

 

Phil