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
ajaxify pagination (Trac #2596) #2596
Comments
Milestone changed to |
trac user Purus wrote on 41816537-03-25 Isn't this to be covered by blacktooth's work on ajaxify? Just curious to know.. :) |
brettp wrote on 41817164-02-06 His work included ajax pagination but hasn't been pulled into core yet. |
trac user Purus wrote on 41817234-09-24 If the target of blacktooth's ajaxify is 1.8.2, the milestone for this ticket can be changed to 1.8.2. Is that okay? |
ewinslow wrote on 41819720-11-26 Ajaxify is not going to be pulled in for 1.8.2. blacktooth added a lot of great features, but I think we still need more clarity on The Right Way to do things before we pull all of that in. |
ewinslow wrote on 41819722-03-04 Also, we're trying to avoid adding new features in bugfix releases. |
ewinslow wrote on 42516853-04-01 Hey, sem. Thanks for being willing to take this on. I think I'd like to write a design doc so we can really figure out what the appropriate approach is. Care to start one? |
trac user sembrestels wrote on 42521171-12-02 I began the page in the community, in the Elgg Feedback and Planning group. http://community.elgg.org/pages/view/918176/ajax-pagination--bundled-plugin-in-19 I ask for access to repository to work in this plugin. Except on that, I will continue doing pull requests as usual. |
Milestone changed to |
Milestone changed to |
This has been open for years with no meaningful discussion here so I'm tempted to close, but people still ask for this all the time on the community, so I'll consider that activity enough to let this live. |
To move forward on this all our JS has to use event delegation and/or the Drupal-like "behaviors" proposal I put forward. I'm all for making the 2.x cycle all about front end improvements so let's leave this. |
Original ticket http://trac.elgg.org/ticket/2596 on 40830035-06-18 by ewinslow, assigned to unknown.
Elgg version: 1.7
With a few modifications to core, we could make this work via ajax.
an entity list (include navigation) would have to be wrapped in a div with a user-specified ID.
a handler is added using $('selector').live('click',...) to the pagination navigation links.
this handler calls $('#internalid').load(href + " #internalid") to refresh the contents of the entity list, including the navigation.
This requires some modifications to core so that ID's can be specified for these lists and so they can be wrapped in div's to sandbox the .load() call. On the upside, it degrades quite gracefully.
The text was updated successfully, but these errors were encountered: