[Paul]

Hi George,

Many thanks for your code which I have inserted into my functions.php file.

I noticed it did not disable the message for our existing admin users so I created a new account via the back-end to see if it disabled the message for new accounts only. Unfortunately the nag message was still there for the new account.

I have about 10 custom snippets in my child theme functions.php file which all work as expected, so I am familiar with this process but I cannot seem to get your code to work 🙁

Does your code disable the nag message only if a user registers via the front-end, or should this work if an existing admin creates a new user in the back-end?

Thank you.

Paul.

• This reply was modified 9 years, 5 months ago by Paul. Reason: Typographical error

[Paul]

Hi Nico,

Thanks for your reply.

I’ve never really explored JS so I would need some help getting started with that.

If you could point me in the right direction I would be very grateful.

Paul.

[Paul]

Hi Geoff,

Thanks for your reply.

I have added my vote to the feature request forum 🙂

Best regards,

Paul.

[Paul]

Geoff, you’re a star!

I downloaded the Advanced Custom Fields plugin and am slowly getting to grasps with it.

I created a sample field in the plugin called my_field_name (very original!), set the Rule to:
Post Type >> is equal to >> tribe_events
I then copied the single-event.php file to my child theme tribe-events folder and edited the code in that file to include:

<?php the_field(‘my_field_name’); ?>

and to my surprise, my sample field appeared in the single event page on the front end 🙂

This is exactly what my client wanted and, as you say, keep editing experience completely in WordPress. Although the initial setup would take a bit of time, this is a much more seamless solution to my clients’ requirements.

We will have to train some new admins on the system in the future and if they are not familiar with WordPress, Events Calendar & WooCommerce, it could all be a bit overwhelming so this should make the learning process easier for them.

I can’t thank you enough for your time & the plugin suggestion, many thanks 🙂

Best wishes,

Paul.

[Paul]

This reply is private.

[Paul]

Ok, cheers anyhoo!

[Paul]

Josh, your code worked fantastically on my dev site, and as a bonus, the internet still seems to be working!

As we all know, typing Google into Google can have catastrophic consequences, so you will be pleased to hear I refrained from doing so 🙂

I can’t thank you enough for your code snippet which works perfectly. Many thanks and thanks again… and another… thanks!

Best regards,
Paul.

[Paul]

Hi Josh,

Thanks for your fast reply and sorry for my slow one!

I’m not 100% on this but as far as I know, the WPMU DEV Post Indexer plugin does not index the post meta. If it did I think it would return search results for meta information keywords for the post type which has been indexed. I’m confusing myself slightly here, but I think that would seem logical!?

I will post to the WPMU DEV forums and ask if there is a way to index the post meta. This would probably be the best solution?

If not, creating new taxonomies is rather new territory for me and I would probably need some guidance.

I will post back once I hear from WPMU DEV.

Best regards,

Paul.

[Paul]

Cheers Geoff,

Your excellent support and enthusiasm is very much appreciated.

Kind regards,

Paul.

[Paul]

Hi Geoff,

Thanks for your reply.

I see the open feature request, which I created, but in the meantime do you happen to know which file this option resides in?

I could then just edit the line of code not to display the RSVP option.

We will soon be training quite a few administrators on how to use the system and removing unused options has the potential to make the learning process slightly easier.

Kind regards,

Paul.

[Paul]

Hi Brian,

I have just noticed this is in the pipeline and I will wait for the update to be released.
https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/8391186-reminder-emails-for-x-days-before-event

Thanks for your reply.

Paul.

[Paul]

Hi Geoff,

Thanks for your reply.

In my original post I mentioned that coupon codes are “open to abuse, simply by sharing the coupon code.”

On pondering over your message I went back to WooCommerce and spotted the ‘Usage Restriction >> Email restrictions’ field which I had previously missed.

I see that customer email address(s) can be put into this field which allows only those people to use the coupon, thus removing any possibility of the coupon being abused by people sharing it.

Thanks to your message (and me opening my eyes), I think our dilemma is now sorted 🙂

Kind regards,

Paul.

• This reply was modified 9 years, 11 months ago by Paul. Reason: Spelling mistake

[Paul]

Ok, Geoff, thanks for your reply.

Kind regards,

Paul.

[Paul]

Hi Geoff,

Thanks for the info. I’ll stay tuned.

Happy Easter,

Paul.

[Paul]

This reply is private.

[Author]

Posts