Forum Replies Created

Viewing 15 replies - 31 through 45 (of 318 total)
  • Plugin Support Patrick

    (@paddyam)

    Hi @dmikra,

    Thanks for getting in touch.

    To control the space between the events, please use the following the following snippet.

    .sugar-calendar-event-list-block .sugar-calendar-event-list-block__base-container .sugar-calendar-event-list-block__listview {
    gap: 10px;
    }

    Note: You can adjust the value to increase of decrease the spacing.

    I hope this helps.

    Plugin Support Patrick

    (@paddyam)

    Hi @udayraj,

    We received an update from the dev team and yes, the plugin should work fine with PHP 8.4

    Kind regards.

    Patrick

    (@paddyam)

    Hi @dynamek,

    Thank you for sharing your perspective, we truly appreciate the feedback. You’ve raised an excellent point about how roles versus capabilities are presented, and I agree that having role‑based options would be very helpful.

    I’ve added this as a feature request to our list for consideration as we plan the plugin’s roadmap.

    We’re always looking for ways to improve the experience, and input like yours goes a long way in shaping future enhancements.

    Thanks again for helping us make the plugin better!

    Plugin Support Patrick

    (@paddyam)

    Hi @congchungquan3,

    Thanks for the rating and as a quick follow-up to your message and to make sure we can assist you properly with setting up email for your website, could you please open a support request from our contact form and include all the details (such as your email provider, current configuration, and any error messages you’re seeing)?

    We look forward to your support thread so we can help you step by step!

    Hi @dynamek,

    Thanks for getting back to us, and apologies if this has been a bit confusing. To clarify: options such as Super Admin, Admin, Editor, and so on are WordPress user roles.

    On the other hand, the list you’re seeing represents user capabilities. Capabilities are more granular than roles, for example, they define specific actions a user can perform within WordPress.

    From the list you shared, it looks like you also have some custom capabilities, such as Rank Math 404 Monitor.

    I hope this clears things up!

    Hi @dynamek,

    Thanks so much for reaching out.

    The items you’re seeing in that field are WordPress capabilities, not user roles. To control who can view submission data, you’ll want to select the specific capability a user must have. WordPress provides a detailed breakdown of how roles and capabilities work here: https://wordpress.org/documentation/article/roles-and-capabilities/

    For example, Administrators have the manage_options capability by default, so any role, built‑in or custom, that includes that capability will automatically have access to the data.

    I hope this helps clarify things, and I’m here if you need anything else.

    Plugin Support Patrick

    (@paddyam)

    Hi @babyewok,

    Glad to hear you were able to track down the conflict and get it resolved!

    Thanks for sharing the details, this is really helpful for others who might run into the same issue and I’ll be I’ll be sure to share this with the team for further discussion and consideration on how we can make this even better. In the meantime, if something else comes up, don’t hesitate to write back, I’m happy to help!

    Cheers!

    Plugin Support Patrick

    (@paddyam)

    Hi @pavefe,

    Thank you so much for the thoughtful feedback and kind words about our support team, we really appreciate it! We’re always working to enhance the experience and make the plugin easier to configure and customize. If you ever run into any issues or have suggestions, please don’t hesitate to reach out to us through support. We’re always happy to help and value your input.

    Kind regards.

    Plugin Support Patrick

    (@paddyam)

    Hi @babyewok,

    Thanks for getting in touch, and I’m sorry to hear about the trouble you’ve run into.

    To confirm, the checkout should work as expected and I’m unable to replicate this on my tests, though it’s possible this is related to a JavaScript error on the site. Could you please share a sample public link where the event is set up so I can take a closer look?

    In the meantime, it would be helpful to check the browser console for any errors being reported, as these could point directly to the issue.

    I look forward to your reply!

    Plugin Support Patrick

    (@paddyam)

    Hi @edgranger,

    I’m thrilled to hear you managed to get this working!

    We also really appreciate the kind words, and if anything else comes up, we’ll be happy to help.

    Plugin Support Patrick

    (@paddyam)

    Hi @revcoincidence,

    Thanks for your patience while we looked into this.

    I received an update from our development team; they were able to confirm the issue and have applied a fix that will be included in the next release.

    In the meantime, you can resolve the issue by applying the following snippet to your site:

    function sce_fix_event_ticketing_btn( $button_template, $event_obj ) {

    // Get the current ticket dates.
    $tz = wp_timezone();
    $start = new DateTime( $event_obj->start, $tz );
    $today = new DateTime( 'now', $tz );

    // We don't show the button if the event already started.
    if ( $today > $start ) {
    return '';
    }

    if ( function_exists( '\Sugar_Calendar\AddOn\Ticketing\Common\Functions\get_available_tickets' ) ) {
    $limit_capacity = absint( get_event_meta( $event_obj->id, 'ticket_limit_capacity', true ) );
    $available = \Sugar_Calendar\AddOn\Ticketing\Common\Functions\get_available_tickets( $event_obj->id );

    // We don't show the button if the event has no tickets available.
    if ( $limit_capacity && $available <= 0 ) {
    return '';
    }
    }

    return $button_template;
    }

    add_filter(
    'sugar_calendar_add_on_ticketing_frontend_loader_single_event_buy_now_button_template',
    'sce_fix_event_ticketing_btn',
    1000,
    2
    );

    function sce_disable_purchase_sold_out_events( $checkout ) {

    if (
    empty( $_POST ) ||
    empty( $_POST['sc_et_quantity'] ) ||
    empty( $_POST['sc_et_event_id'] ) ||
    ! function_exists( '\Sugar_Calendar\AddOn\Ticketing\Common\Functions\get_available_tickets' )
    ) {
    return;
    }

    $event_id = absint( $_POST['sc_et_event_id'] );
    $qty = absint( $_POST['sc_et_quantity'] );
    $limit_capacity = absint( get_event_meta( $event_id, 'ticket_limit_capacity', true ) );
    $available = \Sugar_Calendar\AddOn\Ticketing\Common\Functions\get_available_tickets( $event_id );

    if ( $limit_capacity ) {
    if ( $available <= 0 ) {
    $checkout->add_error( 'sold_out', sprintf( esc_html__( 'No more tickets available', 'sugar-calendar-lite' ), $available ), '#sc-event-ticketing-modal-attendee-fieldset' );
    } else if ( $qty > $available ) {
    /* translators: %d: number of available tickets. */
    $checkout->add_error( 'insufficient_quantity', sprintf( esc_html__( 'Only %d tickets are available. Please reduce your purchase quantity.', 'sugar-calendar-lite' ), $available ), '#sc-event-ticketing-modal-attendee-fieldset' );
    }
    }
    }
    add_action( 'sc_et_checkout_validate_data', 'sce_disable_purchase_sold_out_events', 1000 );

    Thanks again, and please don’t hesitate to reach out if you have any further questions.

    Plugin Support Patrick

    (@paddyam)

    Hi @revcoincidence,

    Thanks for sharing the screenshots and more details on the setup.

    Please allow me to check in with our dev team to run this scenario through testing and confirm whether the behavior you’re seeing is related to caching or something else, and I’ll be in touch with an update.

    Thanks, and in the meantime, please feel free to let me know if you have any questions.

    Plugin Support Patrick

    (@paddyam)

    Hi @revcoincidence,

    Thanks for reaching out, and I’m sorry to hear about the trouble you experienced. I ran a few tests with ticket limits on my end, and everything appears to be working as expected.

    To better understand what might have happened, could you please share more details about how you had things set up? A screenshot of the event settings would be especially helpful. It would also help to know if your site uses any caching (plugin or server-side), as that can sometimes affect ticket availability displays.

    Additionally, when the tickets were purchased, was it a case where 9 out of 10 tickets were already sold and the last order included 3 tickets at once? Or were all tickets purchased individually? These details will give us more insight into whether the issue was related to how the limits were applied during checkout.

    Thanks again, and I look forward to your update.

    Plugin Support Patrick

    (@paddyam)

    Hi @zlong64,

    Thanks for getting in touch and sorry to hear about the challenge.

    If the From email truly matches your verified sender identity, then something else in WordPress may be overriding it before SendGrid receives the message. Please check for any other plugins or custom code that might be hooking into the sending process and changing the From address.

    You can test by disabling other plugins temporarily and sending again to confirm

    Hope this helps.

    Plugin Support Patrick

    (@paddyam)

    Hi @passerbliss,

    Thanks for writing back and for the update.

    Since we’ve tested Sugar Calendar Lite on WordPress.com and haven’t been able to replicate the installation error, it looks like something specific to your account or hosting environment may be preventing the plugin from installing.

    Because this seems tied to the way your WordPress.com Business plan is handling plugin installs, the best next step would be to loop in the WordPress.com support team directly. They’ll have visibility into any account‑level restrictions or configuration issues that we don’t have access to, and should be able to provide more targeted guidance.

    Thanks again for your patience, and I hope this helps point you in the right direction.

Viewing 15 replies - 31 through 45 (of 318 total)