Open Caffeine21 opened 8 months ago
And what is this useless button on both sides..?
We found that the page move URL contains the variable runAggregate=false. If this variable is included, the URL will not work. I'm using the latest version. Is there a way to solve this problem?
![]()
I think this is fixed in the latest npm version but it hasn't been published to docker yet due to an issue with the build.
Then there's no way I can solve it. When will it be updated?
Then there's no way I can solve it. When will it be updated?
As soon as we can fix it. I can't really give a timeframe myself.
Thank you. Have a nice day today
I think it makes sense to keep the issue open until it's fixed right? Unless we can look to another bug that will stay open.
Okay.
facing the same issue for latest mongo-express docker. is there any version of docker where paginantion issue is working.
I have the same issue on the latest Docker image.
same here. Which tag is able to use now?
same here. Which tag is able to use now?
[1.0.0-alpha.4] It works for me.
Is it okay to use alpha image in production ?
When we can expect the solution ? any specific date ?
PLEASE WAAAAAAAAAAKEEEEEEEEEE UUUUUUUUUUUUUUUUUUUP
As I said in October, I'm not able to give a timeframe. I've tried a few times to get the build to work so I could update the docker image but I couldn't figure it out. I don't have a lot of time to put to this project. If someone is able to get the to get the docker build working I can publish the latest NPM version to docker.io.
Changes in #107 / #108 seem to be working. I'm confident that once one of these PRs is merged, we will be able to publish 1.0.2. Thanks @fitztrev for your help!
Pagination working with new tag 1.0.2- Thank you.....
Thank you !
Sounds like it was resolved. 🙂
Page button not created after page 5 It also saves well in the actual database and works well when changing the URL (skip=50), but the page 6 button will not be generated.
Page button not created after page 5 It also saves well in the actual database and works well when changing the URL (skip=50), but the page 6 button will not be generated.
Can confirm. I had this issue with pagination ending at page 2. I have no idea what the exact number of generated pagination links depends on, though (I mean in the context of this bug).
EDIT: This should obviously three pages:
(this is mongo-express:1.0.2
via Docker)
@rtritto is this fixed in the 1.0.3-rc? Looks like you fixed a rounding bug here?: https://github.com/mongo-express/mongo-express/pull/1184
@rtritto is this fixed in the 1.0.3-rc? Looks like you fixed a rounding bug here?: mongo-express/mongo-express#1184
Yes, the fix https://github.com/mongo-express/mongo-express/pull/1184 is in version 1.0.3-rc.
We found that the page move URL contains the variable runAggregate=false. If this variable is included, the URL will not work. I'm using the latest version. Is there a way to solve this problem?