Databases
StackOverflow2013
Postsdbo
POOrchard CMS - Query based on values from ContentPicker
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOrchard CMS - Query based on values from ContentPicker
    primarykey
    data
    text
    <p>EDIT: Rephrased issue</p> <p>I think there is either a bug or I am doing something wrong.</p> <ol> <li>I add a field to the type Blogpost. This field is of type Contentpicker. I call it Related Page.</li> <li>Then I create to regular pages (ContentType Page).</li> <li>I create 4 blogposts. Two blogposts get PageOne as selected value in the RelatedPage field. The other two posts get PageTwo as selected value in the RelatedPage.</li> <li>Now I create a query with filter ContentType is BlogPost. And a filter with Blog Post.Related Page equals {21} (that is the Id of PageOne).</li> </ol> <p>I would expect to get results BlogPostOne and BlogPostTwo. Instead I don't get results. Actually I wanted the pageid to be retrieved from the page the widget is placed on but couldn't get it to work, so I reduced back to a predefined value instead of dynamic for the filter. But like I said no results.</p> <p>So is the query wrong and how should I do it then. Or is there a bug with filters for ContentPicker fields.</p> <p>P.S. I will also submit an issue in Codeplex.</p> <p><strong>UPDATE</strong> In Tokenizer all the values that contain { } are being seen as tokens and therefore are replaced. The problem is that the Ids of content items in a contentpicker field are stored with accolades. So when having {21} as the value for the filter, 21 gets tokenized and since there is no value for this token the value becomes empty. When skipping the tokenizer it works (while debugging). But one cannot skip the tokenizer, because it is very legitimate that there is a token present. So I believe there is a bug with either the tokenizer, or the way the ids are stored in the contentitem field for contentpicker. I think it can be solved by changing the contentpicker to store numbers separated with comma's but without the accolades.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMounhim
    1. USMounhim
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOrchard CMS - Query based on values from ContentPicker
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI seem to have found the 'bug' but I don't know how to solve it. I have edited the question with my findings.
      singulars
      1. POOrchard CMS - Query based on values from ContentPicker
      1. USMounhim
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload