First up, I’ll say if you found a way that’s working and you’re happy with, go with that. If you liked what you had before my comment, I say stick with it.
Setting “has archive” to true treats the post type as just that, as having an archive. Out of box WordPress gets many archives, for example the “post” post type gets one, where you have the pagination there. It uses the index.php
template file by default.
Any category/tags that you view where you see posts with just those cats/tags, those are archives as well. Both use template files like category.php
and tag.php
etc. All the traditional WordPress as a blog files.
Thus you can create post types that do the same. They’d use the archive.php
template file. Hence why you saw “Blog Archive” as in this case it was the archive for the “Blog” post type you created.
Now, you are using a page builder provided by the theme, and it’s using a custom WP_Query within the page, to fetch the ‘blogs’ post type here, and very likely using standard pagination functions in the generated output. Not a bad thing in theory, but provides some potentially unexpected challenges. I have a longer documentation page at https://docs.pluginize.com/article/cleanly-done-pagination-with-custom-wpquery-objects/ that goes into the details more including recommended functions/code, that would be possible if this was a custom theme.
However, you’re beholden to Newspaper theme and the code that their block uses. Part of why if you liked what you had when you got it working, I still recommend going back to that.