Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different (current-posts-per-page) for some tags? #243

Open
toothbrush opened this issue Jan 14, 2019 · 3 comments
Open

Different (current-posts-per-page) for some tags? #243

toothbrush opened this issue Jan 14, 2019 · 3 comments

Comments

@toothbrush
Copy link

I like the fact that Frog automatically can paginate when there are more than n posts, set with the current-posts-per-page parameter. However, i'd really like to have the default, i.e. 10, posts with stubs on index.html, but be able to control whether on /tags/xyz.html pages this number might be different. Bonus points if each tag xyz and foo can have different values of current-posts-per-page. I can make this work for my situation by hacking my local Frog installation, but is there a more.. clean way of accomplishing this that i'm missing?

Apologies for all the obtuse questions. Believe it or not, i'm actually managing to make Frog work well for my purpose. Thanks again.

@greghendershott
Copy link
Owner

Sorry to be slow to respond. Although I'm still keeping an eye on Frog, I haven't had much time lately to work on it, and don't have much of its code in my brain's L1 cache.

As a result I think hacking your local installation is probably the only option for the foreseeable future. Also I'm being pretty slow about pull requests that aren't simple bug-fixes, because I just haven't much time to think through bigger changes.

@toothbrush
Copy link
Author

Don't worry about the slowness, that's fine and understandable 🙂 I don't want to be the person who gets upset because the volunteer who already contributed a bunch of super useful software to the community isn't on 24/7 call 😄

I'll continue hacking my own installation then, with the risk of it diverging a bit from yours. That's fine though – after an initial period of teething issues i'm beginning to understand the codebase a bit, and my rusty Racket it slowly coming back to me.

Should this issue be closed, or left as a nice-to-have enhancement request? It's low-priority from my POV, because i've already hacked around the problem with a terrifying (cond ...) in my local Frog.

@greghendershott
Copy link
Owner

Let's leave it open; I already tagged it as enhancement. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants