[Casey D]

Hello christi78,

I’d like more information if you’d be able. There may be some sort of bug or a usability flaw we haven’t considered yet.

From what I can tell, the javascript validation works well, even if I remove the ‘End Date & Time’. There is this red text and a javascript alert instructing the user to set an end date.

 

Does this make sense? Let me know if I can explain anything else!

Cheers!

– Casey Driscoll

[Casey D]

Hello patrailsofhistory,

For some reason your ‘spans’ have a ‘display: block’ to them in your theme. If you do something like this

#newsbox tribe-mini-calendar-event span { display: inline !important; }

it will probably work, but no guarantees. You’ll have to confirm but that will give you push in the right direction.

Does this make sense? Let me know if this doesn’t work for you.

Cheers!

– Casey Driscoll

[Casey D]

Hello jjeanx,

Typically that level of customization goes beyond the scope of the forums, but if you can give me a lot more information I would be happy to troubleshoot.

I will need specific links and pages though. Also, it would be very helpful to have some screenshots. Here are some excellent tools for uploading some screenshots.

Cheers!

– Casey Driscoll

[Casey D]

Hello literarychicago,

The CSS plugin from my previous reply is a great way to quickly enter fast CSS tweaks. If you wanted to get more sophisticated, you could check out our Themer’s Guide.

This article should give you some quick pointers on adding a hover state to Firebug.

Although, because of some of the javascript in play on our calendar, it may be difficult testing out the hover in some cases. Your mileage may vary.

Cheers!

– Casey Driscoll

[Casey D]

Hello hound,

The 3.6.1 maintenance release went out yesterday with javascript fixes. Did it fix your issue?

– Casey Driscoll

[Casey D]

Hello jbird1111,

We typically close threads if there is no activity after two weeks. Feel free to create a new thread and reference this one to save you time.

Cheers!

– Casey Driscoll

[Casey D]

We won’t be able to provide a mod internally, but if you would like, you can email [email protected] for a list of freelancers we have worked with in the past.

Cheers!

– Casey Driscoll

[Casey D]

Hello nysci,

We typically close threads if there is no activity after two weeks. Feel free to create a new thread and reference this one to save you time.

Cheers!

– Casey Driscoll

[Casey D]

Hello richardm,

We typically close threads if there is no activity after two weeks. Feel free to create a new thread and reference this one to save you time.

Cheers!

– Casey Driscoll

[Casey D]

Hello vinejuice,

It’s entirely likely! I’ll add a feature ticket so our devs will be able to discuss it for future releases.

If you have a moment, we’d love for you to submit your idea to our UserVoice forum. We take user ideas and contributions very seriously, and many times their ideas end up in our future releases.

Cheers!

– Casey Driscoll

[Casey D]

Hello sandras,

Ok great, happy it worked out!

– Casey Driscoll

[Casey D]

Hello sfdsparish,

From I can tell your calendar is working properly. I’d love to help but could I get some more information?

Cheers!

– Casey Driscoll

[Casey D]

Hello Adrian Forster,

Thanks for contacting us! I was unfamiliar with a possible solution for this, so I contacted a developer on our team. This is his notes:

You’ll need a means of differentiating between subscriber and non-subscriber tickets – an easy way is a naming convention, like call one “Gold Tickets (Member)”. A better approach would be to edit each ticket product in the WooCommerce product editor and assign some post meta data. Whichever works for you should work just fine.

To actually filter them out according to who is logged the best approach is not to use a hook but just override the wootickets/tickets.php template.

Then, use current_user_can() or similar to detect their ‘level’ and selectively ignore tickets in the loop (within the template) if he wanted to, though, he could set up a filter on parse_query and try to determine if it is the get_tickets_ids() query by looking at its parameters and modify from there … but I’d probably go with the easier option first off

This level of customization goes beyond the scope of the forums, but I’ll be happy to give pointers where I can.

Does this make sense? Let me know if this doesn’t work for you.

Cheers!

– Casey Driscoll

[Casey D]

From my tests, it looks like version 3.4 was the last time this worked.

Thanks for the heads up and sorry for the difficulties!

In the immediate time frame, if you wanted to roll back to 3.4 (both versions I believe) you will be able to grab the ical file and revert back.

I will be looking into another code based workaround and we will try to get a fix for this in a future release.

Cheers!

– Casey Driscoll

[Casey D]

Hello crystalbridges,

We may have accidentally overridden it, as it isn’t a fully developed feature.

You simply want to be able to get an ical of *all* events, correct? Previously you were doing this with /events?ical=1

I’ll check to see if a previous version did this and when.

Cheers!

– Casey Driscoll

[Author]

Posts