Set as Featured Action?

I'm very pleased with the array of options with managing the status of an article on the front end as seen here:



There does not appear to be a "set as featured" option. Looked through settings and searched around the forums for this. Having a "set as featured" option would make managing the frontend a breeze in terms of updating the homepage.

good idea
issue here
github.com/FLEXIcontent/flexicontent-cck/issues/692

Thanks micker!

Regarding the state selector,
for both backend and frontend (recently) we

- restyled the state Selector
- removed the on-page-load JS for state selector, thus having zero effect JS delay because of it on page load
- removing all its inner HTML too, to cut down on browser HTML rendering too

The above last 2 points are very important when listing 100+ items, e.g. saving 4 seconds (when listing 500 items)

---

And a featured toggler was added too, so with little effort we can show in frontend
- but BEFORE for showing in frontend, a question must be answered which people should be allowed to use it

e.g. in backend we allow the same as Joomla:
- people that can change state (can publish / unpublish)

i think this people that both:
- change state (can unpublish / publish)
- have backend login privilege

I'm quite pleased with the new styling of the actions button menu as well. However it's worth noting that the menu flops over to the right as seen here:



It should go from right to left (as it was in FC 3.1.1). In addition to it not being quite in the right spot this ends up making it non responsive as seen here:



Put it's orientation back would fix the issue. I'm guessing it's missing a class for this.

As for the featured permissions, I would have it require admin panel access + delete access. The publishing idea works, but generally those who are considered trust worthy enough to delete pages are trust worthy enough to feature content. Publishing is not as serious, however having admin access in addition to that also points to it being enough. Honestly I could go either way.

Hello

our old Code / CSS had this into consideration,
i remembered to do it and then it was passed without checking this

it is good that you bring this up