Post Loop BUG REPORT

I would like to submit a bug report regarding the post loop inside of the tag div composer.

I have a page with a category’s posts and a dozen of ads. In order to better arrange everything, I attempted to split the content into three logical sections, and insert ads in between those. In the previous format I had a Category Grid 2 on top (entire row), then a full row banner, and then a 2/3 post loop on the left, and a 1/3 ads column on the right.

In the new format I had a 2/3 Category Grid 2 on the top, and a 1/3 column on the right, with one ad box on the top of the column, and a post loop with an offset of 5 posts, and a limit of 2 posts just below that. The remainder of the page remained as before, with the only difference being that the post loop under the full row banner, I set the offset to 7 this time, to compensate for the introduction of the previous post loop.

No matter what settings I configured the second post loop after that, the post limit would not change; it was being affected by the upper post loop, and was limiting the posts to 2 per page for the lower post loop as well. Obviously affected by the upper post loop, and I tried everything in my powers, including deleting the lower post loop, and saving, and reloading, and re-inserting a new post loop and configuring it anew, clearing the cache memory, clearing the cloudflare cache memory, firing up a private browser to test without browser memory, and what not. I even tried using a post loop 2 in place of the post loop, for both the upper and the lower positions alternatively, so as to make sure no rules of the type A affected the instance of the type B. Everything was useless. Every time the lower post loop would be affected by the upper post loop’s settings.

As soon as I deleted the upper post loop and introduced a couple of ads in its place, the problem with the lower post loop went away.

I thought somebody else could benefit from my experience, and perhaps bringing it to your attention you could come up with a fix in the meantime, hence my posting this here publicly. I don’t really need any further assistance with this in my case for the time being, as I have come up with a workaround that allows me to move on.

Thank you.