ok - at least got it parsing the blog again - we had to rerun setup to bring the blog/subblogs back to life.
BUT - the blog pagination links and tagged blog content links are STILL not working properly, even after the upgrade to .10 release.
Plus, clicking on the most recent sub blog (named "news" on our site) entry on this page:
claims it is taking you to the content located here:
it shows that article-specific URL properly and everything...
but, if you click on it, you will see it actually is displaying the content from main blog's current entry, which is here:
NOTE: my guess is the reason the install needed to be run to even start the blog parsing again was because pulse is installed in a non-default folder. (We install to a subfolder named "see".) Running the install after the upgrade must have fixed some config file(s) pathing to help pulse understand where it lives. Is it possible all these other blog issues with paginations and tags and incorrect content links cited above are just because some config(s) is/are looking for the default install path rather than the custom path?
for example, i know a year or more ago, pagination wasn't working right for lots of users because of path issues. anyone have some insight as to what/where pagination is controlled and how to verify it is looking at the correct path? any other ideas to fix all these blog issues we are encountering? Thanks!!!