Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'el_pagination_tags' is not a registered tag library. After update to 4.1.1 #175

Open
nick-romano-onlogic opened this issue Nov 20, 2024 · 3 comments

Comments

@nick-romano-onlogic
Copy link

nick-romano-onlogic commented Nov 20, 2024

Hello, thank you for maintaining this plugin!

Unfortunately after updating from 4.0.0 to 4.1.X I'm encountering the following error when loading any page with a tempalte that includes el_pagination_tags.

'el_pagination_tags' is not a registered tag library.

Reverting to 4.0.0 solves this problem.

I did a brief peak through the code changes, and it seems like most of the changes from 4.0.X to 4.1.X are build process related. Should I be loading el pagination differently?

Please let me know if there is any additional information you need.


I'm using Django 5.1.3 with python:3.11.10

Context processors look like:

TEMPLATES = [
    {
        "BACKEND": "django.template.backends.django.DjangoTemplates",
        "APP_DIRS": True,
        "DIRS": [],
        "OPTIONS": {
            "context_processors": [
                "django.template.context_processors.debug",
                "django.template.context_processors.request",
                "django.contrib.auth.context_processors.auth",
                "django.contrib.messages.context_processors.messages",
                "onlogic_core_ui.context_processors.onlogic_ui_theme",
                "django.template.context_processors.media",
            ],
        },
    },
]

'el_pagination' is included in installed apps.

@shtalinberg
Copy link
Owner

Compatible with Django 5.1 will be released as 4.2 version in a few days

@micmarc
Copy link

micmarc commented Nov 25, 2024

I'm having the same issue with 4.1.1 on Django 4.2 / Python 3.10.

@shtalinberg
Copy link
Owner

I reproduced the problem, I'll try to figure it out today and release a fix, it's quite strange...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants