Barry

Forum Replies Created

Viewing 15 posts - 436 through 450 (of 17,936 total)
  • Author
    Posts
  • Barry
    Member

    Hi Riley,

    You’re right – it is indeed connected to Filter Bar.

    As noted earlier we are aware of this issue and are hoping to release a fix shortly: please do stay tuned to our release announcements though we’ll also endeavor to post an update within this conversation.

    Also concerning is that this isn’t listed on your β€œknown issues”

    That’s right. As the text on that page notes, it doesn’t cover all known issues – just ones of a certain priority or that are impacting a certain percentage of users. In this case specifically, we chose not to add it.

    Again, a fix is in the works and should be with us before too long. Thanks again for your patience while we finalize our next release πŸ™‚

    Barry
    Member

    This reply is private.

    Barry
    Member

    I appreciate the note – thanks Andrea.

    Though there’s no perfect solution to this sort of issue, this exchange did at least help to trigger some work on additional ‘defensive measures’ to help protect ourselves and our users from similar situations in the future.

    So, though you had a bit of a rocky experience and are moving on in any case, I think this has at least helped to bring about a change which will result in a net improvement for our userbase. That to say, thanks for taking the time to flag this and good luck with your projects (and hopefully you will indeed be able to take a fresh look at our plugins at some future point) πŸ™‚

    Barry
    Member

    Sorry to hear that, Saif.

    We do have some restructuring of our Event Aggregator service in the works that might help here, but it’s hard to be certain that that will help, based on this information alone.

    Could I once again ask for a fresh database dump?

    Barry
    Member

    This reply is private.

    in reply to: Split Payments #1465352
    Barry
    Member

    Hi Colm,

    Thanks for reaching out πŸ™‚

    We don’t currently offer direct support for using Stripe with Community Tickets: though it should certainly be possible to let customers buy tickets using that or any other gateway supported by WooCommerce we do not currently have split payment for any gateways except PayPal Adaptive Payments.

    How do I know if I have a PayPal Adaptive Payments set up on my account?

    I’d recommend logging in to your PayPal account and, if in doubt, opening a support ticket with PayPal to ask if you have an approved adaptive payments account.

    The way the web developer set it up does not enable the seller to view the details of the purchasers in the backend of the site. When working correctly, should the seller be able to see this information?

    If an organizer adds tickets to events via a combination of Community Events and Community Tickets then no, they should not normally be able to login and view the attendee data in the backend/admin environment.

    However, they definitely should be able to view the attendee list for each event that they “own” (and that is facilitated via the frontend of the site).

    Does that help? Please don’t hesitate to let know if I can clarify anything else πŸ™‚

    Barry
    Member

    You’re welcome πŸ™‚

    Barry
    Member

    This reply is private.

    Barry
    Member

    Hi Andrea,

    We are happy to offer a refund within 30 days of purchase (and it looks like you are still within that window).

    Given the nature of the problem I think it is best if the theme developers resolve this and of course I can’t speak to how quickly that will happen, unfortunately, but perhaps you could press them on this point?

    Thanks!

    Barry
    Member

    Hi there, @dialogue99.

    Just wanted to confirm I was able to set up the theme and while setting things up to replicate this seems rather involved I can see what I believe to be the problem in the theme code, which is this sort of pattern:

    $wp_query = null;
    $wp_query = new WP_Query($args);

    The problem is that the first of those lines wipes out WordPress’s global query object completely, leading to problems like the one you documented above.

    The second line replaces it with a fresh query object, but what is often forgotten is that lots of code runs during the construction of the new query object and, until that process completes, code accessing the main $wp_query object will hit a wall.

    I’ll shoot a note to the theme author as you requested πŸ™‚

    in reply to: From Bad to WORSE: Event Aggregator Still Still not working #1461529
    Barry
    Member

    This reply is private.

    in reply to: Major Problems with Event Imports #1461366
    Barry
    Member

    This reply is private.

    Barry
    Member

    Gotcha – thanks! Will get back to you shortly πŸ™‚

    in reply to: Events do not show past February 2018 #1459052
    Barry
    Member

    WP Cron runs through wp-cron.php rather than admin-ajax.php, but yep I’m sure Pantheon’s team will be able to put this in place (or confirm if it already is) πŸ™‚

    in reply to: Disable ticket email (using Easy Digital Downloads) #1459046
    Barry
    Member

    Hi @artstream8401,

    If you have direct access via FTP or if your web hosting control panel offers some kind of file manager, perhaps you could create a new directory at wp-content/mu-plugins and then create a file called event-tickets-plus-customizations.php within that.

    In that file, start with an opening PHP tag <?php on the first line then follow with the line of code I shared above on the next line, ie:

    <?php
    add_filter( 'edd_email_ticket_receipt', '__return_false' );

    Does that work for you?

Viewing 15 posts - 436 through 450 (of 17,936 total)