Plans - hierarchy - plans as options or products?

Any update on this ?

What I think now is:

We can add a new standard field to plan restriction rules called PRICE. If you leave it empty, then it is rule for general plan, but if you put price there, It will become an additional option. Somethign like restriction to access forum support section:

+$15.00 - Add support forum access

So if you checkbox, this amount is added to your purchase and this rule becomes active for you.

What do you think?

iH likedthis aditional price option. i had to create two aditional plans for an adon service.

I'll add it in Emerald 10 since it require some refactoring of existing restriction mechanism. And I'll refactor it as I want to create usage limit parameter per restriction not single in the plan.

Sergey So if you checkbox, this amount is added to your purchase and this rule becomes active for you. What do you think?

Sounds even smarter than my initial idea ;) Why not.

Sergey it require some refactoring of existing restriction mechanism...

On the other hand, my basic idea is easier and just completes the existing pricing feature. My idea came from the "reduce price" option. I wondered why there is no opposite!?

Primarily, I did not think of "rules" and "new restrictions". We already have cross-plans with there own restrictions. IMHO it just requires the new pricing option.

pepperstreet IMHO it just requires the new pricing option.

I cannot see how increas price would work depending on other plans.

Sergey I cannot see how increas price would work depending on other plans.

But there is already "decrease/reduce" option and logic.
Isn't it the same principle? Just vice versa ...

pepperstreet But not so important if only moderators/admins can see them.

It is visible for everyone.

Please change style in inspector and give to me I'll apply.

pepperstreet Do you enable adv filter for tags?

Not yet. Lets first add soome tags and then we will see how we can create acces to those filters.

pepperstreet Filter on-click works for 1 tag only. So, we have to use the exact same "spelling"! BTW, does it respect upper/lower cases?

When you start typing, you have suggestions. If there is somehting, you just use what is there. Iven if spelling is not good. I can chnage it anytime later in tag manager in backend.

pepperstreet What about an extra Status field and Filter for the same purpose? Any advantages?

Status only have 6 options. I am not sure how I would utilize it. And 2 statuses one with Solved and Accepted and another with planned and roadmap would be confusing. That should be the same status.

Any style that you like. Give me CSS.

PLease remind me later. I have to update Cobalt first on MintJoomla since I have new tag list method there. I can apply styles only after I update.

Sergey PLease remind me later. I have to update Cobalt first on MintJoomla since I have new tag list method there. I can apply styles only after I update.

Just found this topic by accident ;) So, here is your gentle reminder!

Updated styles. Looks much better now!