WordPress.com Forums » Tag: regression - Recent Posts http://en.forums.wordpress.com/tags/regression WordPress.com Forums » Tag: regression - Recent Posts en Tue, 21 May 2013 19:03:09 +0000 http://bbpress.org/?v=1.1-alpha-2539 raincoaster on "The more tag is broken" http://en.forums.wordpress.com/topic/the-more-tag-is-broken#post-805539 Mon, 30 Jan 2012 22:13:42 +0000 raincoaster 805539@http://en.forums.wordpress.com/ That is correct. It's a common question. When you look at that unique post's page, you don't see the jump.

]]> billmcn on "The more tag is broken" http://en.forums.wordpress.com/topic/the-more-tag-is-broken#post-805497 Mon, 30 Jan 2012 21:33:45 +0000 billmcn 805497@http://en.forums.wordpress.com/ I find the documentation on this feature confusing, but with your explanation I think I get it. Say I write a post called my-post containing a <!--more--> tag and it's the top post on my blog site. Then if someone accesses that post via the URL

mysite.wordpress.com

they will see a jump. However, if they access it via the URL

mysite.wordpress.com/yyyy/mm/dd/my-post

they will not see a jump. Is that right?

Regardless, pagination looks like it will work for what I want to do.

]]> justjennifer on "The more tag is broken" http://en.forums.wordpress.com/topic/the-more-tag-is-broken#post-805484 Mon, 30 Jan 2012 21:22:22 +0000 justjennifer 805484@http://en.forums.wordpress.com/ Oh, wait, you said in a Page? Then you'll definitely need to use Pagination. The More tag only works on Posts appearing on the front/home page of a site. http://en.support.wordpress.com/splitting-content/nextpage/

]]> justjennifer on "The more tag is broken" http://en.forums.wordpress.com/topic/the-more-tag-is-broken#post-805482 Mon, 30 Jan 2012 21:20:45 +0000 justjennifer 805482@http://en.forums.wordpress.com/ You'll only see the results of the tag on the front page of the site, not in the post itself. If you need to break a long post into several sections, you can use Pagination.

]]> billmcn on "The more tag is broken" http://en.forums.wordpress.com/topic/the-more-tag-is-broken#post-805476 Mon, 30 Jan 2012 21:15:10 +0000 billmcn 805476@http://en.forums.wordpress.com/ If I insert a <!--more--> tag into a page I'm composing for my blog on wordpress.com it does nothing. The page renders without a jump in the middle. This is true of both the preview and the published page.

This used to work. I have a blog page from January of 2011 that contained a <!--more--> tag. It rendered correctly then, but I just went back and checked and it no longer renders correctly. I don't know when it broke.

]]> supportbot on "wp-stats serves http tracking gif when page is https (regression)" http://en.forums.wordpress.com/topic/wp-stats-serves-http-tracking-gif-when-page-is-https-regression#post-524797 Tue, 09 Nov 2010 15:23:23 +0000 supportbot 524797@http://en.forums.wordpress.com/ The blog you specified at robert.accettura.com does not appear to be hosted at WordPress.com.

This support forum is for blogs hosted at WordPress.com. If your question is about a self-hosted WordPress blog then you'll find help at the WordPress.org forums.

If you don't understand the difference between WordPress.com and WordPress.org, you may find this information helpful.

If you forgot to include a link to your blog, you can reply and include it below. It'll help people to answer your question.

This is an automated message.

]]> raccettura on "wp-stats serves http tracking gif when page is https (regression)" http://en.forums.wordpress.com/topic/wp-stats-serves-http-tracking-gif-when-page-is-https-regression#post-524796 Tue, 09 Nov 2010 15:23:22 +0000 raccettura 524796@http://en.forums.wordpress.com/ Looks like for the past day or so the wp-stats plugin now injects a quantserve tracking gif.

Besides for the obvious privacy implications (I bet most wordpress.org blog owners don't know quantserve is being served to their visitors), this has implications for SSL users.

Pages using SSL are now broken since the wp-stats JS doesn't check to see what protocol is being used. http is always used for quantcast (quantcast does support SSL).

This:
document.write(unescape("%3Cscript src='http://edge.quantserve.com/quant.js...

should be something like:
document.write(unescape("%3Cscript src=') + document.location.protocol+unescape("//edge.quantserve.com/quant.js...

]]>