Multi category is not going to be easy and the primary reason behind it is because the workflows and acl for pages are associated based on the category.

For instance, if you have two different workflows for category A and category B. The user chooses their page to be added into both of these categories, then it becomes really tricky. Likewise, it is the same for ACLs.

The only true way to support multiple categories is when all pages has a fixed workflow that cannot be altered based on the category and the ACL.

The only true way to support multiple categories is when all pages has a fixed workflow that cannot be altered based on the category and the ACL.

That is exactly what I set up for all workflows and played with the visibility options in the specific categories.
I must admit I did not test fully the ACL behavior as the categories in use have all the same settings...

ES has so many options and features settings (that's great!) that at some point it looses some flexibility.
I will hammer it down, again, in my opinion PayPlans is probably the most important component if it could override the other components settings with Apps and Subscription Plans to recover some of the "lost flexibility"

Because of the flexibility in EasySocial, it requires proper thinking and planning before rolling out any of these features. We did thought about revamping categories and changing it to "item type" while introducing tagging which serves as categories.

But this is something that needs to be carefully executed as different sites are using the current categories very differently.

Thank you for your attention Mark.
I understand you are still keeping an eye on this and hopefully you will come to a suitable solution in the future.

On a side topic, it is such a shame I do not have enough spare time to fully test the backend options of the advertisement frontend submission and I do not see any report in the forum on the subject (marketplace became THE big thing), so lets hope for the best about Adverts...

Keep up the good work, this 4.0 version is sooo promising

PS: You can close this ticket

Thank you.

Hello,

I allow myself to join in your discussion, because I too have the same problem. It is a recurring subject on the forum elsewhere.
Cannot classify a Group or a Page in more than one category.

Indeed, it is the fact that the ACL settings of a Group are attached to a category that poses a problem.

And if we moved the ACL settings of a Group or a Page to put them in the Workflow (Form Field) ?

Because after all there are already similar settings :
Enable Photos Albums
Enable Videos
Enable Audios
Enable Files
Enable Events

These ACL settings specific to each Group and Page (Form Field), associated with the ACL settings of Profile Types, would suffice to define the usage limits.

And that would also solve the problem mentioned here :
https://stackideas.com/forums/easysocial-pages-permissions-depending-on-profile-acl-and-payplans

Philippe

1. This is not just the ACL. The workflows are also based on the categories

2. Placing the ACL under workflows does not solve anything

3. Please understand that just because you think it works for you does not mean it works for everyone else too. There are many others who also uses EasySocial and we need to think ahead for them as well.

It is indeed a very complex issue.
In this case, a Tag system would indeed be a complementary solution.
And this is also what a lot of users want

https://stackideas.com/forums/tags-for-groups-and-pages
https://stackideas.com/voices/easysocial/item/104-adding-tags-like-in-easyblog-and-replace

Have a nice day Mark.
And thank you for your patience.
Philippe

Yes, I understand but it isn't as simple as adding a tagging system. There are consequences to what we change and what we modify in the core. We do not want to make changes only to cause a domino effect on everything else.

This is something that we need to do in stages and has to be done carefully.

Hi, hi

I think what would at least in my case work really well would be:

Buy access (PayPlan) and learn ABC (In my case in a Group)
Buy access (PayPlan) and learn DEF (In my case in a Group)
Buy access (PayPlan) and learn GHI (In my case in a Group)

1) Basic Access (ES Group Access)
a) Access to basic content eg 10 videos (articles whatever)

2) Pro Access (ES Group Access/ED Discuss)
b) Access to more content eg 20 videos (articles whatever)

3) VIP Access (ES Group Access/ED Access/Converse Kit)
c) Access to even more content eg 30 videos (articles whatever)

Hope this makes some kind of sense.
In its simplest form buying in to more content AND support options.
Would love to hear some feedback even if it is just someone saying you are mad.

thanks

Paul

Hello Paul,

What you are posting here is absolutely not related at all to what they are discussing here. You are suggesting something different altogether and this is why I am requesting you guys to post on the feature requests section.

This is just getting out of hand to be honest.

Hi Mark,

sorry my bad.
did not intent to crash a different topic.

thanks for your response

best

Paul

No worries and I am not blaming anyone here. The only reason that you came and post what you posted here was because Philippe went over to https://stackideas.com/forums/tags-for-groups-and-pages and posted the link back to this thread.

Because there is a huge list of replies on the other post, you did not go through the entire list of replies to understand the context.

Hey Mark,

Indeed,since a week, there has been a lot "excitement" in the forums

All these messages are showing the great implications our community has in your components.
Everyone is looking for imporvements because they like SI components and ALSO the SI Team.

We love you all guys and we know you can help us achieve our goals!

Everyone is seeing the potential of SI components and I believe we all want to push the SI Team to deliver its best and provide us the "perfect" components.

But yes, it will take some time, it is a never ending quest.
Yes we, SI subscribers, should now calm down a little and let the SI Team breathe to get there.

I guess some have the feeling the "Feature Request" section might not get SI attention.
And we, users, do not use properly the "Feature Request" section to discuss things.
Probably it is more user friendly to discuss these request here in the forum?
We also have to monitor 2 different separated entities wihout full notification of what is happening there.
+ I do not like at all markdown, its a geek thing only...

Perhaps I should have marked this post private at first time

That's very well said Supporter.
The new EasySocial 4 version has probably given rise to frustration at not seeing the features we hoped for.
Unfortunately Mark is not Santa Claus, he cannot give us our entire gift list at once.

I agree, let's let Mark and his Stackideas team rest.
And Buy them Coffee

Philippe

Hm, maybe if you guys can outline the issues or problems that you have with the new feature requests section, we'll see what we can do to improve it?

I guess some have the feeling the "Feature Request" section might not get SI attention.
And we, users, do not use properly the "Feature Request" section to discuss things.

Interesting fact from early aviation:
The engineer of the early aircraft was almost always its pilot. This automatically led to the disappearance of bad engineering:D
Integration:
1. Developer's ideas vs webmaster's fantasies about what easysocial should be. For example, I have a fantasy that the description of the photo in the stream must be synchronized with the description of the photo in the album. That it can't be otherwise. Who does that anyway:D
2. The webmaster's fantasies about what his site should be like vs the real user experience.
3. Real user experience. This is the most important thing.

As you have noticed, there is one binding element - the webmaster's fantasies - so it would be good to integrate them when discussing feature requests, based on user experience, and convey the results of the discussion to the developer. At the same time, can fundraising on coffee, to all interested parties, can also negotiate about this. Now there are a lot of requests for similar functions, just from different points of view.
Perhaps additional moderation of the process by the trade union is needed:D

Can we close this topic and continue the discussion on this newly created post?
Improving the UX of the feature request section

Error !
Wrong browser tab

Thanks, will close this thread. Please continue any discussions about the feature requests area at https://stackideas.com/forums/improving-the-ux-of-the-feature-request-section