Source theme collection filtering not working

Developer help Routing
1

So this is annoying. This is my current routes.yaml.

routes:

collections:
  /archive/:
    permalink: /archive/{slug}/
    template: index
    filter: tag:archive
  /:
    permalink: /{slug}/
    template: home
    filter: tag:-[archive]

taxonomies:
  tag: /tag/{slug}/
  author: /author/{slug}/

Interestingly, this works when source is set to magazine or highlight. But when I set it to search or landing, it doesn’t work.

Is there any easy way to fix this using routes.yaml?

2

I believe the problem is that the source homepage uses the routing for the top part of the page (fancy layouts) and then does a #get request for the feed at the bottom. But landing and search use only the bottom part.

This is a five minute fix if you can load a custom theme. Are you able to?

3

Unfortunately not, I’m on the starter Pro plan and really don’t have a need to go up.

Pretty weird this is a default OOTB ghost theme and it’s not even compatible with their features.

4

Gotcha. So maybe take a look at Casper or Edition. They’re somewhat similar to the source landing setting…

5

Is there really nothing else I can do unless I modify the actual theme itself?

Casper and Edition have their own issues I need to spend time screwing around with code injections, which I have already done with source. Got everything working perfectly, except this one thing lol

6

Hi @Cathy_Sarisky , I have this issue and you’ve mentioned its a 5minute fix. Any way you can help me with what I need to know?

This is my yaml file.

routes:
  /:
    controller: channel
    filter: tag:-members
    template: index

collections:
  /:
    permalink: /{slug}/
    template: index
    

taxonomies:
  tag: /tag/{slug}/
  author: /author/{slug}/
7

Hey. You need to be able to load a custom theme. If you can’t do that (because you’re in a starter plan), then there’s not an easy fix.

If you can upload a custom theme, then you need to download the theme, find where it is making the #get request responsible for those posts, and add a filter parameter. Then zip and upload. It’s a small enough change that you don’t need a whole dev environment. Just unzip, notepad edit, and recipe. (I like 7-zip but anything you have that will unzip and rezip will work.)

If your theme has a home.hbs, start there. If not, start with index.hbs. Then look in the partials folder for the partials it is including. Not at my desk this morning, so you’ll have to do a little detective work!

8

Oh I see! Yes I am using source on a custom theme. Thank you … it worked!!!

1 Like
9

I’m running into this issue same issue. It doesn’t seem like Source has been updated yet, which is crazy. Regardless, I’m not understanding the get filter. Am I matching what is set in the routes for the collection?

i.e.:

collections:
  /write-now/:
    permalink: /write-now/{slug}/
    template: index-writenow
    filter: primary_tag:write-now
  /:
    permalink: /{slug}/
    template: index-newsletter
    filter: primary_tag:-write-now

I’d replace the get call on index-writenow to read:

{{#get "posts" include="authors" limit="16" include="primary_tag:write-now"}}

I’m just getting an empty page. And, conversely, I cannot figure out how to filter out the write-now tag on the main index page. I’ve tried about a dozen get combinations and nothing seems to work.

10

I’ll let @minimaluminium speak to that. I’m not sure the current behavior is exactly a bug, but it does seem like it gives users trouble pretty regularly.

{{#get "posts" include="authors" limit="16" include="primary_tag:write-now"}}

^^ This is incorrect. ‘Include’ is for saying what fields you want. You need:

{{#get "posts" include="authors" limit="16" filter="primary_tag:-[write-now]"}}

and...

{{#get "posts" include="authors" limit="16" filter="primary_tag:[write-now]"}}

As an FYI: Ghost returns an empty page when it encounters an error. If you are developing locally, reading your logs can give you important clues about what the problem is.

11

Ok, I have it set for the write-now collection page, but I’m still running into issues with the main feed. The only way I can see to do this with Source is to build a seperate template that combines the index.hbs with an edited post-list.hbs, but I can’t seem to get the right get combination to exclude anything. And routes might as well not exist at this point.