darelparker

Try adding the following to .htaccess if you are hosting with 1and1.com:

AddType x-mapp-php5 .php

Works great! Thanks for the update!

Oh thank you, I’m good. I copied over the previous version from one of my other blogs. Back to normal.

Same issue here. Had to ftp in and delete the plugin folder. Any news on the next update? I love this plugin.

Just got this error on the stats page:

“Goshdarnit!

Something has gone wrong with our servers. It’s probably Matt’s fault.

We’ve just been notified of the problem.

Hopefully this should be fixed ASAP, so kindly reload in a minute and things should be back to normal.”

Strange days in WordPress land lately…

Giacom8, thanks for that fix! Worked here too.

In related news, the WP Stats Dashboard, which relies on WP Stats, is working fine on all my WordPress installations.

I’m having the same problem on a couple of my blogs. I can’t find any pattern related to plugin conflicts, caching plugins, etc. On most of my blogs, Jetpack works fine. But on others, even with identical plugins and configurations, I’m still getting the old stats layout.

I even deleted the old WP Stats plugin to avoid conflicts and corruption. Hopefully Automattic will get this sorted out soon.

I’ve been seeing this error intermittently on several of my blogs since last week. If I had to guess, I’d say it might be caused by a jump in wordpress.com’s server load since the upgrade to WP 3.1. It seems like the statistic image is generated (not cached) each time a page is loaded while the admin user is logged in.

I could be wrong, but a page refresh usually fixes the problem on my end.

Open header.php and look for the following:

<script type="text/javascript">
jQuery(window).load(function(){
		jQuery("#featured-content").loopedSlider({
			autoStart: 3000,
			slidespeed: 500,
			containerClick: false,
			autoHeight: false
		});
});
</script>

Change 3000 (3 sec.) to the duration in milliseconds that you prefer.

Open header.php and look for the following:

<script type="text/javascript">
jQuery(window).load(function(){
		jQuery("#featured-content").loopedSlider({
			autoStart: 3000,
			slidespeed: 500,
			containerClick: false,
			autoHeight: false
		});
});
</script>

Change 3000 (3 sec.) to the duration in milliseconds that you prefer.

Open header.php and look for the following:

<script type="text/javascript">
jQuery(window).load(function(){
		jQuery("#featured-content").loopedSlider({
			autoStart: 3000,
			slidespeed: 500,
			containerClick: false,
			autoHeight: false
		});
});
</script>

Change 3000 (3 sec.) to the duration in milliseconds that you prefer.

No problem Jeff. Actually Fancybox is one of the plugins that works very well with your plugin, since it allows users to disable the jquery autoload. Many other lightbox plugins dont have that option.

At any rate, Frontpage Slideshow is a really versatile and useful plugin. Thanks again.

Jeff, I’m not complaining. I’m letting users know that some plugins allow you to disable jquery in order to avoid conflicting with other plugins. I’m not suggesting that you add this feature to your plugin (though it would be helpful). I’m simply hoping that this information will resolve a problem that a lot of users seem to be having.

I’m not sure why you’re so defensive Jeff, but nevertheless thanks for the plugin.

If anyone is using a Lightbox plugin, it will cause jquery to be loaded twice, and create a conflict with Frontpage Slideshow.

Some Lightbox plugins (like Fancybox by Jose Pardilla) allow you to disable the jquery call. This fixed the problem for me.