Eric Rasch

And I should note, again, downgrading to v1.4.13 on this site brought the sitemap back. I manage a lot of sites and this was a different one on its own server than the ones I was dealing with this morning.

@jpinches: Thanks for posting that. I tried it, but it didn’t work me… still a blank page.

For those that do want to try @jpinches code, here’s what you should add to the .htaccess:

<IfModule mod_mime.c>
  AddType application/xml  atom rdf rss xml
  AddType text/xsl         xsl
</IfModule>

<Files "xml-sitemap-xsl.php">
  Allow from all
</Files>

I was also getting sporadic 404’s on some of the sub-sitemaps (like post-sitemap3.xml). I tried working with the .htaccess file using the 404 fix, but that didn’t work. In the end, I had to fix the 404’s by increasing the ‘Entries per page’ on the Sitemap settings to 9999.

I have a number of sites I’ve recently upgraded and have this same issue. Rolling back to version 1.4.13 worked.

I know this doesn’t help, but I had the exact same issue and reverted just as artfool did.

I’d show you the live site, but after running for 2 days, the server just went down citing this plugin as the cause, so I had to disable the plugin to keep the server running.

WP v.3.3.1 and 14 visits in the Adv. Metrics.

No, nothing like that. Just a normal LAMP stack.

I upgraded the plugin and re-ran the test today and I’m basically getting the same results. Here’s a screenshot of the P3 report (between today/yesterday after removing 1 active plugin): https://skitch.com/ericrasch/ghf76/p3-er-test

Nope. Not running it on the local.

It works now. I had to disable and re-enable the plugin, then upload the .profiling file again, then set the file to 666 all before I accessed the plugin setting page.

Thank you!

Correct. If I click on the ‘fix this’ button, it takes me to the FTP credentials page with this message at the bottom…

Why am I being asked for this information?
P3 cannot write to this file:
/PATH/wp-content/plugins/p3-profiler/.profiling_enabled
P3 needs to write to this file to toggle profiling for your site. If you want to fix this manually, please ensure the file is readable and writable by the web server.

So, our sites have FTP disabled completely. Does this mean we can’t use your plugin? Is there any way around this? I tried uploading the .profiling_enabled file and made it writable, but the plugin still won’t work.

I was having this problem until yesterday. I even tried downgrading to many older versions of Magic Fields.

The final solution for me was to Network Deactivate (I’m running Multisite) the plugin Post Type Switcher. To find that, I first disabled all my plugins, and when that didn’t solve it, I went through and Network Deactivated all the rest of the plugins.

NOTE: Post Type Switcher is still active on the website, but when I ‘Network Activate’ it, Magic Fields stops updating my posts.

So, my suggestion is to disable your plugins and see if Magic Fields starts working again regardless if you’re running Multisite or not).

Sorry about breaking the Forum rules…

Here’s a link to the code I posted @ pastebin: https://pastebin.com/0ttqaYjZ

I’m also using the code mentioned by Ryan Riatno, and I can get it to list all the custom taxonomies, but it will list all the custom posts under each taxonomy, rather than just listing the 1 or 2 custom posts that actually belong under the custom tax.

For example…
Tax X
Custom Post 1
Custom Post 2
Custom Post 3
Tax Y
Custom Post 1
Custom Post 2
Custom Post 3
Tax X
Custom Post 1
Custom Post 2
Custom Post 3
Tax Z
Custom Post 1
Custom Post 2
Custom Post 3

Whereas what I want is…

Tax X
Custom Post 1
Tax Y
Custom Post 2
Tax Z
Custom Post 3

Here’s my code…

[Code moderated as per the Forum Rules. Please use the pastebin]

I’m willing to try anything. I’ve tried about 10 different ways to write this, but they either give me the same results, or no results at all.

FYI: On another site I ran into the ‘Wrong Datatype‘ error in More Types, and this thread fixed that error, as well.