okay- you made some real progress today! Thanks for all your efforts. Email me if you need anything webmaster at dodgeboard.com

Thanks, you've been a tremendous help.

I must say, it's pretty damned impressive what you guys have done with it, especially figuring it out so quickly. I'd like to think it's because I coded it with some high-level concepts in mind, but more likely, you're PHP gods. ;)

The installer's a +++++. What specific problems is it causing?

BTW, header duplication and problems will occur within the vbms_mail_message class. The API function you posted is just a wrapper to provide safe arguments for the class and to easily say "just send the message" without all the extra code.

post 127:

Filburt,

Can you package these changes so that the queries are properly executed?

Then use the files posted by Lionel on post 197 to put together a 3.6.0 beta release.

I have no idea how the phrasing works in vB 3.6, so I don't know even how to start fixing that one. The table prefixes should automagically be replaced when queries are run. It should add the settings and create the group as well.

If the whole process changed in 3.6 versus 3.5, then I don't know what to do. I have near-zero experience with 3.6.

(also don't have <oXygen/> installed right now)

You need to deal with that single line for phrasetype (database has changed from 3.54 to 3.60)

And need to make sure all settings are there (15 of them). Here are 3 screenshots of what the complete settings should be. Some of them, I 'borrowed' from the 3.07 version to manually install.

I also borrowed the code below navbar to display new emails from the 3.07 version

OK here is what I did

1-Imported the phrases directly from Filburt xml into english language

2-Did same thing for templates

replace new_ with your prefix

for settings you are on your own. My sql files have my autoincrements

working 3.60 version here

I think you mean "replace WDF_ with your own prefix"

If you look at the text files Lionel uploaded, you'll see:

I think he means to replace the new_product table line with your own prefix. Same with new_settinggroup and new_phrasetype in the corresponding files

Doh! Thats what I get for working on 2 things at once...