Dirk

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 104 total)
  • Author
    Posts
  • Dirk
    Participant

    As extra info: reverting the Tickets Plus plugin to 4.0.1 resolved it. 🙂

    in reply to: Fatal errors attendees / sales report front end #1042481
    Dirk
    Participant

    Hi Brain,

    Thank you for the quick respons and resolve! It patched it up. 🙂

    Sales rapport on the front end is still only showing last couple transactions but I guess that’s still a work in progress?

    Thanks,
    Dirk

    in reply to: Bug report on front end edit event, sales report #1042463
    Dirk
    Participant

    Hi Josh,

    Yes, we always do that although we have to wait till late in the evening for such a test since it messes up the lay-out. After wordpress 4.4 we suddenly had very different issues with the community plugin which is posted and resolved here: https://theeventscalendar.com/support/forums/topic/fatal-errors-attendees-sales-report-front-end/

    So I guess you can close this thread. Unfortunatly the sales rapport is still only showing the last couple sales but I guess that’s still a work in progress?

    Thanks for the assistance,

    Dirk

    in reply to: Fatal errors attendees / sales report front end #1041879
    Dirk
    Participant

    My mistake, this did not resolve the problem. Still need a solution.

    Thanks!

    in reply to: Fatal errors attendees / sales report front end #1041731
    Dirk
    Participant

    We sorta patched it with this:

    // Include WP’s list table class
    if(!class_exists(‘WP_List_Table’)){
    require_once( ABSPATH . ‘wp-admin/includes/class-wp-screen.php’ );//added
    require_once( ABSPATH . ‘wp-admin/includes/screen.php’ );//added
    require_once( ABSPATH . ‘wp-admin/includes/class-wp-list-table.php’ );
    require_once( ABSPATH . ‘wp-admin/includes/template.php’ );
    }

    So it probably has something to do with WordPress 4.4
    What do your tests say?

    in reply to: Disable RSVP #1041724
    Dirk
    Participant

    Hi George,

    Thanks, that worked!

    I know the changes you made in the 4.0 overhaul are probably very usefull for many people. For us it has been a real struggle tho, haha! We didn’t really need the new functions and some of the old are broken.

    Maybe we’ll use the RSVP function in the future when we not how to rename ‘Woocommerce’ and or ‘RSVP’ differently since their both are not ‘logical’ names for the community members here.

    Thanks for this!

    in reply to: Bug report on front end edit event, sales report #1041669
    Dirk
    Participant

    This reply is private.

    • This reply was modified 10 years, 4 months ago by Dirk.
    • This reply was modified 10 years, 4 months ago by Dirk.
    in reply to: Disable QR codes #1041314
    Dirk
    Participant

    That worked, thanks!

    We have some serious issues since updating to 4.0 but that’s something for a different thread I think. 🙂

    in reply to: Bug report on front end edit event, sales report #1041199
    Dirk
    Participant

    This reply is private.

    in reply to: Disable RSVP #1041197
    Dirk
    Participant

    This reply is private.

    in reply to: Disable QR codes #1040284
    Dirk
    Participant

    Hi,

    Upon adding this to functions.php we got this error:
    Fatal error: Class ‘Tribe__Tickets_Plus_Main’ not found in /home/…/public_html/…/wp-content/…/functions.php on line 40

    Doing something wrong?

    Thanks

    in reply to: How does check-in work with QR codes #1038610
    Dirk
    Participant

    Follow-up:
    Is it indeed possible to remove QR-codes with:
    remove_action( ‘tribe_tickets_ticket_email_ticket_bottom’, array( Tribe__Tickets_Plus_Main::instance()->qr(), ‘inject_qr’ ) );?

    in reply to: How does check-in work with QR codes #1038608
    Dirk
    Participant

    Hi,

    Thank you for the answer! I’m glad it was not something on our side.

    We have some concerns on the QR-codes option tho and before we update to 4.x we would like to know how to disable QR-codes. But I think it’s somewhere on the forums already.

    The concerns are:
    – The check-in is a back-end solution while in the community options we set-up back-end block for everybody except admin. So when an event/ticket wants to use QR-codes they get redirected to the frontend without succesfull QR-code checking.

    – We were able to check-in the same QR code multiple times without an error warning like “This ticket has already been checked in”

    I hope 4.1 will further enhance the QR-code capabilities because, in our opinion, it is not very usefull this way.

    Thanks for all the continuous support tho!
    Dirk

    in reply to: How does check-in work with QR codes #1035581
    Dirk
    Participant

    Hi,

    I just downloaded the new 4.0 plugins and set it up on a test platform. The tickets do seem to spit out QR-codes. So what can they be use for at the moment?

    Thanks,

    Dirk

    in reply to: Bug report on front end edit event, sales report #1032717
    Dirk
    Participant

    This reply is private.

Viewing 15 posts - 46 through 60 (of 104 total)