Kento

Hi Raquel,

One simple approach that you could use would be to create a specific group which protects the material for that time frame.

For example, if you were to provide protected material for the month of October in2024, you could create a group named “20241001 to 20241031” and protect the corresponding entries by assigning them to that group.

For those who should be able to access the material, you would assign the users to that group. If they should not have access after a certain amount of time, you would then remove those users from the group.

There is also a premium extension which allows to drip content (links to documentation page), but it does not cover your specific requirement “only have access to the material generated between those two dates”.

So maybe the way I’ve explained above would be appropriate for your case, please let me know if that helps or if you have further questions.

Cheers!

Hi,

If your question is related to Groups or any of its free extensions, you can use this or the related forum here to post it.

If your question is related to any of the premium extensions, please note that posting about commercial products goes against the forum guidelines and those questions are better directed at the corresponding support areas at WooCommerce or itthinx.

The warnings on chmod() are related to the filesystem permissions, not to the permissions that are managed via Groups. I’ve tried to see if I could observe similar warnings when using the latest versions of WordPress with Groups + Elementor + WooCommerce but don’t get any warnings, neither when protecting a page with Groups nor when editing that page with Elementor.

I see there is also a conversation related this with the support team, if any further help is needed please follow up there as premium support will be able to dig deeper if needed.

Marking this as resolved as I can’t replicate the issue on a clean install.

This was answered here: https://www.itthinx.com/plugins/groups/comment-page-18/#comment-1132935

Marking as resolved, but feel free to follow up if needed.

Friendly reminder that posting about commercial products is against the Forum Guidelines https://www.ads-software.com/support/guidelines/#do-not-post-about-commercial-products

If you need help in integrating certain aspects among two different systems, you can also reach out to the developers of those. As far as Groups and its extensions is concerned, things that make sense in a generic way, even among differing membership solution, could still be considered. That’s not a guarantee that it will happen, but it will at least be looked at.

To get support for WooCommerce extensions and where you could also reach out to the extension developers, you can use https://woocommerce.com/my-account/contact-support/

Hi Jonathan,

Many thanks for your contribution, this has been taken into account in the latest release.

Cheers

Perfect, if you’re going to implement it this way and want to share a glimpse at your solution in case others might find it useful, please do. Any questions or suggestions on the way, please let me know.

Hi Alan,

Many thanks for the added explanation, based on what you describe, this would indeed be a case which would require the object-based capabilities which are yet unsupported by Groups.

What might work for you could be a customized implementation that relies on the membership info from Groups and hooks into WordPress filters to determine whether a user has or has not a certain capability. This could be based on the group membership of the post creator and the user for which a capability would need to be evaluated.

So when a WordPress capability to edit a post is evaluated, you could hook into the user_has_cap filter, look at the post to get its author, get the groups to which the author belongs, then check the groups for the current user and evaluate the result for the filter accordingly.

Thinking about it that way, I think it should be quite easy to implement for a particular case. It’s more difficult when trying to generalize it, but that shouldn’t be a concern in this case.

I hope that makes sense, do let me know if you have questions on the suggested solution.

Hi Alan,

In general, the user who should be able to edit a post created by another user would require the edit_others_posts capability. Note that this would apply to all posts that the user can access. For example, you could create a group which has the following capabilities:

• edit_posts
• edit_published_posts
• publish_posts
• edit_others_posts

The Roles and Capabilities documentation has details on each of those.

Beyond that, it would be great to be able to determine these things in a more fine-grained manner, we’re headed in that direction but object-based capabilities aren’t supported yet. Anyhow, the above might be suitable for your case. You can give it a try and determine the most suitable set of capabilities.

I’ll mark this one as resolved, but feel free to comment if there are further questions or ideas you’d like to share on this topic.

FYI this has been fixed in version 3.1.0 just released.

An update as release 3.1.0 just came out where this should not be possible to happen anymore, so marking this as resolved. Please give it a try and if you see any issue, please feel free to follow-up.

Thanks for reporting this, I can replicate the issue trying to bulk-remove group assignments on posts. Looking into it to send a fix on its way.

Hi, I’ve tried to replicate this but couldn’t, please provide some detail about when this happened, i.e. what action you undertook when it happened and which plugins and theme were active.

Hi,

Your question does not seem related to the Groups plugin but rather a question for the plugin you have mentioned, I would advise you to post details about your request on https://www.ads-software.com/support/plugin/wc-multivendor-marketplace/ where the plugin authors might be able to help you further more appropriately.