skeltoac

I looked at your blog and your stats reports. Sorry about this, but as far as I can tell your stats plugin is working normally. It loads the tracking file and shows the results on your report page. While the 50% drop you experienced could be alarming and might point to something being wrong, nothing I saw indicated a problem with Jetpack or the Stats module.

Probably the second most common cause is a javascript error earlier in the page. If you post your blog’s URL I can take a look and let you know what I find.

The usual suspect is the theme. Please see the FAQ about that.

The scriptaculous directory can be in the widgets directory or the js directory. It doesn’t matter.

I updated the plugin a short while ago for backwards compatibility. If something is still wrong, I’m going to need more details or more access. If you want me to log in to your system and check it out, email creds to my username at gmail.com.

Sorry about the lack of version numbers, folks. We’ll shore that up for you.

The latest change (90 minutes ago) fixed a behavior like the one you describe, which only happens with certain themes. You can get the latest plugin file here:

https://svn.wp-plugins.org/widgets/trunk/widgets.php

Hi all. I built the present importer and I’ll do what I can to help. For starters, I just this minute tested it on my own server: Ubuntu Linux, Apache 2, MySQL 4, PHP 4, no problems.

From reading your many bug reports above, it appears that the cause of the problem is in the responses your servers are getting from the Blogger servers. This is a very delicate relationship and any variance will break the process. What’s worse, I can’t get Blogger to replicate the problem for me.

All I can do is conclude that Blogger’s service level has caused the issue, or your hosting situation is somehow preventing the importer from doing its work. I’d actually lean toward the latter because my tests have never failed in the ways you are experiencing. Poco’s success favors that conclusion as well.

If someone would like me to troubleshoot their issue by allowing me to log into your server, I may be contacted by email. The host is gmail.com and the username is skeltoac. I will need SSH access.

I’ve just tested your patch on a LAMP setup and it works just fine. I’ll submit it to trac for you. Thanks!

Here’s a patch that eliminates any further annoyances caused by this effect:

https://trac.www.ads-software.com/ticket/2454

Short version: that advisory is bogus. Commenter URLs are stripped of all quotes and other invalid characters before storage and display.

Long version: the scripting code the author demonstrates only works when the following are true:
1. The visitor commented on the site in question with that code in his url, or had cookies planted in his browser to mimic the effect of leaving a comment with that code in the url.
2. The visitor is not logged in to the site in question (logged-in visitors do not see the URL input box) and therefore does not have his credentials in his browser’s cookies, so they cannot be stolen by any script in the comment form.

Did you edit wp-config.php yourself? Check to make sure there are no blank lines before <?php or after ?>

gornik: Can you look in your posts table and see if there’s anything with post_status=’attachment’?

santm, I checked your javascript and I see no errors in it. Perhaps an option problem.

https://trac.www.ads-software.com/ticket/2183

Thanks

try wp-admin/options.php

Using the rich editor? Enter creates paragraphs. Shift-Enter creates line breaks.

You can switch off the rich editor in the user options if you want to write like you used to.