cmsplugin-filer | longer maintained , see README
kandi X-RAY | cmsplugin-filer Summary
kandi X-RAY | cmsplugin-filer Summary
DEPRECATED, this project is no longer maintained, see README for more information.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Get thumbnail options .
- Moves thumbnail option to FSM .
- Moves thumbnail option to the given CMS .
- Render the plugin .
- Create an image plugin .
- Rename tables .
- Prefetch the queryset .
- Return the template to render .
- Return all files in a folder
- Configure data .
cmsplugin-filer Key Features
cmsplugin-filer Examples and Code Snippets
Community Discussions
Trending Discussions on cmsplugin-filer
QUESTION
Since the cmsplugin-filer-*-plugins are deprecated with django-cms 3.5, I need a way to keep my plugins with moving them to the newer djangocms-*-plugins.
I am using the cmsplugin-filer plugins FilerFile, FilerFolder and FilerImage. Also I got a custom plugin which inherits from FilerImage. I need to move those to the newer djangocms-file-file, djangocms-file-folder and djangocms-picture without losing my plugins / data.
...ANSWER
Answered 2018-Dec-11 at 08:08After some time working on a migration I came to this solution: https://gist.github.com/wfehr/86ac31e8e263b872b746cc721662251e
The gist provides a migration to move the data between the said third-party-apps and keep alls the plugins/data and change them to the supported ones.
I hope this will help someone facing the same problems:)
(The migration code itself may not be the perfect solution, but it gets the job done)
EDIT:
The linked migration can be used in any application of yours. Just put it in there as the next following migration, for example you have already "0011_added_new_model.py", then put in the file as "0012_filer_deprecation_move.py". Then you have to add the migration 0011 in the dependencies, as seen in other (default) migrations.
TLDR: The above migration is a single, standalone migration. It is called as any other migration with python manage.py migrate [app] [migration]
and you can put it in "any" app you want (where it makes the most sense to you).
QUESTION
I have a website, currently running with Django==1.8.6 and Django-CMS 3.0.x (running through upgrades at the moment).
My users can not edit any of the frontend plugins. At the moment I am sure that this is not only true for my custom made plugins, but for ones that come with Django-CMS as well. As a test I have made a new User with all rights and staff status (no superuser). But also this user can't edit or add plugins.
For my search I have found this: https://github.com/divio/djangocms-text-ckeditor/issues/78
I also tested the solution given there as I am using ckeditor, but I don't have an entry for text, so this:
...ANSWER
Answered 2017-Jun-07 at 13:00The answer is after some debugging the permissions.py of the cms, that my sitepermissions where not set properly in the database. Resetting thos in the backend solved the problem.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cmsplugin-filer
You can use cmsplugin-filer like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page