Posts by dosa

Interesting. I changed the Route to: newsroom/category/[slug:categorySlug]

The page is no longer a 404, but it's not filtering anything either. Just showing ALL articles. So the slug must not be connecting, right?

Does the Set have to be defined as well?

Thanks (again) for this. It helped me resolve another issue I was having as you saw on my other post

Though my slug must not be correct for this page as it's still not working.

And here is the Setting for the slug:

And when I try mysite.com/newsroom/category/awards I still get the 404. I also tried mysite.com/newsroom/category/tags/awards

I hope I am close!

Hi JordinB - I just realized now it was related, sort of. When you mentioned the Routes, I went back at checked the "Post" page and sure enough, I had the wrong routes, since the old name, 'community', was changed to 'newsroom'. I switched them and and boom, working! Thank you for mentioning that!

Now if I could only get those paths right on the Category page.....

Sorry, this is Runway 3.15 latest.

Not sure what I missed, but my blog has a slug setup in SETTINGS as: /newsroom/{postSlug}

I'm displaying articles with perch_blog_custom just fine. But when clicking into an article, I get a 404. The URL looks correct. I tried switching the slug, but no luck. Can anyone help see what I'm missing?

Yes, the set is /tags

Yes, the slug is /transform (I used "awards" in my example above, but same idea)

Not sure what you mean by a "route to parse the category url". Is that something I missed?

In my post.html I have a category selector, see attached example of "Awards" which has a slug of "tags/awards"

I want to use a link like: mysite.com/about/newsroom/category/tags/awards ....to display the results.

I created a page in about/newsroom/category with the code above, then tried the URL and got a 404.

I then switched the 'category' => $categorySlug to 'category' => 'tags/awards'

That shows the items just fine, but why doesn't the URL work using the $categorySlug option?

Ah, sorry. Yep me too Runway all the way.

I'm saying when I enter the proper URL it doesn't work. I have a page setup called /category (instead of archive) so category/tag/transform doesn't work.

The only way it's working for me is directly adding the tag string in the "category" option. That means a manual page for each. There are only 10, but seems unnecessary if it can do the linking dynamically.

....so this would be the "Awards" tag page. But I'd rather it be dynamic, not hardcoded.

Hmm, doesn't work yet. I have two Category sets. The one I want to reference is "Tags". How do I define that set? I tried using the slug from the Categories....in this case an example would be: about/newsroom/category/tags/transform

But I get a 404.

...using Runway by the way. Does that change things?

Yes, that's the function I'm talking about! So is it more complex with multiple Sections?

Yes, I'm categorizing them now, but they started as sections from one blog.

The goal is:

1. Split each group of postings on their own pages (which I am doing now with sections)

2. Also to have category pages for different ways to view the articles (also doing that with sections)

3. But the challenge is to have "tag" style links to a subject, the display all related articles to that category, no matter what the source. Like a dynamic link.

So in my example above, the News story is always on the News pages, but that same story if it has a Category attached to it (which I have setup in the post.html template already), then it can show up on another page since it's related, but not in the same section. The issue arrises when the sections are split up. So I wonder if separate blogs would make sense.

On that same note, I am thinking if I do add additional blogs that match the Sections, I can export those Section stories, and re-import them into the new blog tab. Do I have that right?

Anyone have thoughts on this? Should I switch from Sections to seperate blogs, or keep the Sections and filter them with Categories?

Well, I figured it out. But I'll leave this up in case it happens to you. I had to go into the FTP and fully delete the perch_blog, perch_kraken, perch_forms apps, and full add them back. Using Sublime, I thought the "sync" feature would do it, for there must be something it's missing.

Anyway, once you do that, updates are done

Installing a fresh staging site as I migrate from another site. I've updated all the apps and matched them to my development site, but still I see this warning in the "Add Ons" tab under Diagnostics. I tried the "Update" button, but these apps remain even though I am sure I've replaced the perch_blog, perch_forms, perch_kraken in the addons/apps folder. What step did I miss?

I've got a blog with multiple Sections, each section has many stories. We split those Sections up in pages in the website, such as News, Press, Awards, Blog.

I'm display those sections like this:

Notice the Section is set to "press". But what if an article belongs in MULTIPLE sections. A Press article could also belong in an Awards article. Can you apply more than one Section to a particular post?

This site grew over time and now I realize maybe I should have created multiple Blogs instead, and not one Blog split into sections. Is it too late? Can those posts be moved? For example: Blog has a Section called News with 115 posts ....can I export/import those posts into a new Blog set called News instead? Seems like it would make more sense, but I'm not sure it's worth moving everything. Thoughts?

PS. In researching this, I see this link is broken @drew - https://docs.grabaperch.com/addons/blog/multiple-blogs/

My question was actually inaccurate. What happens is that when CMS blog editors update a page, the date seems to reset. So when they go back and update the post date, it's fine and in order.

We later learned by trial and error that the users were switching the template after doing edits, which reset the date. So now if they start by resetting the template (I have new blog templates ready for older posts) then it's fine and the date doesn't reset. Thanks anyway on this one!

That did it - you are the man @hus_hmd! I get it now, I was putting the addition class INSIDE the perch:if, not just outside it.

Can you have two- perch:before tags?

Ah, nice layout. Thanks guys!

But when I test it, one thing is missing. The "Featured Article" should have a class of "article-1" but the rest of the "Blog Articles" should have a class of "article-3". When I implement your code above, it's only showing one or the other.

So where do I add the "article-1" class for just the Feature Article?

Thanks, however it's not working as I expect because the class that controls the layout is above the <article> class. Other ways to keep the featured view on page 1 of a paginated page?

I've got a page of Blog posts displaying like this:

You'll see I'm using two chunks of content, each split into "article-1" for the large featured story and "article-3" classes for the rest of the remaining article in a grid style.

Two issues have come up:

1. When using the pagination, the featured story stays large, but I'd like it to continue using the article-3 section. Does the pagination have to be for only perch_blog_custom?

2. Since these perch_blog_custom instances are tapping the same Blog content, the Featured Article doubles in the Blog Articles. How can I filter that out when it's on the same page?