.loadPage() getting floats despite passing whole numbers as its parameters: "currentPage method cannot be set to the value 1.75"

Ask the community
,
11

@yisrael-wix Thanks for your response. I am guessing what you said about masterPage.js is the same as page.js (ie: shop.js) considering I don’t think I have anything in masterPage.js? Sorry to be pestering with you so much.

Background
One of the main reasons I organized it the way I did was because I wanted the mobile version of my site to have the filter elements on a lightbox instead of cluttering up the page. So I copied those elements into a lightbox and essentially a lot of the code that dealt with the filters (ie: loading, onClick, etc.) would have to be duplicated so I decided to just put them in their own page and import them. After doing that I found that it also made the code easier to manage as everything related to certain aspects were in their contained files especially since the Wix editor expands every function whenever I open it making it a bit cluttered.
Follow up
“The problem is that you can’t be sure from which page the Public files are used and it follows that you can’t be sure which components are available on the page.” As long as I am keeping track of those $w I’m fine right? The benefits of keeping things more organized in their own files heavily outweigh the small chance that I try to use the $w on an element that doesn’t exist on a certain page. The only time it happened to me was when it was a mobile page and those elements were hidden in the mobile version; I fixed it with form===mobile or whatever, but in that case I think it would have had an issue even if the code was directly in the page.js file anyways :sweat_smile:.

Regarding the ‘getBoundingClientRect’ issue after using filters/pagination
Steps to Reproduce:

  1. Go to any page greater than 1 (can just click the link)

  2. Filter dataset (pagination still present)

  3. Deselect filter (pagination disappears and throws error)
    I was able to the fix the issue I mentioned in the previous post by just adding a line of code that would execute when the user tries to filter the dataset so that it loads back to page 1 before actually filtering the dataset. However it may be something for QA to look into as I was able to narrow the issue down to it occurring when trying to change $w(’ #pagination ').totalPages.
    Thanks