staze

lol! You fixed the preg_match, but not the preg_replace…

The block should look like:

$pluginurl = plugin_dir_url(__FILE__);
if ( preg_match( '/^https/', $pluginurl ) && !preg_match( '/^https/', get_bloginfo('url') ) )
	$pluginurl = preg_replace( '/^https/', 'http', $pluginurl );
define( 'WPSEO_FRONT_URL', $pluginurl );

(sorry I keep giving you work. =P)

This works…

preg_replace( ‘/^https/’, ‘http’, $pluginurl );

Correction, it does not fix the problem, it just changed it. I hadn’t removed the sitemap created by “Google XML Sitemap” before testing now that I have, it’s still not working right.

Now I get “Error loading stylesheet: A network error occured loading an XSLT stylesheet:http://www.staze.org/css/xml-sitemap.xsl” (which makes sense, since the xsl exists within the wordpress-seo css directory.

Since this should be something more like:

http://www.staze.org/wp-content/plugins/wordpress-seo/css/xml-sitemap.xsl”

I just edited the sitemap myself and this does indeed allow the XSL to load.

I doubt it’s the fact I don’t have WP_PLUGIN_DIR set since if that was the case, I’d think it would be something like http://www.staze.org/wordpress-seo/css/xml-sitemap.xml

Any thoughts?

That’s just fine, thanks!!

I did. And to be double sure, I just removed the existing sitemap, and regenerated again. Same result.

It appears that wordpress is doing a replace of all http:// with https:// in config options when force_ssl_admin is set, so that things work when logged into the wp-admin site (and don’t generate a bunch of errors about some content being insecure).

might it be better to just regrab that value from wp-config.php when generating the sitemap, to avoid this? I’m not sure how Google XML Sitemap does it, but it does not have the same issue. =/

Thankfully, the sitemap is visible to google, so it’s really only an issue if I try to look at it from a web browser (or something that actually uses the xsl file).

ah, cool.

I wait with baited breath. =) btw, will you be enabling updates from wp.org with this release?

Thanks for the heads up on wp_plugin_url… as it doesn’t seem to be documented really anywhere, I had no idea it was actually available. It fixed another issue I was having that was purely cosmetic, but still annoying.

As a note, wordpress-seo never prompted to update from 0.1.3 to 0.1.4. I had to download the new plugin, and move it onto the site. Just to make sure things went right, as well, I disabled and reenabled the plugin to make sure something wasn’t wedged.

So, I managed to fix the CSS issue by removing the stylesheet from “All Templates”. Re-adding it to each specific template would probably resolve this.

More importantly, seems that HTML minification breaks the wiki since it collapses the newlines between list items, so it creates one big list.

Would be good to have a way to exclude pages/directories from minification.