ok i think i fixed the problem with the "report this journal" feature seems some lines of code were blocked out.

if anyone has a problem with this not showing let me know I am just waiting on confirmation to see if what i did is correct

From the time I downloaded the install till the time it was running took about 15 mins. Nice job getting this to work with 3.5. very easy install.
I dont understand the journals or blogs, I never used them but some members on the hunting board wanted them.

Again nice job and a very fast install.

im having a problem with editing others journals anyone got that to work?

As an admin I can edit other members journals with no problems.

Delw

well i finally figured it out but i cant let my mods edit them.

I tried setting the permissions(there were some that were coded out with <!-- )
and they always go back to No

I submitted a bug report hoping to get it back soon.

BTW to turn on the report a journal feature it is kinda hard.

Comments from some members arent showing up at all - but from most members they are .... any ideas why that may happen ?

The name appears , and everything else , just not the actual comment ... happened to myself as admin on one or two journals.

Needs a proper importer - but here's a vBJournal to vBDrupal conversion brief.

Hi Everyone,

It's been fixed by one of my Admins. He made some changes to the journal.php file and commented his hack (search for "sn hack" without the quotes) of the code. Feel free to replace your journal.php file with this one. It should work. To the author of this hack, feel free to make use of the code changes, although you may be able to clean it up (not sure. This was done rather quickly, so it could be a quick and nasty).

I make NO guarantees, though. Please make backups of your DB and whatnot. I accept no responsibility for the changed file and offer no support whatsoever.

alright, sorry. It's not completely fixed yet. Still working. The permissions are all messed up, and bbcode also isn't being parced in the journal entries.

At least the journals will display now, and people should be able to update it. Everyone that should have access to it in the admincp may not, though. Also, some functions which may reply on the permissions (for example moderating a journal entry) may either not work or produce an error. Will feedback when I have more news.

ok, sorry. It is fixed :D The permission problem "seems" to have been fixed by someone updating the usergroups' journal permissions, as well as updating the journal settings.

This effectively recommitted the data to the DB, fixing the problem... I think. Perhaps someone can test it and see if it works?