Wondering if anyone who would know has seen or looked into this yet.  I've examined the situation further, and I've noted that when you use the tabbed excerpt rather than the one generated by the blog feature's defined-length excerpt, it keeps its markup (bold, italic, etc), and it's enclosed in the standard paragraph tags added by the wysiwyg editor -- the blog-generated excerpt appears to strip all markup, and it doesn't use any <P> tags, it's simply <div class="blogtext">the stripped txt</div>. (what the heck did I do before there was firebug?!)

For this reason (the stripping of markup), I'd have to say I prefer the non-stripped, available by using the tabbed excerpt -- but that weird appending of the comments link rather than the Read More link really needs to get fixed-- if you can tell me where that code is and what it should be instead, I can probably do the edit myself -- it's only the inclusions of the ASP code that sometimes throws me for a loop, the HTML is no biggie.

Thx,

Andria

Hmm.  I went to demo.mojoportal.com.  When I tried adding a new post to the blog, when the page opens for that, there is no tab for "excerpt," just tabs for "content" (where the post is actually entered), and "page meta data".  When I went into the feature settings for the blog, there are no jquery tabs, so there is nothing past "date/time format string" -- no way to even check and see what the excerpt settings are.

I did note that that demo site is running mojo 2.3.5.5, and mine is still 2.3.5.4 -- could it be some difference between versions, or, is the demo site setup to use excerpts at all -- it's one of the jquery tabs that aren't showing up in the demo site's blog feature settings page.

Thx!

Andria

Ok, when I went back to the demo site, there was another skin active, so I checked again, and did see the jquery tabs; I set it to use excerpts, and I am also unable to reproduce the error, so at this point I'm thinking I should upgrade my 2.3.54 to 2.3.5.5, and see if that might fix it.  So I'll go and download the whole site, and backup the database, and then do the upgrade.

Thx,

Andria

Further on this weirdness... I went ahead and got an IntenseDebate account, and am using that now instead of Disqus, and the "read more" link appears just fine, whether I use the blog-generated stripped excerpt (and yes that makes beautiful sense to strip markup, so as not to leave any of those messy unclosed tags) or I enter the excerpt myself in the tab -- of course, because it doesn't strip the <p>, it does put the read more link on the next line, as the </p> automatically kicks to the next line.  so maybe I'll just change the look of the Read More link, to make it fit better visually.

I read someplace else in this forum when I was trying to learn how to use the thing, that the IntenseDebate comment system seemed to cause far less problems all round, so I figured it was worth trying out.  I like that the mojo code seems to play nicer with it, but again, I think the problem I've seen with this might already be resolved with the newer 2.3.5.5 release.  I never was able to reproduce the weird link at the demo site, though I tried getting everything set up as it is here -- but then again, I didn't go into site admin and change the comment system there, so perhaps that might be a factor as well.

At least now I have a working Read More link, even if I use the tabbed excerpt (which I do like, for the ability to customize the excerpt length, and retain markup), so that's all to the good, problem solved.  And now I have a much better grasp about the markup stripping/not-stripping -- thanks y'all!

Andria

You may be right about the javascript, but I have rarely been able to decipher much javascript, so there's no way I can look at it and figure out what's wrong with it.  Switching to a different comment system works for me, as it will serve to keep my .net sites distinct from my .com sites, which are all on a Linux server, running Joomla and disqus (though I'm planning to move one of my .coms to another mojo site on the .net server, just because my son, who is the ostensible admin for my book review site, finds the joomla backend almost incomprehensible -- it took me about 2 yrs to get really conversant with it).

At some point I'll revisit the demo site and try that, setting the comment system to disqus in the system admin, and see if that will reproduce the error; at least if it can be reproduced in 2.3.5.5 it would indicate that it didn't get inadvertently fixed with the new release.  It could be something as simple as a misplaced semi-colon and javascript would have a hissy fit. 

Andria