Support Forum

Genesis faces a similar thing with SEO settings.  They are there by default, but if you activate another SEO plugin, they turn off.  You could do a similar thing; load support for Arne's plugin, but turn it off if another sitemap plugin is installed.  Personally, if it is documented for an installation (ie, tell users to pick the sitemap plugin that corresponds to the sitemap they are using for their general site), I think that is good enough, and I think it leverages SPF's plugin model.

Mind you, I am not recommending this approach, because I think all sitemap generation for SPF should be in a plugin, with docs telling you to activate one of the available plugins.  If SPF is not going to "ship" with every plugin, it could ship with the plugin you create for Arne's sitemap generator.  The way all plugins are zipped up is fine, but when you finally release 5.0 you don't have to include every plugin in the download as long as there are clear docs on where to get new ones and how to add them.

For SPF to do a check, I wasn't referring to other WP plugins generally, but just SPF plugins.  The way Genesis handles it is to keep a list of SEO plugins that are checked; it's not every SEO plugin, just the big 6 or so.  If one of them is activated, Genesis turns off its own SEO.  Genesis does this check by looking for the existence of certain functions or constants, plugin by plugin.  This model can work in SEO because there are a variety of SEO options.  I would be hard-pressed to name another potential sitemap generator candidate for SPF beyond Arne's plugin and Yoast's WordPress SEO.

Wow, fast response.  I think this is a great change.  Now, I have to step up and plagiarize 2 or 3 lines of code and produce that plugin for Yoast's WordPress SEO. 

I did test it, and the good news it works.  I am running version 4.0 beta 7 of Google XML Sitemaps.  Version 4.0 is required for multisite.  It works a little differently from prior versions, where the sitemap is virtual and broken up, first by month.  There is also a misc.xml file, and this is where the forum posts go.  I got a post on my test forum, and it was successfully put in the sitemap.  So far, so good.

For the to be explored/resolved, let me start by saying I am on build 7101, updated from SVN sometime on Sat around 4 or 5 pm eastern time.  The guest poster that made the post didn't register, so presumably his post would have been held for moderation, right?  But it is in the sitemap.  I figured I would need to approve this post, and couldn't find a way to do it on the backend, so I activated the admin toolbar plugin.  At that point, every refresh of the forum triggers an invalid database query in red in the upper left.  And this is in the error log:

file: /problem-with-post-edit-buttonome/qbg/qbgarage.com/wp-content/sp-resources/forum-plugins/admin-bar/library/sp-admin-bar-components.php

line: 62

function: sp_GetAdminsQueuedPosts

error:

SELECT wp_sfwaiting.forum_id, forum_slug, forum_name, topic_status_set, topic_id, wp_sfwaiting.post_count, wp_sfwaiting.post_id FROM wp_sfwaiting LEFT JOIN wp_sfforums ON wp_sfwaiting.forum_id = wp_sfforums.forum_id ORDER BY forum_id

At the top of the forum, when logged in as an admin, I see that there are 0 posts that need moderation, but if I view the forum as a guest, I don't see the post.

So, why is it in the sitemap if it is held for moderation?  If it is not held for moderation, why is not showing on the front end to guest visitors?  I did receive an email saying the post is awaiting review.  Is the admin bar plugin the only way to moderate posts?