clintecker / django-chunks

Think of it as flatpages for small bits of reusable content you might want to insert into your templates and manage from the admin interface.

Welcome to my Github! 😎

• 🔭 I’m currently working on React/[Java|Type]script/Firebase/Crypto Stuff for @generalgalactic
  • Galactic Camera, What is Galactic Camera?
  • NFT Experiment: Floppydisk.xyz. The Drop, Technical Write-up, OpenSea Collection.
  • Sign-In with Ethereum (SIWE/EIP4361) Node/JS imeplementation.
• 🌱 I’m currently learning about Ethereum, Solidity, NFTs, Crypto
• 💬 Ask me about python, distributed systems, identity, auth, software architecutre, VueJS, Firebase, Solidity, NFT contracts
• 📫 How to reach me: email, Instagram, General Galactic Discord
• 😄 Pronouns: he/him

django-chunks's Issues

upload your package to PYPI

Please, we're using chunks in many projects, and it would be great if we can download it with setuptools.
Thanks!

cache key can be invalid

The Chunk key field is a CharField, which can take almost any kind of character data, including Unicode, spaces, whatever.

In the templatetag, the chunk key is used as part of the cache key. If using memcached with python-memcached, even spaces are illegal in a cache key. This causes 500 errors.

My first solution was to slugify the chunk key before using it as cache key. This works, but raises the possibility of two overly-similar (but still unique) chunk keys slugifying to the same cache key and stomping over each other's cache. The only way this would really work is if chunks gained an actual SlugField with uniqueness enforced.

So my second solution (found in my fork) was to rip out the direct caching support entirely. IMO there's no reason for django-chunks to have its own (buggy) cache support, when its just as easy (and more flexible) to wrap calls to the chunk tag with Django's built-in template fragment caching tags.

Python 3 support

added support for python 3 here:

31fe485

what about context?

Is it capable of rendering context variable?

If {{ chunk name }} then do something?

Anyone know if this is possible? I've messed around a bit and can't seem to get anything to work so I assume it won't work but was curious if anyone has done something like this?

{% if chunk_name %}
do something
{% endif %}

DJango Chunks distribution not found while deploying it on heroku

Failed to install on Heroku server :
Error No distributions at all found for django-chunks (from -r requirements/base.txt (line 22))
Storing debug log for failure in /app/.pip/pip.log

Chunks are cached forever by default

If you don't pass a cache timeout to {% chunk %}, the chunk contents will be cached forever (or until the cache runs out of space). I can't see how this would ever be desirable behavior. The chunk is being stored in the database so it can be modified at will, yet the default behavior prevents that from taking effect. I'd recommend merging in carljm/django-chunks@8dcf287e to rip out the caching support altogether. Users who want to cache the chunk can wrap it in {% cache %}.

Alternatively, the Chunk model should clear the cached value on save.

Allow chunk content to included (like the {% include %} tag)

It would be nice to be able to include a chunk in a similar fashion to the way the {% include %} tag works. I've created a patch that adds an additional tag to django-chunks, {% include_chunk %}, which can be use like so:

{% include_chunk "some_chunk_name" %}

The diff can be found here