Bug in new version 1.6.20 – no booking possible

Oh, I regret you`re right. There might be a problem on both (production and preproduction) databases. I found that since 10th July there is no booking id recorded in eme_payments. Ups… althouh bookings work with V1.6.14. Confusing!

Here are the structure of the both tables:
eme_payment
id int(11) Auto-Inkrement
creation_date_gmt datetime [0000-00-00 00:00:00]
booking_ids text
random_id tinytext

eme_booking
booking_id mediumint(9) Auto-Inkrement
event_id mediumint(9)
person_id mediumint(9)
booking_seats mediumint(9)
booking_seats_mp varchar(250) NULL
booking_approved tinyint(1) NULL [0]
booking_comment text NULL
booking_price text NULL
creation_date datetime [0000-00-00 00:00:00]
creation_date_gmt datetime [0000-00-00 00:00:00]
modif_date datetime [0000-00-00 00:00:00]
modif_date_gmt datetime [0000-00-00 00:00:00]
booking_payed tinyint(1) NULL [0]
transfer_nbr_be97 varchar(20) NULL
wp_id bigint(20) unsigned NULL
lang varchar(10) NULL []
ip varchar(250) NULL []
discount tinytext NULL
discountid int(11) NULL [0]
dgroupid int(11) NULL [0]

Do you have an idea, why the booking id is no longer recorded or how to fix that issue.

Are these all eme tables?
eme_bookings
eme_categories
eme_dgroups
eme_discounts
eme_events
eme_fieldtypes
eme_formfields
eme_holidays
eme_locations
eme_payments
eme_people
eme_recurrence
eme_templates

Ok, it seems indeed your db is not up-to-date, probably because the user doesn’t (or didn’t) have the needed database rights to add/edit/remove tables.
So:
– make sure the user has the needed mysql rights
– go into the wordpress db, table wp_options, and set the value of the row with option_name=eme_version to 95
– disable/enable EME plugin

That should force a re-adaptation of your mysql tables then.

Okay, rights are checked and ok. But eme_version is already set zo 95
Also did an enable/disable, but can`t see any effekt. eme_version stays on 95 after enable/disable eme plugin. Is that correct?

eme_version should go up to 103 when going to the new version. If not, it means something is seriously wrong in the db … check your webserver logfiles for issues (and your mysql logfiles).
Are you using multisite (not that it matters, should work just fine)? Are you checking the correct database tables?

ok, after setting eme_version = 95 and updating plugin the eme_version is indeed 103. But the problem still exists.

I tried on preproduction to delete entries from eme_payment without booking id and on eme_booking which seems to belong together. Didn`t work. Maybe there is an other dependency?

I am not using multisite and sure working on the correct tables. ??

One idea: Could I export all relevant table data without eme_booking and eme_payment entries, delete plugin, and inserting all data again? Or would that lead into a inconsistency?

Now that the eme_version is 103, can you show the 2 table schemes again?

Sure ??

eme_payments
id int(11) Nein
creation_date_gmt datetime Nein 0000-00-00 00:00:00
booking_ids text Nein
random_id tinytext Nein

eme_booking
booking_id mediumint(9) Nein
event_id mediumint(9) Nein
person_id mediumint(9) Nein
booking_seats mediumint(9) Nein
booking_seats_mp varchar(250) Ja NULL
booking_approved tinyint(1) Ja 0
booking_comment text Ja NULL
booking_price text Ja NULL
creation_date datetime Nein 0000-00-00 00:00:00
creation_date_gmt datetime Nein 0000-00-00 00:00:00
modif_date datetime Nein 0000-00-00 00:00:00
modif_date_gmt datetime Nein 0000-00-00 00:00:00
booking_payed tinyint(1) Ja 0
transfer_nbr_be97 varchar(20) Ja NULL
wp_id bigint(20) Ja NULL
lang varchar(10) Ja
ip varchar(250) Ja
discount tinytext Ja NULL
discountid int(11) Ja 0
dgroupid int(11)

Ok, I see again something here …
Your eme_bookings table is missing a column called payment_id, that was added in version 1.6.13. So you had problems in the past in fact ??

So change the version in the options table to 89 please (the db-version in 1.6.12) and then disable/enable the new version.

Huch?! Okay, I gave it a try and tada… this is the new structure:

eme_booking
id int(11) Nein
creation_date_gmt datetime Nein 0000-00-00 00:00:00
random_id tinytext Nein

eme_payment

Spalte

Typ

Null

Standard

Verweise

Kommentare

booking_id mediumint(9) Nein
event_id mediumint(9) Nein
person_id mediumint(9) Nein
booking_seats mediumint(9) Nein
booking_seats_mp varchar(250) Ja NULL
booking_approved tinyint(1) Ja 0
booking_comment text Ja NULL
booking_price text Ja NULL
creation_date datetime Nein 0000-00-00 00:00:00
creation_date_gmt datetime Nein 0000-00-00 00:00:00
modif_date datetime Nein 0000-00-00 00:00:00
modif_date_gmt datetime Nein 0000-00-00 00:00:00
booking_payed tinyint(1) Ja 0
transfer_nbr_be97 varchar(20) Ja NULL
wp_id bigint(20) Ja NULL
lang varchar(10) Ja
ip varchar(250) Ja
discount tinytext Ja NULL
discountid int(11) Ja 0
dgroupid int(11) Ja 0
payment_id mediumint(9) Ja NULL

If this is fine, I′ld like to implement it on production. ??
The booking is recorded correctly with success message on preproduction right now.

If it works now, go ahead ??

Franky, you are the best!!! Thank you so much! Now everything works perfect again. THANK YOU!!!

You’re welcome. Glad to hear it works now!