Hi Sue -
Thanks - although taking structure out of the equation doesn’t seem to make any difference to the results.
<h1>By Artist A-Z</h1>
<div id="primary" class="wrap">
{exp:weblog:entries weblog="shop_detail" orderby="artistname" sort="asc" show_future_entries="yes" show_expired="yes" limit="8"}
{/if}
Currently the custom field “artistname” is a custom field within a category (called artists) - i’ve also tried creating a custom field outside of the categories within the shop_detail weblog - and that too doesn’t affect the sort order or results.
With the price sorting
{if segment_3 == "price_high"}
<h1>By Price Low to High</h1>
<div id="primary" class="wrap">
{exp:weblog:entries weblog="shop_detail" orderby="price" sort="asc" limit="8"}
{/if}
If I remove the ‘limit’ I am faced with a white screen - in fact if I set the limit to around 53 for price asc or above - I am faced with a white screen - while if I set my limit to around 60 desc I am faced with a white screen (with and without structure pagination).
For some reason sorting the price desc seems to pull the data in price order (with the most expensive first) - but pulling the data asc is a complete jumble…
My two urgent questions are:
Am I referring to a custom field within a category correctly (or do I need to wrap it in some sytax to make it clear that it is a custom field within a category) for the artist names.
Do I need to define the custom field for the price as numbers / digits somehow or should a text field be fine?