[Cliff]

I’m not familiar with metabox.io, but could you please provide your code snippet that saves the post data?

[Cliff]

I understand you’re frustrated, and we definitely understand Divi’s popularity. We even have a KB article about using it with our plugin: https://theeventscalendar.com/knowledgebase/divi-pagination-problems/

Testing on a desktop-width browser, I see your sidebar is set to a width of 20.875% from your Divi customizations, which means it’s only 219.094px in my specific browsing session.

Our widget’s CSS “fails gracefully” (if you want to call it that) in the case of a very narrow container width because its text wraps instead of being cut off.

So, here’s your current display on my computer: https://cl.ly/2j2e2h0s451z

You could add this CSS if you’d prefer the text to be cut off instead (I doubt it but am providing it for demonstration purposes):

.tribe-events-adv-list-widget .tribe-mini-calendar-event .list-dayname {
white-space: nowrap;
}

Or you could change the width of the date and info columns, like this, which is what I’m assuming you are wanting:

.tribe-events-adv-list-widget .tribe-mini-calendar-event .list-date {
width: 20%;
min-width: 40px;
}
.tribe-events-adv-list-widget .tribe-mini-calendar-event .list-info {
width: 73%;
min-width: 135px;
}

(Note that I did not provide the responsive / media query CSS that you may desire to fully implement this customization.)

To be clear, this is a customization not to Divi but to your implementation of Divi.

Please familiarize yourself with our Scope of Support / Terms to help avoid any future dissatisfaction due to our support limitations.

Finally, please let me know if there were other issues besides this widget’s day name display that you still would like assistance with.

[Cliff]

I appreciate your question and the desire to customize it for your use. However, we cannot provide such in-depth customization help, per our Scope of Support / Terms.

Since you said you already created another view, I assumed you had a template file you wanted to load at a specified URL. The suggestion I shared was how to add the link to the Tribe Bar’s view switcher.

You’ll need to know WordPress coding basics to leverage the filter I suggested. Additional coding might also be needed to accomplish your customization.

If you need some coding help, you may want to ask your developer or reference our documentation and list of known customizers.

[Cliff]

I’d first suggest looking to see if you can spot any console errors at the Attendees Report screen (if needed, you may reference our KB article Using Google Chrome Developer Tools).

If there isn’t anything obvious there, please enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages) and share any debug messages you see after reloading your Attendees Report screen.

Then, please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins and WooCommerce core) and see if that helps narrow down the cause of this.

[Cliff]

I’m glad to hear. Thanks for sharing with us and other users. Have a great weekend.

[Cliff]

I’d suggest confirming each with PayPal when you discuss your specific app’s credentials.

[Cliff]

Got it. I confirmed this is how this works currently.

I’ll mark this ticket as Pending Fix, which means this thread should receive a reply once the applicable fix has been released. I cannot guarantee when it will be fixed as it’s in the development team’s hands now. They need to assign it, code it, test it, and schedule it for release.

I apologize for this issue and appreciate your understanding and patience.

Here’s some CSS you could use to hide it:

a.tribe-community-tickets-payment-options-link {
display:none;
}

Please let me know if you have any follow-up questions on this topic.

[Cliff]

I’m glad to hear it! Have a great weekend.

[Cliff]

This reply is private.

[Cliff]

Thanks for the extra info. Could you share your slow/duplicate queries from Query Monitor while in Testing for Conflicts mode?

[Cliff]

Very glad to hear it!

Really appreciate the reminder for this weekend 😉

[Cliff]

Here’s our KB about minification plugins: https://theeventscalendar.com/knowledgebase/problems-with-minification/

Here’s some CSS to hide your sidebar only on the CE form page:

body.tribe_community_edit .four.columns {
display: none;
}

Please let me know if you have any follow-up questions on this topic.

 

[Cliff]

This reply is private.

[Cliff]

Hi, Lyoures.

Thanks for your detailed inquiry.

We actually have someone on the team who can read German; don’t pay to have it translated.

Please reference our Do you offer discounts for nonprofit organizations? help article and feel free to submit the application there if you’re interested.

[Cliff]

Hi, Lauren. Sorry you’re experiencing this.

I haven’t seen this reported like you’re describing, and it’s not currently a known issue so I’d suggest following these recommended troubleshooting steps for your own site:

There might be some new updates available. Could you please make sure all your Modern Tribe plugins (and WordPress core) are at their latest versions?

• Downloads / Version Numbers
• License Keys
• TEC Automatic Updates
• or TEC Manual Updates
• WordPress core updates

Once you verify you’re on the latest versions, please test to see if the issue is still happening for you.

If it is, please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this.

If it doesn’t, please enable WP_DEBUG and WP_DEBUG_LOG and share any debug messages you see while trying to replicate this issue and doing other things on your site relevant to this ticket.

If it is still happening in Testing for Conflicts mode, please send a screenshot of each instance of each of the duplicated Venue (including the URL to see the Post ID).

Let us know what you find out.

Thanks.

[Author]

Posts