quadshot

This is now part of the Display Options Extension about to be released.

If you join the mailing list on opentickets.com you will get notified of any updates.

The suggestion has been added to our backlog and planned in future Extension releases. If you join the mailing list on opentickets.com you will get notified of any updates.

@jvolzer

Nice looking site.

We have verified that this is either a plugin conflict, a conflict with the newest version of WooCommerce (or perhaps both).

This has been filed and we’re hoping to have a new version of OTCE very soon.

@jvolzer I see the issue:

This image is very vertically tall, and there isn’t that much real estate on the ticket.

This one is 174×426.

The space on the ticket is about 200×100 for the Venue and Event respectively, so I would suggest trying an image that size.

Basically what’s happening is that the tall image is being squished into a rectangle.

If you try that size, the image will fit nicely.

@freshground

your site appears live and I just want to verify that your issue is resolved. If it is not, we do see the live site and have a login.

If you still need help, post here and we’ll be notified.

Best,

Buford
Support

@backbeatjohn The IP address should have no bearing on the QR code.

I see you have another thread with this same post. Could you perhaps provide a WP login so we can take a look? if you do feel ok with that, email it to [email protected]

Thank you

Marking this resolved here since this issue is already active in the Service Desk.

@mlbtp

Patrice,

Can you please help us:

Paste the ‘System Status’ from the ‘OpenTickets’ menu in the Dashboard

Optional: Can you give us a login to take a look? We’ve never had this bug reported. If you do create one, please email it to [email protected]

@robdoar

We’ve not heard back so marking the issue as resolved. Please re-open or make a new ticket if you need more help.

@backbeatjohn

Can you please paste your ‘System Status’ from the ‘OpenTickets’ menu item in the Dashboard.

@jvolzer can you provide a link directly to that image? We have never seen that on a ticket.

I see you had another issue open, so if you didn’t already place the System Status from the OpenTickets menu item in the Dashboard, please paste that here and we can take a look.

@petervandoorn @jvolzer

If would help if we had the System Status message from ‘OpenTickets -> System Status’ on your Dashboard.

That might help identify the issue.

@chelys please email [email protected]. since you are a paying customer you can access our online support desk. We’ll send an invite. (We can’t tell by the username on www.remarpro.com which purchase was yours)

Marking this resolved on the www.remarpro.com forums.

Hello @blankartist

The reason we have event areas as mandatory is that we decided to build a platform that was flexible to all needs.

For example, imagine you are running events at a hotel. You have one Venue (Hotel) but several event areas (conference room A, conference room B & Main Ballroom). OTCE allows for any scenario of Venues (Physical Places) and Areas (locations within the physical places).

Also, people might want different images on their tickets for each area. In vegas we have the ‘Treasure Island’ and ‘Mandalay Bay’ areas in one Convention Center.

Regarding the inventory in the WooCommerce Product page, that wouldn’t work since you might have more than one show for that ticket type. For example, you could have a $10 price for Adult Ticket during the week and $15 price on weekends for the same ‘Ticket’. (We have a multiprice Extension that does this, but to allow all the prices/seating arrangements we have to have inventory in Event.)

Also, some people run a ‘blackbox’ for an Event Area, so they might allow 100 in one show (to allow tables for a dinner theater) and 150 for another (with SRO for a concert. Therefore we have to abstract the inventory to the actual Event.

In your situation it is one extra hoop to setup for a one-time event, but we tried to make this flexible for everyone.

I hope this helps explain the design behind it and sorry it is more complex for a one-time event.

Please let us know if you have any other questions or suggestions.

@creasechris I’m just pinging you to let you know this is still on our radar. QA is going through various scenarios to attempt to replicate the check-in issue.