"Featured" enhancement

i agree, would be usefull

Agree

What about featured items through field value. e.g. Status field. This can be changed in frontend without editing the whole article. Drawback: This would require to set such a field as a criteria for "featured". i.e . list those articles at the top... or select and display those articles in records-module etc.

@pepperstreet

Actually it is even possible to set the "feature" attribute through the SQL actions in the STATUS field with place holder [record_id] directly in the js_res_record table.

I was playing around with it earlier, but i was looking for a better integrated "featured" handling from the core Cobalt, since i see the 30 day functionality with the prolong options quite limited.

There is a parameter in content type which can change this 30 days to whatever.

This is not about the number of days...

it is about an easy and convenient way to switch it on and off.

An example would be - marking of records/ problem cases etc for easy identification.

they will stay on top of the list until the problem is fixed ("unfeatured") and not when it exoires after x days

That is not exactly what featured designed for.

Do you think that status field where you can set record status problem and anyone can filter to see all problem records and change status after fix?

"featured" is the only option which can be set on top of all list, regardless of the sort order.

like in the forum -- a featured article is like a "sticky" article.

in advanced template even a color scheme is hardcoded for featured attribute. (which reminds me on quite some enhancements for adv template in my head ... :D )

A strong point for Cobalt is its "flexibility" and not limiting the user. I believe that the "featured" functionality can be used for a lot of other things. The example above should only show one of many possibilities.

Yes, i agree, it can be done with a status field, but why using an additional field when it can be achieved with core functions?

Maybe not an immediate priority, but definitely worth to think about it.

Yes, i agree, it can be done with a status field, but why using an additional field when it can be achieved with core functions?

Because it is very good field with ajax actions. It is designed for those purposes.

You can add additional SQL queries for every status. For example status "To fix" set this record featured for 100 years and status solved set it back. I think custom SQL queries instatus field would be good for that.

Sergey There is a parameter in content type which can change this 30 days to whatever.

Это еще актуалньо? Весь кобаль облазил и нигде нету

Pavel8289

Sergey There is a parameter in content type which can change this 30 days to whatever.

Это еще актуалньо? Весь кобаль облазил и нигде нету

Зайдите в редактирование типа, перейдите на вклдку Emerald.

Sergey

Pavel8289

Sergey There is a parameter in content type which can change this 30 days to whatever.

Это еще актуалньо? Весь кобаль облазил и нигде нету

Зайдите в редактирование типа, перейдите на вклдку Emerald.

Спасибо. Даже не мог подумать что там оно есть!