Symphony.

I’ve been working with Nick’s SymQL lately and I run into problems with data source pagination in connection with filter actions for tag list fields. Brendan mentioned that this might be a long running bug in the core tag list field. As SymQL is building a layer on top of the Entry Manager the tag list field might really be the problem.

Sorry for cross-posting but if this is a core bug it should be mentioned here.

Is this easy to reproduce? Does it only happen with SymQL (even if it appears its the fault of the core)? I.E. can you create a normal DS and still have the same problem?

I need to check this again. I switched from SymQL to custom SQL to solve this issue.

(double post — sorry)

I believe this issue has been resolved somewhere down the line.

1. Create a section and add a Text & Taglist field
2. Create 3 test entries using random tags ([one, where], [test, two], [one, test])

Now:

1. Create a datasource and set the pagination to 1 page.

2. The output pagination element will be:

   <pagination total-entries="3" total-pages="3" entries-per-page="1" current-page="1" />

Now update the datasource and filter on the Taglist field [test]:

<pagination total-entries="2" total-pages="2" entries-per-page="1" current-page="1" />

Which seems correct to me.

I did some test with Symphony 2.1.2 today using the custom datasource mentioned in the first post (which is SymQL based): my issue still exists and I guess it has something to do with the SymQL OR filter. The datasource return the correct set of entries but miscalculates things inside the pagination object.