msmeritt

Nice to hear from you! I’d prefer to talk detailed specs offline. But I can give you a general answer to your question.

The HTML is to be coded a particular way, and history has shown me that, with this thing I’m talking about, the way it needs to be coded can change over time. This kind of coding will be on many, many posts. Putting HTML directly into posts is just what I’ve done in the past — and when the coding method changes, I’ve had to go back to every single post to make changes. I don’t want to have to do that anymore. I want to be able to change the plugin code once and have all the posts change automatically as a result.

Feel free to get in touch with me via http://marksmeritt.com/connect/ if you’d like to discuss further. Thanks again for writing.

Will and others, thanks for replying here. I thought it useful to provide some response here for posterity, for others who may want to use and better understand MicroID, ClaimID and this plugin.

I certainly do understand now — and I didn’t earlier — that MicroID is properly implemented inside those div tags and that they serve purposes beyond ClaimID. So that certainly helps illuminate things here.

I personally would love a plugin that put the proper ClaimID verification coding into all of a site’s pages, not just home and author pages, and not just other MicroID usage. Whether that’s consistent with your intentions/purposes for your plugin, that’s certainly for you to decide, and I wouldn’t hold it against you if you chose not to build it in, I’d just keep looking elsewhere for broader ClaimID verification functionality.

In the meantime, I should mention that, even after upgrading to your new version 1.1, I’m still experiencing all the same issues and don’t see the verifiability that you mentioned 1.1 should have:

Sites that use static Pages as the home page do have the same MicroID calculated as ClaimID, but not in the head/meta tags, so unverifiable by ClaimID though you say it should verify.

Sites that show latest posts on the home page have no MicroID at all for the page itself, only for each of the individual latest posts within. So can’t compare ClaimID calculation, and also certainly unverifiable by ClaimID though you say it should verify.

I know now that the plugin isn’t currently intended to provide ClaimID verification beyond home and author pages. Re: calculation, though, while I see a match between plugin and ClaimID for single posts, I continue to see mismatches between plugin and ClaimID for non-home static pages. As you requested, I’ll contact you directly about that as an FYI.

Thanks for your help!

Oh, I figured it out via an alternate widget and the bookmark tags, lovely, thanks!!

Thanks for responding.

The trac.wordpress.org link says Not Found — what is/was there?

I looked at my sitemap-ui.php and in it I see a reference to wp_load_alloptions. Just to see, I changed it to get_alloptions() as you noted, but when I then rebuild manually, I still get the user_trailingslashit() error noted above.

Technically, add-on domains are subfolders of the main hosting account, so I assume you’re referring only to subfolders that truly act only as subfolders and not also add-on domains.

I’ll go back to the host and see if they may have anymore insights. However, I also had thought that there might be a problem in the upload somehow, though since the installation went fine and I am able to fully navigate around the dashboard, if there is an upload problem, it’s definitely something not so obvious.

So the question would be how to handle any re-upload given that the thing is now installed. I’m not upgrading so couldn’t follow those instructions. Is it safe to literally just upload everything all over again on top of what’s there, overwriting? Should I delete everything that’s there first and then reupload, or would that somehow mess things up since it’s already installed? Some other thing to do?