Kimberly

Hmmmm…the “?” may just be a visual display problem (so not important) since it appears your site isnt having problems accessing those files (it knows where they are).

Curious….in your error_log file in your root directory (so not what you see in the settings page but inside an actual file called error_log — u will need to use a file manager to get access to it e.g. ftp) do you see a line that begins with “PHP Notice: MySQL” (or any line that uses the word “MySQL” in it)?

ALSO can you click the debug function link (on the settings page) and scroll down to “Build Process Results” (located near the bottom of the page). Do you see any variable line that is empty or set to 0?

I ask because as I look through the plugin source code it appears the only real way for it to give the error you are getting is via the _endTime variable being equal to 0 which only happens if an error occurred; and the only place that can happen is when it starts accessing your database.

I am also getting curious about your server side php.ini configuration for running processes (i.e., max_execution_time) or mySQL’s time limits. I will look into that later.

It’s called a “umlaut” represented in html as ä or ä.

Anyway it sounds like your PHP is not set to the correct character set to handle this special character. So I believe you need to convert the character to ISO-8859-1.

If you are comfortable with coding jump into this plugin’s main php file and use preg_replace(“/ä/”,chr(138),$string). The output should be a true umlaut.

Do you have anything in your error_log file?

I will have a look at the author’s source code to see what’s going on.

When you create and publish a post does this plugin successfully create your new updated sitemap with the new post? I am just curious if this problem is only occurring for scheduled posts.

Also, are you using any page caching plugins? I know a plugin called Quick Cache has an issue with scheduled posts which i had to provide a patch fix for other users to use which then resolved why XML sitemap wasnt working (in their specific case).

Sounds like all of you are having problems due to your server not supporting loopback requests.

Ok here are two files i’ve written for ya to help test if your server is functioning correctly.

1. Change {SITE HOST NAME} in the code (two spots).
2. Place them both on your server.
3. Run LoopbackTest-Call.php from your browser.

LoopbackTest-Call.php:

<?php
	$ch = curl_init();
	echo "<b><u>Server: ".$_SERVER["SERVER_ADDR"]."</u></b><br/><br/>";
	curl_setopt($ch, CURLOPT_URL, 'http://{SITE HOST NAME}/LoopbackTest-Reply.php');
	curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
	$html = curl_exec($ch);
	echo "This php file attempts to test Loopback Requests by calling: <b>http://{SITE HOST NAME}/LoopbackTest-Reply.php</b> which resides on the same server<ul><li>If the response fails the display shows \"<u><b>FAILED!</b></u>\" and means Loopback Requests are not working on this server.</li><li>If the response is successful the display shows \"<u><b>SUCCESS!! Loopback Requests Work!</b></u>\" and means Loopback Requests are working on this server.</li></ul>Response: ".(strlen($html)==0?"<b style='color:#FF0000'>FAILED!</b>":$html);
?>

LoopbackTest-Reply.php:

<?php
	echo "<b style='color:#00FF00'>SUCCESS!! Loopback Requests Work!</b>";
?>

Let me know the results. If it says FAILED then i will let you know what you need to do.

1. As Josh says, check the very last lines of your page source to see if you spot QuickCache’s special comment lines

2. Check your error_log file for any qc errors

3. Check the /cache folder to see if a unique qc-c-* file is/was made (though if #1 isnt present then it’s a good indication no qc-c-.. file exists)

Curious…so your css files aren’t loading? Can you provide a link to your site. I’d be happy to have a look and run my debugger tool on the page to verify what the css is/isn’t doing.

I thikn you can just append &qcAC=1 to a file and QC will create a cache for it. However that might only work for not caching..havent checked his code to see how versatile that option is.

Besides that you could go inside the admin-ajax.php file and add define(“QUICK_CACHE_ALLOWED”, true); but that would involve messing with the core files which isnt recommended but i admit i’ve messed with the core many times (but i know what i am doing). Again, i havent tried that before.

Replace line 667 which currently shows:

$path = $base_path.$location;

with this:

$path = preg_replace("!/{2,}!","/",$base_path.$location);

That will fix your problem.