Not working with Django 4.1
See original GitHub issueDjango has removed de installed property from the Model Options object (_meta). And will produce the following error when using Django Activity Stream
AttributeError: 'Options' object has no attribute 'installed'
this comes from actstream/registry.py
line 60 (version 1.4.1).
See this commit from Django https://github.com/django/django/commit/8e3b1cf098018b4632de63c359ef6d761e92ec04
Issue Analytics
- State:
- Created a year ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Troubleshooting — Django 4.1.4 documentation
Troubleshooting ¶. This page contains some advice about errors and problems commonly encountered during the development of Django applications.
Read more >Django 4.1 release notes
Django 4.1 release notes¶. August 3, 2022. Welcome to Django 4.1! These release notes cover the new features, as well as some backwards ......
Read more >django 4.1 polls tutorial, all done Admin working fine but index ...
No url at http://localhost:8000/ address is expected behaviour, where you want to go is http://localhost:8000/polls/ .
Read more >PyCharm - Step 4. Create and Run your first Django project
How to create and run a simple Django application (creating project; running Django server; configuring database; creating models, templates, views; ...
Read more >Offline PDF and ePub doc links for Django 4.1 do not work
The links to download the offline copies of Django 4.1 documentation for. PDF and ePub are not working. The HTML ZIP works with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For those who also face this before they make django 4.1 release and still want to use django 4.1, maybe this could help:
i just pushed the change to main branch. going to make a django 4.1 release