Visibility Control for WooCommerce helps you hide messages, menu and content for specific criterion anywhere on your WordPress page.
You can show/hide HTML elements, menus, and other details based on:
1. User’s purchase of a particular WooCommerce Product or Variation, Or
2. User is Logged In or Logged Out.
You simply need to add a CSS class to your element div or span. As explained here:
If Product or Variation ID is 123
- To show the element/menu item to user who purchased above product, add this CSS class: visible_to_product_123
- To hide the element/menu item from user who purchased above product, add this CSS class: hidden_to_product_123
- To show the element/menu item to a logged-in user, add this CSS class: visible_to_logged_in OR hidden_to_logged_out
- To hide the element/menu item from a logged-in user, add this CSS class: visible_to_logged_out OR hidden_to_logged_in
Mechanism of Functioning
- Multiple CSS Classes: If multiple visibility control classes are added, ALL of them must meet the criterion to keep the element visible. If any one of them hides the element, it will be hidden. For example: visible_to_product_123 visible_to_product_124 will show the element only to those who have purchased to both products.
- Hidden data/elements reaches the browser. Though user’s do not see it.
- CSS is added to the page for all CSS elements that needs to be hidden based on above rules.
- After page is loaded. These elements are removed from page using jQuery (if available), so it won’t be available even on Inspect.
- Elements rendered after the page load are hidden but not removed from DOM/page.
Depending on the interest in this feature, we will decide on adding a setting, shortcode and/or a Gutenberg Block option to achieve this feature.
This section describes how to install the plugin and get it working.
- Upload the plugin files to the
/wp-content/plugins/visibility-control-for-woocommercedirectory, or install the plugin through the WordPress plugins screen directly.
- Activate the plugin through the ‘Plugins’ screen in WordPress
- Add the CSS classes to your HTML elements or Menu Items as described in the Details section.
What is WooCommerce?
WooCommerce is one of the best eCommerce plugin for WordPress. It allows users to create a fully-fledge eCommerce store with multiple payment methods.
[Our Other Products] What is GrassBlade xAPI Companion plugin?
GrassBlade xAPI Companion is a paid WordPress plugin that enables support for Experience API (xAPI) based content on WordPress.
It also provides best in industry Advanced Video Tracking feature, that works with YouTube, Vimeo and self-hosted MP4 videos. Tracking of MP3 audios is also supported.
It can be used independently without any LMS. However, to add advanced features, it also has integrations with several LMSes.
[Our Other Products] What is GrassBlade Cloud LRS?
GrassBlade Cloud LRS is a cloud-based Learning Record Store (LRS). An LRS is a required component in any xAPI-based ecosystem. It works as a data store of all eLearning data, as well as a reporting and analysis platform. There is an installable version which can be installed on any PHP/MySQL based server.
It is pretty similar to this plugin and having same features, it allows controlling the visibility of HTML elements based on user’s access to the LearnDash LMS course.
It automatically mark the LearnDash lessons or topic page completed in the background when user visits the page. The Mark Complete button will will act as next button after enabling this plugin.
This plugin allows you issuing points and badges for the activities happening on xAPI or SCORM Content. It works with GamiPress and GrassBlade xAPI Companion plugin.
We provide native Experience API (xAPI or TinCan API) support for WordPress with GrassBlade xAPI Companion plugin. We also have a Learning Record Store called GrassBlade Cloud LRS for advanced reporting of WordPress events and eLearning content.
以下人員參與了開源軟體〈Visibility Control for WooCommerce〉的開發相關工作。參與者
- Feature: Added support for roles: Example: visible_to_role_administrator
- Fixed: issues with addons page specially on network website.
- Fixed: jQuery 3.0 conflict on some websites.
- Improvement: Compatible with different editors now: Gutenberg, WPBakery Builder, Visual Composer, Elementor, Brizy Builder, Beaver Builder, Divi
- Added Add-ons page
- Initial Commit