vBJournal for vBulletin 3.5

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.

[poolking]

Originally Posted by zajako

i guessed that, I dont see anything in the admin cp about it. Not in the options or anywhere else.

Have you read the documentation about 3.5.x? That would be the best place to start, look for the section dedicated to the plug-in system.

[Chadi]

How do I change the dark gray color in the journal comment list (see attached) to my alt1 color (the light blue area you see)?

[dethfire]

how do you upgrade to beta 2? ah crap, I uninstalled the product to install the new upgrade and it deleted all the journals! Now I gotta pay $20 to get the server dudes to restore the tables

[Paul M]

Originally Posted by dethfire

how do you upgrade to beta 2? ah crap, I uninstalled the product to install the new upgrade and it deleted all the journals!

Yes. I think that's extremely bad practice, the uninstall code should not remove tables until it's the release version.

[Andreas]

The uninstall code should always remove all data belonging to the hack, this is what uninstall codes are for

[dethfire]

Originally Posted by Andreas

The uninstall code should always remove all data belonging to the hack, this is what uninstall codes are for

I was unaware there was one, I suppose I'm still in 3.0x mode. I thought it would just uninstall the plugins. Anyway, to upgrade do you just overwrite the files and overwrite the product? If yes, it seems easy and obvious, but you still shouldn't make people guess what to do.

[Paul M]

Originally Posted by Andreas

The uninstall code should always remove all data belonging to the hack, this is what uninstall codes are for

Not in pre release versions where you are releasing new versions all the while and therefore people will (are expected to) uninstall/reinstall. The uninstall code is for people who no longer want the hack. Deleting the tables of people who are testing your hack is a very poor thing to do and is one reason I no longer test this. I posted the fact very early on in the thread but nothing changed so I stopped using it. Trashing my tables is not something I appreciate.


(btw, as a seperate issue - I personally don't see the need to ever remove tables as part of an automatic uninstall, they don't do any harm if left, and people can make up their own minds to remove them if they want).

[Omega Prime]

Stupid question, but has anything changed with the journal? What I mean is that I noticed it shows that the last update was on the 20th, and yet I don't see any changelog for a beta 2...=/

[Andreas]

@dethfire
Yes, overwrite and import te product XML is the standard procedure to update hacks.

@Paul M
Do you also prefer to manually remove registry entries?
Uninstall shoul clean up everything, so the board & database is in the same state as before the installation.
Anyway, this Hack could also be tagged "Final" (as there are no big issues whatsoever), so discussing about not having uninstall-codes for "pre-release versions" doesn't make much sense.

@Omega Prime
You won't see Beta 2 for a while, I just updated the laguage packs.

[Paul M]

Originally Posted by Andreas

@Paul M
Do you also prefer to manually remove registry entries?

Removing registry entries does not lose loads of data. No comparison really.

Originally Posted by Andreas

Anyway, this Hack could also be tagged "Final" (as there are no big issues whatsoever), so discussing about not having uninstall-codes for "pre-release versions" doesn't make much sense.

Well change it then.