crosa

Likewise – one of our properties relies heavily on this plugin for their editorial workflow. If the fix is as simple as what is above, I’m hoping it will be implemented quickly.

Hi RavanH:

Thanks for following up. I will definitely take a look.

We were able to put in a workaround last week, which looks similar to what you are doing in the dev version. The edit was in xml-sitemap-feed/xml-sitemap.php , and I changed the XMLSF_NEWS_POST_TYPE from ‘post’ to ‘any’ as follows:

if ( !defined(‘XMLSF_MEMORY_LIMIT’) )
define(‘XMLSF_MEMORY_LIMIT’, ‘256M’);

if ( !defined(‘XMLSF_POST_TYPE’) )
define(‘XMLSF_POST_TYPE’, ‘any’);

if ( !defined(‘XMLSF_NEWS_POST_TYPE’) )
define(‘XMLSF_NEWS_POST_TYPE’, ‘any’);

if ( !defined(‘XMLSF_NAME’) )
define(‘XMLSF_NAME’, ‘sitemap.xml’);

if ( !defined(‘XMLSF_NEWS_NAME’) )
define(‘XMLSF_NEWS_NAME’, ‘sitemap-news.xml’);

After making the change, an /audio custom post type story indexed for the first time, so I think we’re good for now.

Not sure about the error above, but version 2.5.1 is quite busted (see other messages in this forum) – revert to the pre-2.5 version and see if that clears things up.

This upgrade to 2.5.1 is stripping authors and not allowing them to be re-added.

I also no longer see the ability to manage authors in quick edit.