Updated page-builder install manual #324
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* travis: Fixed test issues with fixto.js Use a bytestring for the file content use mezzanine that works on 1.4 don't need the patched mezzanine any more always use the most recent minor versions of django
Django-compressor 1.3 introduces the filter class functionality that django-pyscss relies on. django-pyscss doesn't require that version of django-compressor because it is compressor agnostic. It might be nice to add an error into django-pyscss if django-compressor < 1.3 is installed though.
Require django-compressor>=1.3 for django-pyscss.
- Use the grab/grabbing cursors instead of pointer - Only draggable widgets use a special cursor
This way, you don't have to fetch the page object when you want to put a link in the search results.
This allows the UI to update based on new data after the move. For example, widgets can change their `display_name`s based on their tree position.
Conflicts: widgy/contrib/page_builder/models.py
With the introduction of mezzanine.pages.context_processors.page, there was a change in how PageMiddleware and the page view interact which broke the PreviewView and HandleFormView in widgy_mezzanine. This commit fixes the problem in a way that works for both pre- and post-3.1.2 Mezzanine.
Updated quickstart to cover south migrations with easy_thumbnails
Allow RichTextPage in the Admin
The previous implementation of class_to_json wasn't calling css_classes because you can't call property methods without an instance. I added a method get_css_classes which works on both instance and classes. This allows widget creators to set css_classes on their widgets and for that to work in both to_json and class_to_json.
Fix widgy_mezzanine preview for Mezzanine==3.1.2
Change Button's css_classes so that it doesn't confict so hard.
Added ability to add classes to FormField Input - added tutorial
This will happen when the connection is reset, for example.
Recommend installing from PyPI in quickstart.
If CSRF_COOKIE_HTTPONLY is set to True, Widgy won't be able to extract
the csrf token from the cookie. Instead we can extract it from the input
that is output by the {% csrftoken %} template tag.
Conflicts: widgy/contrib/page_builder/forms/__init__.py
This was the original intent, as Widgy is usually used with the admin site.
* preview-redirects-to-login: authorize_view should only allow staff, not any authenticated user. accomodate django 1.4's handling of LOGIN_URL Previewing when not logged in should redirect to login
It's not required and only causes problems (lazy admin registration).
More informative messages for compatibility errors
mezzanine.boot shouldn't be recommended
Previously, find_media_files was using the set order of the filenames, which will differ between processes on Python 3 and may differ on Python 2 with the -R flag.
The base widgy migrations had references to ReviewedVersionTracker, which is not part of the base widgy install. This commit changes the dependency to VersionTracker instead, which is part of the base widgy install.
`south` is no longer installed as a part of `django-widgy[all]`. This patch removes it from the tutorial.
…rMigration Remove dependency for ReviewedVersionTracker in migrations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.