I am glad to see you back.

I'd suggest not messing with the editor until its properly supported in vb4.

How do I go about upgrading from vB3 lite to vB4 pro?

Over 5k uploads that I need to keep. :)

Will this work with 4.2.0 pl3?

(I know you posted 4.2.1, I hafta ask as I wont be upgrading to 4.2.1 anytime soon)

@Reece^B: Back up your gallery database tables and images directory then follow the instructions in the readme file to upgrade from lite to pro. Don't of course overwrite your images directory!! Set the config file, leave the prefix file as blank, and FTP all the stuff over (except the images directory or it'll overwrite your current one) and then import the XML file allowing overwrite. The upgrade will change the database tables but won't mess with the images themselves.

@smirkley: Good question. I don't have that version installed to test. Last version I played with before 4.2.1 was 4.0.0 and that was before the inclusion of the CKEditor. My guess is that it'll install just fine (you might need to edit the XML file and remove the dependency though).

Thanks for sharing your superb product..

Some minor problems showing,as in duplicate titles,description fields when uploading.

Receiving the following error after install:
Also, I haven't made the vba template modifications yet, but the vbadbanced CMPS front page is completely blank and only shows if I disable your mod. :(

i got something like this to that's why i had to uninstall the mod

@skol: That looks to be from double entries in the photoplog_customfields database table. Do you remember what you did right beofre that occurred? If you post the content of the photoplog_customfields table, I can tell you what rows to remove (or you can figure it out by looking where the doubles are based on catid in that table).


@angeljs and @davidg: If you receive an error like this:
Update: I thought that (a) you didn't FTP all the PhotoPlog files to the server or (b) you FTPed them to the wrong place, but I received a PM with a clue, sorry, I'll look into this.

@angeljs and @davidg: Please see "How to upgrade from PhotoPlog Pro v.2.1.5 to PhotoPlog Pro v.2.1.6?" in the release post to take care of the problem you experienced. Sorry.

If anyone else has a problem, just let me know. It is likely something minor that can be easily fixed. For PhotoPlog Pro v.2.1.5 on vB 4.2.1 I moved stuff around b/c I got sick of waiting and waiting for the XML import, but I accidentally introduced a bug that I didn't come across in my tests. Said bug is now fixed in PhotoPlog Pro v.2.1.6 so thanks for letting me know.

Hope you enjoy PhotoPlog. :up:

I wish this was part of standard vbulletin .... great product!!