[George]

Hi @tanyazailer

We unfortunately are not available for hire for such projects and the plugins are not compatible at this time. 🙁

I’m sorry to bear the bad news!

If you deeply want to hire someone to help you build out these features, your best bet is to hire a professional developer to write the code for you.

We have a list of great developers here → http://m.tri.be/18k1 (and have no affiliation with any of these folks—they’re simply some well-respected names in the community that we’ve compiled to share in situations like this one).

I wish you the best of luck with your project,
George

[George]

Thanks @Tom,

I took a look and found that these are the specific errors coming from the Visual Composer system:


Warning: Invalid argument supplied for foreach() in /home/rtc/public_html/wp-content/plugins
/js_composer/include/classes/core/access/class-vc-role-access-controller.php on line 176

Warning>: Cannot modify header information - headers already sent by (output started at /home
/rtc/public_html/wp-content/plugins/js_composer/include/classes/core/access/class-vc-role-access-controller
.php:176) in /home/rtc/public_html/wp-content/themes/sportcup/ReduxFramework/ReduxCore/inc/class.redux_functions
.php on line 192


We do not make the code that is referenced in those files, so I would recommend bringing these errors to the Visual Composer support team and seeking assistance from them from there.

Best of luck with your project!
George

[George]

Thanks for your follow-up here—can you share links to the other threads you found?

I will cross-reference the information and see where this bug stands.

Thank you!
George

[George]

Thanks for reaching out, Ilse. These are our “Pre-sales questions” forums—for technical support, can you log into your account on this site and post in a premium forum if you have a premium license?

If you don’t have a premium license, then please post your support question in our free support forums for The Events Calendar at http://wordpress.org/plugins/the-events-calendar.

Thank you! I will be closing this thread itself to facilitate the above actions.

— George

[George]

After reverting back to 2015 theme the widget is now working.

☝️ This fact here means that the ElegantThemes theme is the source of the problem. I would recommend reaching out to their support team for further assistance regarding what Divi might be doing on your site to break the widget.

Sincerely,
George

[George]

Hey romanz,

That cost field exists in the free version because there is no way to establish the cost of an event.

But when you have Tickets installed along with events, well then the tickets have a price and that is the cost of the event, so adding another cost field is unnecessarily redundant…

…in most cases.

Some folks want both though, so you can do that by adding the snippet mentioned in this knowledgebase article → https://theeventscalendar.com/knowledgebase/use-the-event-cost-field-with-tickets-installed/

Try that out and you’ll have both fields on your site.

Cheers!
George

[George]

Thank you for confirming all of this!

I am puzzled here—I do not have these issues on my site, whether Jetpack is connected or not.

I will keep tinkering and exploring, but in the meantime, can you open up a support ticket with your webhost? There might be something on the server level at play here.

— George

[George]

Sorry about that Melissa—that’s because this is a Pre-Sales Questions forum post.

These forums aren’t even meant for support like this, I should’ve noticed—these are meant for only pre-sales questions forums.

Shoot us an email with those license keys AND a link back to this forum thread for context; I’ll take care of things and reply to you there.

I’ll close this thread to facilitate that. The email address is support at this domain. 🙂

Cheers!
George

[George]

Thank you!

This reveals that Event Tickets Plus is at version 4.1 on your site—can you update this to 4.1.1?

It also shows that Events Calendar Pro is at 4.1—can you update this to 4.1.1, too?

This will bring all of your versions to 4.1.1 together which might help.

Thank you,
George

[George]

Excellent! Best of luck with your site. 🙂

[George]

Hey @Greg,

This CSS should help get rid of that gap:


#tribe-events .tribe-events-list .type-tribe_events {
border-bottom: 0 none !important;
min-height: auto !important;
}


This is the only way I could pull it off.

For further customization support, I would recommend hiring a developer if needed, but I hope this last bit of CSS I shared helps.

— George

[George]

Hey Nick,

The fieldsets are their own post type. This is post type is ticket-meta-fieldset by default.

To get the DATA, however, all you need is the “Product” ID of the actual ticket.

You can then use this method, where $product_id is the Product ID:

$meta = Tribe__Tickets_Plus__Main::instance()->meta()->get_meta_fields_by_ticket( $product_id );

How do you get a Product ID? Lots of ways; it all depends on your project and your custom coding and where you need that code.

I would recommend opening up a code editor and finding this class inside your Event Tickets Plus files:

Tribe__Tickets_Plus__Meta__Render

Read through that, tinker a bit, back-engineer it—it’s all there and you can learn a lot.

I will now be closing this thread because we cannot help with code and code customization projects.

If you need to do some custom coding and aren’t familiar with sussing out these sorts of inner-workings details, your best bet is to hire a professional to help out.

I wish you the best of luck with your custom designing and building.

Cheers,
George

[George]

Thank you for this information, @Linh.

I’ve been tinkering a bit on my own test site and have not yet reproduced these problems, and all of your site’s information is up-to-date, so unfortunately there might be a deeper bug going on here at the root of these issues.

We are working on a deep investigation into Eventbrite because we’ve had a spike in issues like this. There have been API issues in the past and they might be happening again.

What does this mean? Well, unfortunately it means that we’re going to keep investigating. I don’t have many specific things to recommend at this time. 🙁

Stay tuned to this thread, though. I will be posting updates if we have any!

Sincerely,
George

[George]

Sure—your recurrence information is mostly set up, you just need to give the event a start and end time on the same day.

So, keep your recurrence information, but make the event start some time on 3/30.

Then make the event END some time ALSO on 3/30.

(If the event is all-day long, then just check “All day event.”)

Then your recurrence will work as expected.

I hope this helps!
George

[George]

No problem David, thanks for sharing—just wanted to see what the solution was, and I appreciate your sharing this!

Best of luck with your project,
George

[Author]

Posts