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
How can I reinitialize
on V3?
#396
Comments
My answer from https://stackoverflow.com/questions/58790605/how-can-i-reinitialize-or-destroy-infiniteajaxscroll-v3: You can call Otherwise you can probably overwrite the variable that contains the IAS instance. Pseudo code example: // previous instance
var ias = InfiniteAjaxScroll(/* options */);
// destroy
ias = null
// reinitialize
ias = InfiniteAjaxScroll(/* some other options */); |
Hi @fieg! Thanks for answering! I tried both
|
Can you check if your pagination links are correct, because this looks strange: |
Hi @fieg! Yea it currently works like that, I previously used the is there a way to fix this? sorry and thank you! |
I didnt see this behavior with other implementations, so I guess it something specifics in yours. Do you have a live url so I can check it out? |
@ivanasetiawan I released a new beta version which fixes an scoping issue. Maybe that caused to old url to persist. Can you try the new version and see if it fixes your problem? |
@fieg Awesome! I will update and let you know. |
I think like this: // previous instance
var ias = InfiniteAjaxScroll(/* options */);
// destroy (not really needed)
ias = null
// reinitialize (creates new instance)
ias = InfiniteAjaxScroll(/* some other options */); |
I’m closing this issue for now. Please let me know if it works as suggested. If it doesn’t you may reopen the issue. |
@fieg apology for the delay! It seems to be working properly. Thank you! |
Np, glad to hear it's working! |
Support question
I have been trying to google around but with no succes! there's also no
destroy
?How can I
reinit
IAS on V3? (no jquery, I am usingimport InfiniteAjaxScroll from '@webcreate/infinite-ajax-scroll';
)The text was updated successfully, but these errors were encountered: