Ok, have done :)

After upgrading to current version, i get the follow error:

Parse error: parse error, unexpected T_PRIVATE, expecting ']' in /home/my604/public_html/forums/journal.php(564) : eval()'d code on line 188

Line 564 is an eval()-call for template JOURNAL.
Did you customize this Template?
If so, revert it.

I did revert the Template. Let me double check. Thanks.

Yes all the template are reverted back to default. What to do next? THanks

Still the same error (normally can't be)?
If so, send me an ACP account so I can take a look what's wrong

Ok.. I tried to paste the template in the XML into the JOURNAL template in ACP and I get the following error in the ACP:

"
Parse error: parse error, unexpected T_PRIVATE, expecting ']' in /home/my604/public_html/forums/includes/adminfunctions_template.php(3532) : eval()'d code on line 187

"

As said, send me an ACP login so I can take a look as smth. must be broken.

I'm also getting that same php error :(

Can you unistall this hack just fine now?

Seems one of the admins at my forum was able to fix the issue, but now the entries appear blank o_o

Seems you've missed the images/misc/music.gif file from the zip, Andreas?

Oops, and the updated includes/xml/bitfield_journalhack.xml file (can edit own comments).! ;)

There is some more gifs missing. ;)
buddy_journals & myjournal
But thats trivial. :)

Whats this fore O.K? Seems like i have missed any music options.
By the way, my journal works just fine. No errors at all.

I had this on a few templates

I fixed it by searching for this

"$journalinfo[private]=='1'"

and replaced it with

"$journalinfo['private']=='1'"

Might not be the right way to do it, but it sorted out the problems

Is there any way to get the journal read markers to update immediately rather than after a time period?

It seems that no matter how many times I read someone's journal the indicators stay the same colour for ages.

I think you'll find that they're actually included in the latest zip.. ;)


Beta 1 introduces a "now playing" feature for journal entries.

The Alpha 4 zip also had this, which has now been removed.. :)

@moonclamp
vBJournal currently doesn't have a real read-marking; this has to be implemented in future versions.

@Oblivion Knight
I've added the missing music.gif to the ZIP, as well as a new bitfield XML.
But not yours, as it would be incompatible with Alpha 1-3.

Everything seems to be working EXCEPT the links to "My Journal" in the navbar and also the link to "New Entry" on the Journal Links navbar.

These both seem to be associated with the "gotomyjournal" phrase.

I believe I did everything I was supposed to do, I reverted all the VBJournal templates, made all the necessary changes to the other templates, uploaded the new product, what did I miss?

*confused*

What did you mean?

I apologize, let me clarify. I downloaded the new zip file and followed all the instructions.

When you go to the journal index, everything works except for the "My Journal" option. For example, if you go here http://www.familycorner.com/forums/journal.php3 and log in with this test account I set up for you:

Username: TestUser
password: test

and create a journal. Then after that, use the drop down menu in the navbar to select "My Journal". Another spot is from the Journal Index page, there is a button below the latest entries that says "My Journal". That doesn't work either.

The last thing is just below the "My Journal" button, there's a nav drop down that says "Journal Links" and one of the options is "New Entry". That doesn't work either.

Server issue. vBJournal is written to use .php extension, you use .php3 extension which is not supported.

I just found another error. I had made a test entry in my journal before the upgrade along with several other entries. I decided to delete the test entry so I clicked the delete button which brought me to a page that asked if I was sure i wanted to delete it. When I said yes, it took me to a page can't be found error.

It worked fine before. :(

Dunno if it's just me, but as I said before, I get the following when viewing anyone's entries (see attachment):

I spoke with my server, and they said that the extension php3 are from legacy installs for backwards compatibility. I adjusted all the extensions to say php3, so this should not be problem because I have been running Vbulletin this way since 2001.

vBulletin does support different extensions, vBJournal does not - easy as that :)

@Omega Prime
Send me an ACP/FTP/phpMyAdmin login and i'll take a look, but it seems like your tables are empty (though I wonder why there are pagenavs then ...)

I understand what you are saying about not supporting php3, however, this worked fine yesterday before the upgrade. What are your comments on that?

There is no way older versions could have worked properly, except if you modified them (phrases, templates, PHP-Files).
If you did, it's up to you to get it working as this is not supported.

Ok I found it. Somehow my find/replace didn't complete, I had several .php extensions that had not been changed to .php3. Changed them all and it's working beautifully now!

Thank you for this, my members love it :)

Here's a question for you. Is there a way to list the new blog entries with the VB new posts? So when a member clicks on "New Posts" from the nav bar, can we work in the new blog entries also?

Just a thought :)

Kinda difficult. For the moment: Not possible.

Seems it was a template issue, so the journal works again :)

Greatest hack ever!

hey i have installed your vbjournal! its really great but there is a small bug. when people comment ( i think its when they click discuss) , only their usernames are shown, their comments can't be seen. do u know how i can fix this? thanks a lot!

Make sure that you are using vBulletin 3.5.1, vBJournal Beta 1 and that you don't have any vBJournal Templates customized.
If the problem still exists, send me an ACP login as I can't reproduce the problem on my board.

hm.. i have version alpha 3. where can i download the beta? i tried dling the zip file again , but its alpha

The ZIP is Beta 1, not Alpha 3!

you still have the script listed as 3.5.0 RC3, how well does this work with v3.5.1? I haven't installed it cause of the info above. aka version number .. although I'm looking forward to when you have it ready for the latest version.

Thanks for keeping this hack alive :D