pinax / pinax-blog Goto Github PK

@jtauber do we ever use this in all the instances we use this software?

Does anyone else?

otherwise when run ./manage.py migrate this error happen

RuntimeError: Model class pinax.images.models.ImageSet doesn't declare an explicit app_label and isn't in an application in INSTALLED_APPS.

There appears to be no base template examples, such as the ones referenced in views.py :
biblion/blog_list.html
biblion/blog_section_list.html

This helps with #34 as well.

I've got latest version from git today, but after i tried to setup biblion app and run it - i got -

Exception Type: TemplateDoesNotExist
Exception Value: biblion/blog_list.html

and this file is really missing. Could you please add this and other templates to repo.
Thanks for you job !

The problem seems to be the creole library which hasn't been updated in 5 years! I'm happy to deprecate its use but perhaps as a start we should not require it.

ERRORS:
blog.Post.image_set: (fields.E300) Field defines a relation with model 'ImageSet', which is either not installed, or is abstract.

Any idea?
thanks

Some forms of integration only support RSS. We should offer both feed types, not just ATOM.

as is done for pinax-pages, would be nice to support in pinax-blog

At the moment an unpublished blog post can be reviewed by an auth'd user but it would be nice if they could be viewed by unauth'd users at obscure URLs too.

When running the first migration after installing, this error was thrown:

RuntimeError: Model class django.contrib.sites.models.Site doesn't declare an explicit app_label and isn't in a
n application in INSTALLED_APPS.

I had to add django.contrib.sites to the INSTALLED_APPS and set SITE_ID = 1 in settings.py.

Is this related to #69?

the PINAX_BLOG_SLUG_UNIQUE setting when set to True, causes a migration to be generated after install. the migrations that ship with pinax-blog were created with the default settings which is False.

perhaps the migration should be edited to be dynamic based on that setting. that doesn't handle the case where you might want to switch after you have installed but could handle the case where you know what you want from the start.

After a recent upgrade, I'm getting:

NoReverseMatch: Reverse for '('pinax_blog:blog_feed',)' with arguments '()' and keyword arguments '{'section': 'all', 'feed_type': u'atom'}' not found. 0 pattern(s) tried: []

hitting the feed.

The problem seems to be line 171 in views.py:

 feed_url = "http://%s%s" % (current_site.domain, reverse(url_name, kwargs=kwargs)) 

https://draftin.com/documents/69898?token=5fjKKlZ0-AeBzqj_RAftAGdzRzl9VBfBHj5wpSWm_gU

Hi,
I was just perusing the code and noticed a hardcoded value in the RSS feed
https://github.com/pinax/biblion/blob/master/biblion/templates/biblion/rss_feed.xml#L8

I keep getting a
RuntimeError: Model class django.contrib.sites.models.Site doesn't declare an explicit app_label and isn't in an application in INSTALLED_APPS. whenever I tried to run the app.

I followed the exact instructions on the docs, installed deps and did not install creole since I'm using py3.

Any ideas?

Django 1.9.2
Py 3.4.3

We shouldn't support having both urls render the same content.

Perhaps, if we have PINAX_BLOG_SLUG_UNIQUE = True, then the url for SlugUniquePostDetailView is added otherwise the url for DateBasedPostDetailView is added.

Hi,

I have installed the last version of Pinax and I'm getting an error in the admin page. If I try to access /admin/blog/post/ I get aNoReverseMatch u'pinax_blog' is not a registered namespace. I only get this error in the /post/ sections, the rest are working fine.

I have the following code:
At settings.py

INSTALLED_APPS = (
    ...
    'pinax.blog',
...
)

at urls.py
url(r"^blog/", include("pinax.blog.urls")),
I have also done a python manage.py migrate.

Any idea of whats going on? The rest of the sections work perfectly.
Cheers

how to get list of sections in templates blog_list, blog_post?

At the moment we calculate the feed's "updated" as the "published" of the top post but I'm wondering if it should instead be the latest "updated" of any published post. We should make sure the whole feed is sorted by "updated" anyway and use the latest updated for the feed's "updated".

See https://github.com/pinax/pinax-blog/blob/master/pinax/blog/views.py#L166

django master test with py3.3 fails with

ImportError: cannot import name find_spec

because find_spec introduced in py3.4

It's ideal to have titles no longer than 60 characters and meta descriptions no longer than 150 characters.

We should at least provide that help text in the admin, but ideally we should provide a character counter that decrements as you type.

It's easy to get an invalid feed if someone has non-xml html in their content. However, the fix is also easy, just use:

<content type="html" xml:lang="en">
    {{ entry.teaser_html }}
    {{ entry.content_html }}
</content>

to fix #60 we changed content to be html but I've just found a case where I had to make the summary html too. Similar change but to summary element

Currently it's a dropdown with image pks. It should at least have the image file names, but even better would be some type of AJAX image browser in the admin that you could just select the thumbnail.

• add sample markup for markdown in the help text of each image inline (currently just defaults to creole sample)
• make sure that normally linked images work as well so that external images can be used in the markdown

I couldn't install biblion using easy_install with:

easy_install biblion

But I've figured it could be done this way instead:

easy_install https://github.com/eldarion/biblion/tarball/master#egg=0.1.dev10.1

Perhaps this should be added to the docs

Greetings,

As of now pytz is at 2016.6.1 but pinax-blog seems to require pytz==2015.7. Would it be okay to have pytz>=2015.7?

Regards,

SN

Hello people,

i'm having this problem with creole.

I've installed the dependencies, but can't import creole.Parser.

What's going on? Has the library changed?

Image Support

• images: display image set thumbnails
• images: select the one that is primary
• images: use react image set frontend widget

A model like:

class Section(models.Model):
    name = models.CharField(max_length=150)
    slug = models.SlugField(unique=True)

That the Post model would have a FK to instead of just storing integers that are calculated from the position of a section in the list, would make it a lot easier to add a section to the blog in run time.

I realize that this isn't something that happens frequently, but it just seems cleaner.

either in docs or somehow as something runnable via management command:

https://gist.github.com/paltman/73cf67290df3e92790c29934fa8a56e5

I am getting an error regarding the user model used:
blog.Post.author: (fields.E301) Field defines a relation with the model 'auth.User', which has been swapped out.
HINT: Update the relation to point at 'settings.AUTH_USER_MODEL'.
blog.Revision.author: (fields.E301) Field defines a relation with the model 'auth.User', which has been swapped out.
HINT: Update the relation to point at 'settings.AUTH_USER_MODEL'.

This setting defaults to django's default user model, but is preferred to support custom users: https://docs.djangoproject.com/en/1.8/topics/auth/customizing/#substituting-a-custom-user-model

Same issue as django-cms/django-cms#550

At the moment if I want the publication date (e.g. what's shown in the dateline and, in many cases, the URL) to be other than when I actually switched it from "draft" to "published", I have to use the shell.

It would be nice if there was a way to publish with a datetime other than now.

I find it much easier to use CK Editor when building a blog. Would be great if you added that.

I'm also running into a lot of errors when using this so going to give it some time and come back!

By having an API that is compatible with http://wp-api.org we should be able to use all the different desktop and mobile apps for managing blogs and writing posts.

I simply don't understand the rationale for this, when we still have to refer to the image by PK. Why have the relationship at all?

a use case we have right now for the upcoming Pinax blog is to customize the blog_index view to be able to filter by tags (there is site level django-taggit integration)

Pull the contents of this post into some documentation around using pinax-blog:

http://eldarion.com/blog/2015/04/22/using-images-pinax-blog-posts/