Version: 1.0.2 Beta, by Andreas
Developer Last Online: Jan 2023
Version: 3.5.1
Rating:
Released: 09-16-2005
Last Update: 11-16-2005
Installs: 597
DB Changes Uses Plugins Template Edits
Additional Files Is in Beta Stage
No support by the author.
This is a Port of vB Journal by An-Net
A t t e n t i o n
This Hack is unsupported and incompatible with PHP 5.
You are herby advised to not use it.
If you do have this hack installed it is advised to use vBulletin Blog instead.
You can import current entries to vBulletin Blog via Impex and uninstall this hack afterwards.
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;
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.
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.
@Omega Prime
Seems like you are using customized journal Templates.
Please revert them.
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: