Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Regular barcode instead of QR code | Event Espresso - Staging Server
Whilst it may be possible, you would need to customise the plugin to remove the QR code generator and slot in a barcode generator.
This really isnt advisable on two fronts.
Firstly it will be a lot of work to modify the plugins, including the API and mobile app (though that may not be an issue for you due to the barcode scanners). Plus there would be constant maintenance due to future changes to the plugins from our end.
Secondly the amount of data a traditional barcode can hold is nowhere near a QR code and subsequently this will mean a reduced amount of information on the barcode which may cause issues integrating it back in as currently the QR codes hold more than 128 chars.
We do not currently plan to produce a barcode friendly version of the ticketing system.
You’re more than welcome to try it, but please understand that we cannot support changing the ticketing add-on to output a barcode instead of a QR code.
Viewing 3 reply threads
The support post ‘Regular barcode instead of QR code’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.