Setting Up Two Levels of "Featured"

This topic contains 6 replies, has 2 voices, and was last updated by  identity 4 years, 11 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #516839

    identity
    Lifetime Member
    Post count: 445

    Looking to have two levels of Featured listing options and want to prioritize sorting based on those levels.

    I’m assuming this can be set up, using a Checkbox field and setting appropriately by package. Question though is whether and how this would be setup with regard to the sorting options.

    Ideally, I’d like to have the following:
    – Premium Featured (randomized order within)
    — Standard Featured (randomized order within)
    — All other listings (non-featured) (randomized order within)

    If this is possible, what would the settings and nesting look like within the Sorting tab?

    Thanks

    #516850

    Alex Rollin
    Moderator
    Post count: 27815

    The checkbox, adding that as a subsort, would only sort listings that are not 1) featured 2) not featured, of which there would be 0.

    #516855

    identity
    Lifetime Member
    Post count: 445

    What if Premium Featured were also designated as Featured?

    Just trying to figure out a way to introduce a tertiary level as incentive for upgrade.

    PACKAGE
    ====================
    Good – not featured
    Better – featured
    Best – premium featured

    Thanks

    #516869

    Alex Rollin
    Moderator
    Post count: 27815

    Sounds like a different name for the checkbox.

    What if there was a field, admin only, “Besters” that had
    Good/1,Better/2,Best/3

    Then sort that as you say, Besters->descending, subsort->random.

    #516997

    identity
    Lifetime Member
    Post count: 445

    Alex,

    Thanks. Interesting thought.

    Tangenting off that…could this be done simply through the Package field?

    So, say there are 4 packages…

    1 – Free, non-featured
    2 – Paid Bronze level, non-featured
    3 – Paid Silver level, featured
    4 – Paid Gold level, “premium featured”

    Goal being for sort order:
    Gold level (randomized)
    Silver level (randomized)
    Bronze level (randomized)

    Would that be doable just using the existing Package field or would a dedicated field, e.g. Besters, be needed?

    Thanks

    #517058

    Alex Rollin
    Moderator
    Post count: 27815

    Package field is a number, so, packages can be created in an intentional order so the ID can be used for sorting or custom code can be used to sort non-sequential IDs into a custom order.

    #521225

    identity
    Lifetime Member
    Post count: 445

    Bummer…circling back to this.

    I had been playing with it as a Radio setting and was working. But now, unless I’m missing something, looks like the only way to do this with an admin only radio field of “n-tiers” of featured ordering, is to manually edit it on every listing, upgrade, and downgrade.

    What I think is needed would be the ability to:
    – designate a field to be “pulled” into the Packages settings
    – then the ability to set the value of that field by package

    Example:
    Create an admin only Radio field of “package_tier” with Option Values of A/0,B/1,C/2,D/3 and check it as a “custom package” setting.

    Then within the Packages tab, say you create 4 different packages that you assign the package_tier as:
    – Platinum package_tier = D
    – Gold package_tier = C
    – Silver package_tier = B
    – Copper package_tier = A

    (Obviously you might want to create additional tiers and set accordingly so that you could easily “slide” a new package in between existing ones.)

    This then allows sorting to be preset to favor varying “featured tier” levels:

    Random within Platinum
    Random within Gold
    Random within Silver
    Random within Copper

    If I’ve missed how to set this up so that it is automated via the package levels, please let me know.

    Otherwise, or anyway, I think this ability to designate a field to be a package field with a varying assigned value based on package could be a powerful addition.

    Cheers

Viewing 7 posts - 1 through 7 (of 7 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount