Upgrade for 5 !

wohoo... it worked!!!!

Thank you, thank you , thank you!!!

Now everyone on my website can have her/his own blog with their own chosen theme, while the main website stays under the main theme, and while it all happens within one database.

Here's what I did:
1) went to http://drupal.org/project/blogtheme and downloaded the 4.7 version , and uploaded that forlder called "Blogtheme". Naturally, it didn't show up in the Admin>>Modules.
2) Then I went to http://drupal.org/node/130769 . Download that attachment. Rename it so that it ends with ".zip". Open the zip file. Drag and drop all files in that zip file into "Blogtheme" folder. Now this module with show in Admin>>Modules . Enable it and that's it.

There are no options to control or manipulate this module, but hey it works and it does everything it sais on the tin.

Very handy. I hope an option for something like this is incorporated in the 5.2 or 6.x core.

Thanks again, Christefano.

Thanks for the report, matrixfighter. Hopefully others can review it, as well. I haven't used this yet so I won't set it to RTBC.

Hi, I'm just testing this as well. Thanks a lot, vadbars!

So far, anything seems to working the way it should (that means, as it would work in 4.7.x).

There is just one minor issue that is probably the same in 4.7.x:

the comment form of a blog entry won't use the theme chosen by the blog author, but the main theme or the theme chosen by the user who is commenting.

But I guess the reason for that is, that for comments, the comment module and not the blog module is used. So this is rather a feature request, not a review if vadbars patch works on 5.x. Which it does!

So maybe I should open a feature request regarding the comment form (or try it myself).

Another issue: it's not possible to divide the blog theme from the theme chosen by the user - therefore for him/her the mainpage and other pages that are not his or someones else blog will be presented in the theme chosen for his/her blog. Or did I miss anything regarding this? But this is also rather a feature or support request as I don't think it's implemented in the 4.7.x version of blogtheme.

I jotted those issues down so that anyone using the 4.7.x module could check if this was implemented in the 4.7.x version.

Thanks, Chris (still a drupal noob but already loving it!)

Hi, I'm just testing this as well. Thanks a lot, vadbars!

So far, anything seems to working the way it should.

There is just one minor issue (which is probably the same in 4.7.x):

the comment form of a blog entry won't use the theme chosen by the blog author, but the main theme or the theme chosen by the user who is commenting.

But I guess the reason for that is, that for comments, the comment module and not the blog module is used. So this is rather a feature request, not a review if vadbars patch works on 5.x. Which it does!

So maybe I should open a feature request regarding the comment form (or try it myself).

Another issue: it's not possible to divide the blog theme from the theme chosen by the user - therefore for him/her the mainpage and other pages that are not his or someones else blog will be presented in the theme chosen for his/her blog. Or did I miss anything regarding this? But this is also rather a feature or support request as I don't think it's implemented in the 4.7.x version of blogtheme.

I jotted those issues down so that anyone using the 4.7.x module could check if this was implemented in the 4.7.x version.

Thanks, Chris (still a drupal noob but already loving it!)

the upgrade 5 is a duplicate of : http://drupal.org/node/108075
A D5 version has just been released.

For bug report and feature requests, please open one new issue per bug and per feature.

i use txt file in this post and it's work for me

i try the new release version 5.x-1.0 on download link, it was error, sori i forgot the error says, maybe like ( not espected

oc i try it again ones more and...
Parse error: parse error, unexpected ')' in C:\sites\all\modules\blogtheme\blog_theme.module on line 32

Thanks for reporting. It's fixed in the version blogtheme 5.x-1.1.