Flask-blogging

Latest version: v2.0.0.post2

Safety actively analyzes 629564 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 6

0.1.1

- Fixed PEP8 errors
- Expanded SQLAStorage to include Postgres and MySQL flavors
- Added ``post_date`` and ``last_modified_date`` as arguments to the
``Storage.save_post(...)`` call for general compatibility

0.1.0

- Initial Release
- Adds detailed documentation
- Supports Markdown based blog editor
- Has 90% code coverage in unit tests


Compatibility Notes
===================
- **Version 0.4.1**:

The documented way to get the blogging engine from ``app`` is using
the key ``blogging`` from ``app.extensions``.

- **Version 0.3.1**:

The ``SQLAStorage`` will accept metadata and set it internally. The database
tables will not be created automatically. The user would need to invoke
``create_all`` in the metadata or ``SQLAlchemy`` object in ``Flask-SQLAlchemy``.

- **Version 0.3.0**:

- In this release, the templates folder was renamed from ``blog`` to
``blogging``. To override the existing templates, you will need to
create your templates in the ``blogging`` folder.

- The blueprint name was renamed from ``blog_api`` to ``blogging``.

- **Version 0.2.0**:

In this version, ``BloggingEngine`` will no longer take ``config``
argument. Instead, all configuration can be done through ``app`` config
variables. Another ``BloggingEngine`` parameter, ``url_prefix`` is also
available only through config variable.

Page 6 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.