Issue with isArchive after changing category base

🙋Get Help
1

Hello friends,

I’ve switched the Category base in Wordpress > Settings > Permalinks to “Topics”.

On the Frontity side, I see that when I look at the state.source.data we’re seeing an entry for "/topics/insights/’, which was previously the default "/category/insights/’ before switching the category base.

However, if I navigate to “/topics/insights/” in the browser, then I get a 404. This was not the case before switching the category base. “/category/insights/” worked just fine - no 404.

data.isArchive no longer is true for “/topics/insights/”, whereas it was true for “/category/insights/” before the category base was changed.

Any ideas on why this might be happening would be greatly appreciated, thank you!

2

Hey Brett,

That means that the handler is not detecting the url so its not adding isArchive to the data of the link.

From what I can see you also have to adjust that in frontity. https://api.frontity.org/frontity-packages/features-packages/wp-source#state.source.categorybase

Have you done that already?

1 Like
3

Thanks so much, that was the solution. Still becoming familiar with the docs, I must have missed that.

Take care!

1 Like
4

Glad it worked, man!

1 Like