fedata

We did not here back from you. Anything we can help you with?

We have tested the download of orders and tickets with umlaut names and it works fine.

https://ibb.co/xSSr73M7

https://ibb.co/gL7LBVv7

Could it be that this where old entries which are still stored in the wrong format? The patch yesterday was only valid for new entries. Any old entries can easily be corrected with a MySql ‘UPDATE replace ‘ statement on the “qrcodes” table.

Please let us know.

Thank you for your kind words. Please consider leaving a review.

Version 2.2.3 is now available.

https://ibb.co/5hHfYdF

• This reply was modified 1 month, 2 weeks ago by fedata.
• This reply was modified 1 month, 2 weeks ago by fedata.

Thank you for pointing us in the right direction. We have found the problem and will release a plugin update either today or tomorrow.

Thx for using our plugin. We did some testing with an orderform and via the admin add order interface and with both methods the umlaut is shown/printed correctly.

You should check with phpadmin if the database tables for the Fast Events plugin have the right ‘Collation’ it has to be ‘utf8mb4_unicode_520_ci‘.

If not, check your WordPress wp-config.php and change or add the following entries:

/** Database charset to use in creating database tables. */
define( 'DB_CHARSET', 'utf8mb4' );

/** The database collate type. Don't change this if in doubt. */
define( 'DB_COLLATE', '' );

• This reply was modified 1 month, 2 weeks ago by fedata.

Thx for using our plugin. There is no such thing as activating the plugin. Do you mean installing and using the “Management interface”? See https://docs.fast-events.eu/en/latest/apps/admin.html#administrator-accounts

It can only be istalled by an WordPress admin account and used by an admin account. For any other regular WordPress account. Read this section https://docs.fast-events.eu/en/latest/apps/admin.html#server-accounts

If the 403 is in another part of the plugin, please specify the url and the WordPress account role (admin, regular, …) you are using and we will look into this.

You can correct the double counts by going directly to the events table and update the ‘sold’ field accordingly.

Thanks for pointing out the shortcode spelling issue. We have released an updated version.

Enjoy your events.

Thx for the file. The problem has been identified. You made a small configuration error in the “Stock” screen of the “Basic settings”. You have specified the event itself as a linked event. In your case, you should not use linked events. Select “No connected event” from the dropdown field.

We will issue a warning in the next patch release (2.2.1) if you use the exact same event as a linked event.

See docs for linked events

You can use this temp emailadress: [email protected]

We tested an identical environment and it worked fine.

To see what is actually going on, the first step is to look at the contents of the events MySql table. Assuming you have access to the backend MySql database, you can do an export of the “fe_events” table using PhpMyAdmin and send us this file.

If you do not have access to the MySql backend, please use the “Tools” menu and “Export events” to export all three events and send the zip-file.

I trust you are on the latest version of the pluging (2.2.0) and FE Admin (4.2.0).

Please post screenshots from the tickets sold overview, the event details and the details of every ticket type.

With the 2.0 release still to become available this year, we looked at what we will do in 2024.

A number of veteran users from the past already spoke to us about enabling ticket personalisation.
We have therefore decided to include this functionality in the 2.1 release. It will be implemented as follows: the order form will be limited to name and email address. When the user wants to download the tickets, they will be asked to personalise each ticket after which either all tickets can be downloaded or individual tickets.

Personalisation is done based on all input fields defined for the event. The number of fields will be limited, possibly 6 or 8, because we want to be able to print everything in the qrcode block.

Sorry for the delay, email alerts were not sent.

See this link for the answer: https://docs.fast-events.eu/en/latest/getting-started/overview.html#order-pages

Answered in private email