thesiim

The error indicates that the room the booking was originally made does not exist anymore (most likely deleted). I will create a task to improve the registration schema update validation.

Hey
Just to be sure did you try refreshing the backend page?

• This reply was modified 3 weeks, 4 days ago by thesiim.

Yes it is by design. Sometimes payment processing takes some time to complete but sometimes its instant. There is already a task to make this payment landing page more customizable.

What you can do is inspect the error thrown in https://github.com/SiimKirjanen/seatreg/blob/master/php/payment/stripe/SeatregStripePayment.php#L58-L63
I did couple of tests locally and seems to be working fine. The error object should give some info what is happening.

Did you made any code changes? Might be the reason why Stripe webhook signature is failing.

Currently decimal prices are not supported. I cant remember the reason for the limitation. Needs to be investigated.

Hey, this needs to be investigated. In the meantime, you can try hiding it using custom styles found in the Registration Settings under the Custom Styles section.

No worries. Its good that people report issues…

Oh I see now. If you copy your registration then the room images seems to be broken.
Will create a task to fix this.

When creating a new room you should be able to add previously uploaded image as a background. The room image modal has “Previously uploaded images” section that displays uploaded images and there is a “Add to room background” action you can click. That will change/add the background image.

No they are separate =)
You can disable the legacy without affecting the new custom payments.

In settings you can turn off the legacy custom payment option and create a new one. Is that not working?

The first custom payment you have is using legacy custom payment that does not support payment icon.
I will create a task to add spacing between the icon and payment text.

Hey
Can you make some explanation screenshots of the problem? I don’t think I understand the issue.

Hey
I created a task to make the search case insensitive.