Blog as site_start > 'list by tags' no longer works

I set my Articles Container as site_start, so i can call it like

instead of

which works fine.

But now, when i click on a tag on the site, the uri is

and the ArticlesRouter doesn't find the Articles Container anymore, which has an alias 'blog' - that alias is not inserted in the tags-uri, since the blog is site_start.

Is there an app for that?

Ok, temporary work around:
i specified a Tag Listing Chunk, where i hard-coded the blogs alias.

Not pretty, but then i'm already pretty enough.

It sounds to me like you have just to set your article resource-id as main under settings.

Thanks for your answer.

I'm not sure which setting you are referring to - if by "main" you mean setting the articles resource as the websites starting page i.e. 'site_start', this is exactly what causes the problem and is the reason for this post. As i said in the first sentence:

I set my Articles Container as site_start, ...

Or maybe you mean something different?

I just ran into the same issue and fixed it another way which I thought I'd add to this thread.

Just to confirm, ordinarily (when site_start is not equal to blog id), when you are either on the blog or on one of the articles:


and you click on a tag, you'll be taken to a page listing all articles with that tag:



BUT, when you set site_start to your blog id, then your blog and article url's become:


and when you click on a tag on either the full blog list or the article page itself, you are taken to this broken url:


Note the missing "/blog/".


SOLUTION
-----------

On the main blog page, each blog entry is created using the samples.ArticleRowTpl chunk. In there you'll find that the list of tags is created as follows:


The toLinks snippet can accept a property called "tagKey" which is set to "tags" by default.

So to fix this problem on the blog list, just add &tagKey=`blog/tags` to the toLinks call. I.e. change the above code to:


The problem will still exist on the article page. The article page is created using the template: sample.ArticleTemplate. In there you'll find the lines:


Replace that code with: (note that &tagKey=`../tags` is used in this case).



FIXED. The tag links will now be given the correct href on both the blog page and the article pages.

WARNING: Instead of modifying samples.ArticleRowTpl and sample.ArticleTemplate, you should duplicate them, and modify the copies. Then in the blog settings, change the "Article Row Chunk" and "Article Template" to point to your copies. If you don't, your changes may be overridden next time you update the Articles add-on.

Interesting. Your post made me check the tag links on my blog for the first time and you're right -- none of them work. Unfortunately, my blog home page URL is in the form:

mysite.com/blog.html

I wish I'd ditched the .html suffix long ago, but it's too late now.

The obvious choices for displaying tags don't work:


mysite.com/blog.html/tags/tagname would be the obvious choice, but it just takes me to the blog's home page.

mysite.com/blog/tags/tagname takes me to the site's home page.

Strangely, the thing that works is

mysite.com/blog.htmltags/tagname

So my question is, should I try to make the tag links generate that URL, or is there some way I can make one of the URLs above work without trashing the rest of the site or existing links to my articles?

BTW, my Archive links work as:

mysite.com/blog.html2013/08

As documentation on this topic is not too verbose ;-), I‘d share what worked for me.

If blog home is the homepage of your site (site_start), and friendly_urls is on, your tags and archive links will need some extra settings.

• container_suffix is /
  
• add the container of your blog to all tags and archive links in your Articles templates.
  

$articles-rowTpl, [[!tolink]]:
- add &tagKey=`blog/tags`

Articles Template, .post-info, [[!tolink]]:
- add &tagKey=`blog/tags`, set &target=`[[*parent]]`

Articles Template, #footer-content:
- The +tags and +archives placeholders, i.e. what goes into them, should be edited, but I couldn’t find a way to do it (can anyone help?). So I edited the template files, causing me extra work for future updates to the Archives addon :-(.

core/components/taglister/elements/chunks/tag.chunk.tpl
- set <a href="/blog[[+url]]">

core/components/archivist/elements/chunks/row.chunk.tpl
- set <a href="/blog[[+url]]">

If you had it different in the first place, you may want to do some retrofitting.
- The new url scheme will apply to new blog posts only. Old blog posts keep their url, as it is stored in the database. There is no need to do anything about it, unless you prefer a consistent url scheme.
- If they are not too many, you may want to edit your old blog post urls in the database, and redirect them in the .htaccess.
- My container_suffix used to be .html, as I have first level documents in my site. Uncheck the container setting in your first level documents, should they be checked - now the url of your first level documents changes back to *.html.

Hope this helps. [ed. note: BrigitteB last edited this post 9 years, 4 months ago.]

Thanks for the report. The tag links on my blog work now, so I must have solved this, but I can't remember how.