dmitcha

Here’s what I did – it works great functionally, but it is triggering an error I am trying to fix. Not sure if the answer is in this source code, so checking still.

My dropdowns were for meta fields. All I did was add a “|” at the top of the list, which then created a blank line without an actual field at the top of the dropdowns.

When I tested it, it triggered an error for the blank field, but the dropdown boxes still functioned, and they returned the correct search results.

The error I received was:”Notice: Undefined offset: 1 in /home/content/28/9910428/html/staging-db/wp-content/plugins/ultimate-wp-query-search-filter/classes/uwpqsf-front-class.php on line 94″

So I am going to check to see if the code for taxonomies allows me to override this error message, in which case, it is the easiest fix, and this plugin becomes the perfect solution for filtering ACF fields.

TC.K, thanks for your work on this plugin, and if you already know the easy to way to make this work, I’d appreciate any tips!

haaaahahaha – you still solved the MAIN problem for most of us!

Sure. It’s perfect for those (like me) who don’t care about other sort options. And maybe someone else will come up with a way to toggle it on and off after seeing this thread. I’m glad I was able to share it with others (recognizing you yourself remain unimpressed and unappreciative, lol)!

Understood. From what I’ve read here and elsewhere, what a lot of people want is the default sort order to be by registration date and descending. Happily, this snippet plus your plugin manages that specific desire – and in less than five minutes!

Thanks, and I found a simple CSS solution to remove all three columns from my Forum list, so not a problem. Note, the topic title styling affects internal pages, too, so I left it at 55% rather than making it bigger. Still looks great!

ul#forums-list-0.bbp-forums li.bbp-forum-topic-count {
display:none;
width:1%;
}
ul#forums-list-0.bbp-forums li.bbp-forum-reply-count {
display:none;
width:1%;
}
ul#forums-list-0.bbp-forums li.bbp-forum-freshness {
display:none;
width:1%;
}
ul#forums-list-0.bbp-forums li.bbp-forum-info, li.bbp-topic-title {
width:55%;
}

Hi, I currently use s2Member pro for exactly this. You configure restricted access to set the number of IP addresses within a given period. So you might say only one address per month. They have a video for set up.

I advise upon purchase that this is for “single computer access.”

This does eliminate your users’ option to access via their cell phones and tablets on the go, as those IPs will constantly change.

As soon as a user account exceeds the IP limit, they lose access. You can manually clear logged IPs to allow access again.

I’ve now switched to Woocommerce, though, and have to find another solution since s2Member doesn’t integrate with shopping carts (you configure each individual pay button to include the restricted access).

This comment is the reason I immediately downloaded and installed the plugin – thanks to steven for his hilariously helpful review!

Oddly, no (it may be a theme override).

However, now that you’ve explained this, I am going to allow checks because I can remove site registration from the checkout page in my theme and prevent access before checks have cleared. So thanks for that!

If it’s helpful at all to others, here’s a very quick summary of how to prep Woocommerce BEFORE you set up the plugin (I read the documentation and followed it carefully, but this part wasn’t clear until this exchange):

1) Install the plugin
2) Go to Woocommerce “Checkout” tab
3) Under “Checkout Options,” disable Guest Checkout if you require users to return and register after purchase (e.g., to complete a membership sign-up)
4) Under PayPal, disable the PayPal Standard option
5) Also disable any other active payment gateways (this will remove the default “checkout” buttons from any pages in your payment pipeline)
5) Under PayPal Express button, enable PP Express and follow each of the steps on the documentation page to configure. (https://www.angelleye.com/create-paypal-sandbox-account/)
6) If you choose to enable other payment gateways, you might want to use the Woo Docs to customize form-billing and form-shipping to edit elements non-PayPal buyers see (for instance, I removed the registration option and will manually add members after checks clear).
7) Rate the plugin highly and comment on the author’s awesome support
8) Donate to the plugin!

@angelleyes, I defer to you for corrections, and I hope it’s a useful summary of the WooCommerce prep for this excellent plugin.

Thanks so much for your quick reply. Here’s what works and why I’m confused (in case it helps anyone else):

1) Yes, if I just click the PayPal Express button, it does complete the Sandbox transaction and return for registration. That does capture the member AND add the associated member status, thank you.

2) All last night, I was trying to get rid of the “proceed to checkout” cart button and the “checkout” button on the shopping cart icon hover. Everything I read said those buttons were removed by the plugin (or is there an option I didn’t select?). It was clicking those that was sending me to the registration page before payment.

Sorry, I had two tabs open and posted to the wrong thread! I don’t see a way to delete my comment, so if it’s useful to anyone, the link was for restricting the view of the Events Calendar to registered users (https://www.ads-software.com/support/topic/shortcode-usage-as-calendar-month-view?replies=3#post-7440458).

Thanks for the flag, Barry!

Since this request keeps coming up (I’ve been trying to do this for days), I want to share here what this link offers in case it is exactly what you need. The link’s solution is EASY and it WORKS. It took less than 5 minutes to implement and test.

RESTRICTING ACCESS TO CALENDAR AND EVENTS
@nico’s link sends you to two snippets that allow you to restrict access to calendar content:

1) Can’t view it on the site. The first snippet restricts users that are not logged in from accessing the display of virtually generated content (e.g., the main page) as well as of event details.

