-
Notifications
You must be signed in to change notification settings - Fork 191
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
placeholder without django admin interface?!? #85
Comments
Hm. I see that i can add/edit placeholder with the djangocms frontend. But not in the admin. So the workflow is:
Is this right?!? |
What's about this: if ``BLOG_USE_PLACEHOLDER==True`:
Maybe auto add always one "TextPlugin" to a new created article? btw. the information from #52 (comment) should be added to the README ;) |
The workflow is dictated by django CMS. |
Please have a look at above PR |
OK... But IMHO it is a good idea to help the users now ;) What's about this: if Currently it's very circuitous to create a blog article if placeholder are used. |
This can be configured using |
Thanks! I add now this:
Maybe a good idea to add some needfull example settings into README? btw. i think the "went hurdle" is very high ;) |
Some more workflow suggestions and questions: the blog post category is a needed field. But the field is under collapsed "info" tab :( And IMHO it's a good idea to redirect after blog creation. I added this:
to PostAdmin() class. But this only work, if the normal django admin backend is used to create a new blog entry... If the djangocms frontend is used, the redirect will not work. Think because of JavaScript "inline" usage... it's a pity |
* move needed category to the top * move auto slug field into collapsed info tab see: nephila#85 (comment)
I really dislike automatic redirection, especially from inside the admin to the frontend. A proper solution must be implemented at the cms level so all the application can benefit |
Yes, redirect from admin backend to frondend is confusing. But the normal you start a new blog post in the djangocms frontend, isn't it? |
Sorry, that i ask again... Currently it works in this way:
The boring things here are:
I don't know what the future plans in djangcms are to simplify this in the blog app... What's about to display non-published blog entries, for users who hat the permissions to edit blog posts? |
I'm a little confuse...
The is
BLOG_USE_PLACEHOLDER
it'sTrue
in my case (and by default)...But it seems that there is no interface to create/edit content via placeholder.
I see only the translated "abstract" field in admin.
So the detail view has always no content, because
{% render_placeholder post.content %}
will always result in no content.The text was updated successfully, but these errors were encountered: