Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
James Tauber
@jtauber
i think I might even prefer STATES to STATUSES too
Patrick Altman
@paltman
yeah
James Tauber
@jtauber
so I’m fine with PINAX_BLOG_UNPUBLISHED_STATES
Patrick Altman
@paltman
let’s do that
i think that is even more explicit
James Tauber
@jtauber
yep
agreed
Patrick Altman
@paltman
but Post.status or Post.state will have a choices that is built by combining that list with Published
James Tauber
@jtauber
yeah, that’s fine
Patrick Altman
@paltman
whereas SECTION records an index integer that is determined at site ready, i think i’d prefer state to be a slugified version of the name in teh list
that said
an integer is predictable for storage
i’ll just copy the section implementation
has stood the test of time
Steven Wilcox
@swilcox
speaking of sections... because you're using the index integer if you were to say "insert" a new section somewhere other than last in the list of sections after writing posts associated with the other sections, you'll end up assigning those previous posts to the new section you added.
Patrick Altman
@paltman
that’s a good point
i’ve considered changing section to be just the slug that is defined
and then just documenting rules about max characters allowed in teh setting
Steven Wilcox
@swilcox
another idea... the blog_list and section_list views could be unified or partially unified and the corollary would be to have the ability to do the q= search stuff while in a section_list view and results limited to posts within that section.
Steven Wilcox
@swilcox
btw, I've forked it in case I get the chance to work on it and see if I can make the view thing happen.
Steven Wilcox
@swilcox
another thought on sections as I was working on my merged view. To a visitor to a site, "All" means something more like "any" section. To the owner of a site, the "All" seems more like you have it, which is a separate section "all" which also shows up in the query for a particular section. Via template/display logic, you can treat them that way (by never explicitly linking to the "all" section and instead linking "all" to the blog list which shows all categories). But just wanted to point out that a visitor to a site might be confused by the "all" category if used as a separate section name. Or maybe it's just me. I don't know. Wondering if there should be an optional way to get a list of sections without the "all" included for making it easier to display sections without the "all" listed.
James Tauber
@jtauber
I thought we used “all” in both those senses depending on whether you were authoring or reading
but it’s been a while
Steven Wilcox
@swilcox
seems like if you do a Post.objects.section("all") it's only giving you posts in the "all" section. Which is right I suppose, but since "all" is the slug you get using the template tag to render the section slugs and names, it's going to link to a view (presumably) of just posts flagged as being the "all" section.
James Tauber
@jtauber
yeah, that seems suboptimal
i do remember the eldarion blog (this isn’t the place to talk about eldarion internals, but biblion came out of eldarion’s blog) had a “general” and if you put a post in “general” it appeared in both the “technical” and “business” streams
Patrick Altman
@paltman
i think that was because there was/is a setting to name the “all” section and in that case we named it “general"
so i think the behavior for the “all” section whatever it is called needs to return everything; of course now that I think about it, that seems ind of stupid as why use the section api instead of just all published
certainly something we should revisit holistically to make sure we are doing what makes sense regardless of the history
Steven Wilcox
@swilcox
I almost addressed it in the blog_list view when I merged them. If you change the "new" first line of the blog_index to:
if section or section != settings.PINAX_BLOG_ALL_SECTION_NAME:
It will treat /blog/section/all/ the same as /blog/
Steven Wilcox
@swilcox
oops... that should be "and"
James Tauber
@jtauber
so I’m working on learning-greek and because most of my Greek linguistics libraries are Python3, I’m switching learning-greek to Python3 but I’ve just discovered pinax-blog doesn’t work with Python3 because of the creole library
Patrick Altman
@paltman
Yeah. I specifically disabled py3 on Travis because of creole.
James Tauber
@jtauber
i created #44 for it
Patrick Altman
@paltman
@jtauber pinax-blog==4.0.0 is now on PyPI with Python 3.3/3.4 support and optional creole
i couldn’t workout how to make it support Python 3.2
as it seems Markdown requires Pygments and Pygments installation fails under 3.2 for some reason
Patrick Altman
@paltman
works nicely
Patrick Altman
@paltman
@jtauber thoughts on pinax/pinax-blog#37
Andrii Magalich
@ckald
Hello, is there anybody here?
Steven Wilcox
@swilcox
@ckald yes.
Andrii Magalich
@ckald
I wanted to ask if anybody is going to fix the problem with AUTH_USER_MODEL
Actually, there is an issue and a PR on this topic: pinax/pinax-blog#46
It's Travis build has failed, but it does not look like this is a PR problem
Patrick Altman
@paltman
@ckald I'll check it out
Patrick Altman
@paltman
@/all we have switched over to using Slack (http://slack.pinaxproject.com) instead of this (Gitter). Please join us there!
Slava
@slavugan
can't find how to get "section_list" in template