Custom Post Type causes CSS class name conflict
I have a custom post type with the slug of image. When I configure Admin Columns for this custom post type, it adds a class called ac-image to the <body> tag.
The problem here is that this class is already defined for another function in the AC CSS and now these styles are being applied to the <body>. The conflicts are mainly visual, however it does apply an overflow: hidden which prevents us from being able to scroll in the main window, which isn’t ideal.
I have worked around the issues for now, but it would definitely be a good idea to prevent these conflicts in a future release so that the work arounds are not necessary.
Thanks!
Thanks for your input.
Yeah, the body class might not have been the best prefix choice :)
I’ll create a fix for Image for the next release, but also try to find a more sustainable fix by finding another prefix for the body class. But unfortunately, this must work backward and also must change in all our integration. Anyway, the issue is noted and I’ll look for a fix.
You must be logged in to reply to this topic.