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

Major Issue with Jazzmin Detail Page #498

Open
VirajPoriya2202 opened this issue Jul 5, 2023 · 1 comment
Open

Major Issue with Jazzmin Detail Page #498

VirajPoriya2202 opened this issue Jul 5, 2023 · 1 comment

Comments

@VirajPoriya2202
Copy link

I hope this email finds you well. I am writing to report a major issue I have encountered on the details page of Jazzmin. I will provide an example to illustrate the problem.

Suppose I have a category model with a subcategory. In my implementation, I have registered the category and included the subcategory as an inline model using inlines = ['subcategory', ]. The subcategory model has a dropdown or choice field.

The issue arises when I perform the following steps:

  1. Add five subcategories to the dropdown.
  2. Remove any [subcategories] from the middle.
  3. Attempt to add a new subcategory.

Upon adding the new subcategory, the dropdown or choice field reloads without the correct CSS formatting. As a result, the appearance of the dropdown is distorted and visually unappealing.

I kindly request your immediate attention to this bug as it significantly impacts the user experience. It would be greatly appreciated if you could address this issue promptly, as it is hindering the functionality of Jazzmin's details page.

Please let me know if you require any additional information or if there are any updates or patches available to fix this problem. Your expertise and support in resolving this matter would be invaluable.

Thank you for your prompt assistance. I look forward to hearing from you soon and having this issue resolved as quickly as possible.

Attachment :-->https://ibb.co/mbChtCh

@kevalrajpalknight
Copy link

Hey @VirajPoriya2202 Thanks for reporting this issue. I believe this is because when select element is added to the DOM, it's not initialize with the select2 instance. @farridav I would really appreciate if you could let me know if this issue is taken care by some, or I am really looking forward for such contribution.

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

2 participants