Arne

You always have to submit it manually to see it here, but Google will process it even if you don’t submit it manually.

Regarding the error in your browser: Make sure you use the right URl, as defined in your WordPress options. If you put “www” there, you also have to submit / view your sitemap with “www”.

Hi,

I’ve tried several things but unfortunately can’t reproduce this behavior. Did you clear the cache of W3TC after changing the settings?

@wnthne: Sorry, that is not possible. Google doesn’t care about the stylesheet, it is only for you to make the sitemap more human-friendly to read.

To solve your issue, are you accessing the sitemap on the same URL like your blog? The domain is very important, for example choose between www and not-www and don’t mix them.

Great, thanks for the feedback.

Oh sorry, somehow I read WPML. Yes, it should work out of the box! Let me know if you run into any issues!

Hi,

after further testing, I think i will keep it at 0. The recommended value for “output_buffering” in the php.ini is 4096, which means that there will be always one output buffer (“default output handler” in ob_list_handlers) and the level will be always at least 1.

http://de.php.net/manual/en/outcontrol.configuration.php#ini.output-buffering

php.ini (default for production)

; Output buffering is a mechanism for controlling how much output data
; (excluding headers and cookies) PHP should keep internally before pushing that
; data to the client. If your application's output exceeds this setting, PHP
; will send that data in chunks of roughly the size you specify.
; Turning on this setting and managing its maximum buffer size can yield some
; interesting side-effects depending on your application and web server.
; You may be able to send headers and cookies after you've already sent output
; through print or echo. You also may see performance benefits if your server is
; emitting less packets due to buffered output versus PHP streaming the output
; as it gets it. On production servers, 4096 bytes is a good setting for performance
; reasons.
; Note: Output buffering can also be controlled via Output Buffering Control
;   functions.
; Possible Values:
;   On = Enabled and buffer is unlimited. (Use with caution)
;   Off = Disabled
;   Integer = Enables the buffer and sets its maximum size in bytes.
; Note: This directive is hardcoded to Off for the CLI SAPI
; Default Value: Off
; Development Value: 4096
; Production Value: 4096
; http://php.net/output-buffering
output_buffering = 4096

To keep the plugin more easier to maintain, only one kind (the sitemap index) is supported at the moment. But it really doesn’t hurt to have it like this!