2) Doesn’t appear in search results. The second snippet prevents your events from appearing in search results on your site if a user is not logged in.

PRACTICAL EFFECTS
I copied this snippet into my functions.php file, and here are the functional results:

– Clicking on the main Events Page slug redirects to your designated advisory page (e.g., “This is restricted content”).
– Shortcode content still displays (e.g., the embedded countdown clock for an event)
– Clicking on shortcode links for more details redirects users that aren’t logged in to your advisory page.
– Directly entering an event slug into the address bar also redirects users to your advisory page.

Note: I chose not to restrict the search results because I wanted users to see all of our delightful events. I just modified my search results so dates did not show up. This was a double-win because the search results were displaying the date of the event post entry, rather than of the event itself, so having to re-code that so it was correct was not a good use of my time.

IMPLEMENTATION
1) Create a child theme. That way, the changes you make to functions.php won’t be overwritten when your theme updates. (If a child theme is beyond you, back up and save your current functions.php file offline, then change the file. Make a note in your personal calendar of the file you changed and add a link to this page so you can do it all again if you have to. Real developers, please forgive my sacrilege here.)
2) Create a redirect page. This is the advisory page where users will be sent to if they don’t have permission to view the calendar or events.
3) In child’s function.php, copy and paste one or both of the snippets. Be sure to change their temp slug to the actual slug of your redirect page (the comments in the snippet show you how).
4) If you would like to restrict content on the basis of something other than a user’s logged in state, you will want to change this conditional – “user_is_logged_in” – to the metadata representing the correct state for users who have access (e.g., user must be a member of a defined group, etc.)

I hope this comment is allowed to remain since I have spent DAYS trying to work around this before getting through this, and I thought a simple explanation would save people LOTS OF WASTED TIME.

@nico, I defer to you, of course, for any corrections, here, and I thank you for your exceptionally pretty plugin. Finding a beautiful calendar was my top priority, so all the extra functionality is a plus!

I disagree with @barry :); this solution is EASY and it WORKS. It took less than 5 minutes to implement and test.

Since this request keeps coming up (I’ve been trying to do this for days), I want to share here what this link offers in case it is exactly what you need.

RESTRICTING ACCESS TO CALENDAR AND EVENTS
@barry’s link sends you to two snippets that allow you to restrict access to calendar content:

1) Can’t view it on the site. The first snippet restricts users that are not logged in from accessing the display of virtually generated content (e.g., the main page) as well as of event details.

2) Doesn’t appear in search results. The second snippet prevents your events from appearing in search results on your site if a user is not logged in.

PRACTICAL EFFECTS
I copied this snippet into my functions.php file, and here are the functional results:

– Clicking on the main Events Page slug redirects to your designated advisory page (e.g., “This is restricted content”).
– Shortcode content still displays (e.g., the embedded countdown clock for an event)
– Clicking on shortcode links for more details redirects users that aren’t logged in to your advisory page.
– Directly entering an event slug into the address bar also redirects users to your advisory page.

Note: I chose not to restrict the search results because I wanted users to see all of our delightful events. I just modified my search results so dates did not show up. This was a double-win because the search results were displaying the date of the event post entry, rather than of the event itself, so having to re-code that so it was correct was not a good use of my time.

IMPLEMENTATION
1) Create a child theme. That way, the changes you make to functions.php won’t be overwritten when your theme updates. (If a child theme is beyond you, back up and save your current functions.php file offline, then change the file. Make a note in your personal calendar of the file you changed and add a link to this page so you can do it all again if you have to. Real developers, please forgive my sacrilege here.)
2) Create a redirect page. This is the advisory page where users will be sent to if they don’t have permission to view the calendar or events.
3) In child’s function.php, copy and paste one or both of the snippets. Be sure to change their temp slug to the actual slug of your redirect page (the comments in the snippet show you how).
4) If you would like to restrict content on the basis of something other than a user’s logged in state, you will want to change this conditional – “user_is_logged_in” – to the metadata representing the correct state for users who have access (e.g., user must be a member of a defined group, etc.)

I hope this comment is allowed to remain since I have spent DAYS trying to work around this before getting through this, and I thought a simple explanation would save people LOTS OF WASTED TIME.

@barry, thanks very much for posting the link, and I hope this response helps others.

Harry, this plugin creates a “virtual page” and will not provide a shortcode (there are many, many requests).

The default slug is /events, or you can set up a customization in Events>>Settings.

Thanks so much – I disabled their “head.php” file by renaming it then replaced their header.php file with yours. It worked, then I got the error warning again, indicating base.php. So I replaced the base.php file, too. I’ve stopped getting the crazy error message “Warning: Cannot modify header information” now – GREAT news.

Hi, would you mind snippeting the lines of code you fixed here? McAfee exploded when I tried to go to the download site. Thank you for doing the fix.