mbi / django-front Goto Github PK

Hi,

During an installation via pip, static directory isn't downloaded.

$ find .env/lib/python3.6/site-packages/front -maxdepth 1
.env/lib/python3.6/site-packages/front
.env/lib/python3.6/site-packages/front/templatetags
.env/lib/python3.6/site-packages/front/forms.py
.env/lib/python3.6/site-packages/front/__init__.py
.env/lib/python3.6/site-packages/front/migrations
.env/lib/python3.6/site-packages/front/south_migrations
.env/lib/python3.6/site-packages/front/tests
.env/lib/python3.6/site-packages/front/urls.py
.env/lib/python3.6/site-packages/front/conf
.env/lib/python3.6/site-packages/front/models.py
.env/lib/python3.6/site-packages/front/__pycache__
.env/lib/python3.6/site-packages/front/views.py

So I have those errors:

[24/Apr/2017 14:48:48] "GET /static/front/css/front-edit.css HTTP/1.1" 404 1685
[24/Apr/2017 14:48:48] "GET /static/front/js/front-edit.default.js HTTP/1.1" 404 1703
[24/Apr/2017 14:48:48] "GET /static/front/js/front-edit.js HTTP/1.1" 404 1679
[24/Apr/2017 14:48:48] "GET /static/front/css/front-edit.css HTTP/1.1" 404 1685
[24/Apr/2017 14:48:49] "GET /static/front/js/front-edit.default.js HTTP/1.1" 404 1703
[24/Apr/2017 14:48:49] "GET /static/front/js/front-edit.js HTTP/1.1" 404 1679

The README deserves more love, maybe write some proper documentation.

Hi

This looks really neat and well put together. Our use case though is that we'd like to edit our own models with inline editing. Is this something you plan to support, or would be interested in?

I hope this is a reasonable place to ask.

Thanks

Will

from this
https://www.django-cms.org/en/frontend-editing/

to this
https://kepler.app/

Rewrite all the JavaScript as vanilla so as not to have to rely on jQuery any longer.

The epiceditor/themes/preview/github.css skin points to epiceditor/images/modules/pulls/dirty-shade.png which doesn't exist. This in turn causes django-pipeline to error when running collectstatic.

If epiceditor is pulled from a CDN like it says in the docs, is it really necessary to include its source and assets in your package?

Alternatively, include the missing image file I guess! 👍

Thanks for an awesome tool as our Chief Marketing Officer (CMO) loves the ability to edit our site's content.

I would be interested in restricting users to what content they can edit. Is there a way to limit what user groups can edit what content? The easiest way might be to create a second shortcut (e.g., {% front_edit "home_title" %}), and let the developer implement a permission feature themselves. For example, the developer could implement django-front on a legal page where legal has a shortcut to edit the content (e.g., the current shortcut) but everyone else can only view the content.

On another note, what features and/or bug fixes do you foresee in the near future to bring your django-front to v1.0?

Hi,

django-front looks like an awesome fit for a project I'm working on! Thanks :)

The only thing I'm missing is the ability to 'pin' content to a specific version. We have an edit/approve workflow that allows a 'normal' user to edit content on their page but it has to be approved by a staff member before it goes live to the world. I'm thinking of storing the PK of the placeholderhistory in our page model and rendering that content, instead of using the default front template tag (with the slight complication that the owning user always sees the latest version).

I just wanted to check if there was another way or if it might be worth trying to add it on a fork and submitting it as a PR?

Hi, thank's for making this Django package, it's really easy to use.
I've been developing my own CMS using this package. but somehow, when I upload an image with over 6MB, I got the following error, and the image can't be saved:

Request body exceeded settings.DATA_UPLOAD_MAX_MEMORY_SIZE.
Bad Request: /id/edit/save/
"POST /id/edit/save/ HTTP/1.1" 400 26

Is there any documentation to set the upload limit when using summernote editor & django-front?

Does it work well with translations, for an example, I have a button with text in it: {% trans "start free trial" %} if I wrap the whole tag trans with {% front_edit "my_button" %} will it work on other languages respectively ?

Alright, I've managed to test it on my own, correcting the question (or making a request of it):

Could you make support for translations ?

Mate, please update it to 0.4.1 because error I fixed 4 days ago is still in pypi and it generates sentry errors :(

Are there plans to add a page in the admin with an overview of all translations? Perhaps the ability to edit translations there aswell?