ShaneJenkins

Heath, I have contacted the support crew at WebCentral, they have an open ticket that it appears someone is looking at, hopefully we’ll have some answers soon.

Try adding or updating a plugin and let me know if you get messages.

Good luck

Did you change the username to vs50261_1_dbo?

You have two users they are the same except one had _dbo at the end and it’s the only one to access the db with

You DB_NAME looks right.

Dont use local host for the DB_HOST, I have bne2-0001my.server-sql.com

And the DB_user is the username that ends with _dbo, so for you it’s probably vs50261_1_dbo.

Like Swanson says, go ahead and change your password.

Let me know how you get on.

Ah it looks like you have had as much joy with their support staff and massive waits in queue as I have.

There were two things that Web Central had to do to get WordPress to a position where it could be installed.

1. Upgrade their standard PHP
2. Tell me that I needed to add on MySQL

Have you added MySQL?

After that I added the

* DB name
* DB user
* DB password
* DB host

And it installed and it does work, but it’s not something I want to leave with a client when there are so many error messages.

If you get yours working let me know if you get the same errors.

It looks like both systems use WP native user registration, which explains the clash. I have disabled the standard EM registration form and forced people to register using the Your Members registration form, it’s working fine.

Ok the JS conflict problem is gone now, but I still have the problem with the form, any suggestions?

Looks like its running jQuery 1.6.4…might have to check the theme and see what it’s loading.
Thanks again

Thanks for the tip Marcus, I’m at WP 3.3.1 but will check the jQuery file for sure

Oh, I see that now, fun. I’ll have to work out what’s causing the conflict, but I cant see it causing the issue that I see on the booking form.

https://shanejenkins.com.au/eldred/events/the-hospitality-supervisor-2/

I just had another look, I thought it’s possibly because have user registrations for bookings. So it’s required to register the user in the first instance. But then I disabled through the No-User Booking mode and it didnt make any difference.