<< gk clicks install!! :D


ack!! phrases?? I want to update this for another language!! :(

It's not yet fully phrased, but I am in the process of replacing all hardcoded Text with Phrases.
Will be fully phrased done in Beta 1 at least.

schwwwweet! :D thanks. that's a HUGE deal for many of us I would imagine.

great work so far though anyway. :)

Oops ;

<a href="http://bugs.kirbydemos.ath.cx/view.php?id=15" target="_blank">Known</a> and fixed already.
A new release should be ready today.

i am geting this when i edit vBJournal Premissions

any ideas on this one

I just upgrade my site from 3.0.8 to 3.5 rc 3

Did you upload the Bitfield XML before you imported the Product XML?
Anyway, admincp/index.php?do=buildbitfields should fix the problem.

thank you very much sir. workd like a charm.. one of these days i will get the hang of this stuff..

:banana:

Where does it tell you to do that ?

[high]* Andreas slaps Paul M around a bit with a large trout
[/high]
You know exactly that Bitfield XMLs always have to be uploaded before product import ;)

[high]* Paul M slaps KirbyDE back with a very large trout
[/high]
Yes, that's not the point :p Not everyone who installs it will know .....

Any more slapping and u 2 will need to get a room............lol

Updated. Details see first post.

So if we're upgrading, run the query, then do what with the original product xml? Delete it? Uninstall it? Or overwrite?

edit: n/m... uninstall deletes existing journals right? Unfortunately I had to uninstall, because I didn't set it to allow overwrite the first time I uploaded the XML.

Yes, uninstall deletes existing data.
If you don't tick overwrite that's not a problem as it will just do nothing then.
Just do it again and make sure overwrite is ticked.

Latest version working on RC3 with no issues. Thanks for the update Kirby! :)

A XSS Vulnerbilitie has been discovered in vB Journal Versions prior 1.0.2 Alpha 3.
In order to keep your site safe it is recommended to update immediately.

Fix for vB Journal 1.0.1 (vBulletin 3.0)
FIND
REPLACE

Where is the code?

Obviously journal.php ;)

That's where I initially thought but I don't have that code.

Are you using Version 1.0.1 on vBulletin 3.0.x?

No, didn't realise the 3.0.X series was being discussed in the vB3.5 extensions forum. :D

Oops...

I just included this in the warning as the 3.0 Version is also affected.
For vBulletin 3.5, just upgrade to the latest Version of this Hack.

Good, I should be sorted then. :)

Is it just that one line in journal.php that is affected?

So to upgrade do we just need to upload the new journal.php or make the change in the email to correct the bug?

Just overwrite the existing File if you are using the vBulletin 3.5 Version - or apply the fix if you are using the vBulletin 3.0 Version.

Dunno if it's just me, but after the upgrade to the current build, I'm getting issues with a few users having blank comments. It shows their name and the time they made their comment, but that's about it :(

(Note that it can't be permission issues as I've already checked those)

Hmm ... how can I reproduce this effect?

Economics is like jacks: If on the side before weakness down falls, the other one slams also on the ass.

So True

@Omega Prime
Seems like you are using customized journal Templates.
Please revert them.

I get the following SQL error when I try to edit Journal Buddies;

Invalid SQL:

SELECT userid, username FROM user
WHERE userid IN ()
ORDER BY username;

MySQL Error : You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ')
ORDER BY username' at line 2
Error Number : 1064
(etc)
Classname : vb_database

Using latest version on vB3.5 RC3. Have not customised the journal in any way but have been upgrading it since about Alpha 1 Build 1.

I thought I'd take the opportunity to show a few cosmetic issues I've come across where the system doesn't go seemlessly with my styles (see attachments).
1) Wrong text colour in dropdown.
2) USERCP_SHELL appears to be using the wrong Alt colour;

Normally this can't happen.
Try
[sql]update usertextfield set jbuddylist='' where jbuddylist=' '[/sql]

Query done. "Affected Rows: 0". Actually I was a little apprehensive about posting on your bugtracker because I wasn't sure it was a bug. But I'll continue this there if you like.

Hmm, then I don't know how this could happen.

Try editing Plugin vBJournal: Edit jBuddylist, change
to

Still getting the same thing I'm afraid. I'll open the case on your bugtracker, but first I'll try uninstalling/reinstalling from scratch.

EDIT: Uninstalling results in this fatal error: Fatal error: Call to undefined function: fetch_table_info() in /home/root/to/plugin.php(994) : eval()'d code on line 10

So.. guess I'll have to make the thread after all.

I really wanna know who wrote vB_Database_Alter ... that class doesn't really seem to fit with vB Code standards ;)

As for the buddylist problem: I can't reproduce this effect without intentionally putting corrupted data into the database. But even then the above code prevents the error.

You should also keep in mind that uninstalling deletes all existing journal data.

This looks good. Will it work on RC2 and are there any screenshots?

Thank you. :)

Will not work on RC2.
Currently there are no screenshots, but you can take a look here

Templates have been reverted, but since they're not vB defaults, they're just erased. The reason why it seemed that I customized it was that I first added the journal back in Sept. 2004 and I guess they haven't been overwritten since the recent 3.5 port of the journal.

At any rate, it's as I noted before with some users showing up with blank comments, while others appear fine :ermm: