Opened 14 years ago
Closed 14 years ago
#2485 closed enhancement (wontfix)
Widgets JS and Pagination JS remove theme div classes
Reported by: | thekmen | Owned by: | |
---|---|---|---|
Milestone: | 1.5 | Priority: | normal |
Severity: | Version: | ||
Component: | Core | Keywords: | JS |
Cc: |
Description
Not all themes will have classes for widgets as 'widget' so the JS sorting options will not work.
widget-groups.js
widget-members.js
Can .widget be removed from both these files.
Same issue with Load More & pagination, for this to work, it has to be inside a class with an id of content.
Can #content be removed from global.js?
Change History (2)
#2
@
14 years ago
- Resolution set to wontfix
- Status changed from new to closed
r-a-y is right - the .widget selector is needed to avoid class conflicts in bp-default.
As r-a-y suggests, if you have a BP theme where this doesn't work out of the box, either add the 'widget' class to the widget selector, or deregister widget-members.js, modify its contents in another js file, and register it separately.
I think the reason why the class "widget" is added to the selector is because if you use the widget on a group or member directory page, both the widget and the directory will be AJAX-ed.
A possible workaround is to deregister the wp_enqueue_script() for the JS files and build your own JS off of the packaged ones.
Look into wp_deregister_script() to get rid of the default JS.