cloudhopper

Skippy is the man!

Changed the code referred to (2 posts above) to read:

ORDER BY post_title ASC”

and sure enough, the code filched from the Codex (see Post#1) now works – listing *all* my posts, by title, in Alpha order. (I now have to work out why some of the posts don’t seem to obey the rules of alphabetic order, but that’s another game!).

I will add a comment to the bug report – if I am allowed.

Signing out note: if someone works out whether the other codex examples (the ones with the parse errors) actually work, or need some ammendment, it would be nice to know. :o)

Thanks Skippy, I’ll have a play with that.

Slightly OT, but relevant in context: it is in areas such as this that WordPress scores so strongly for me, in that it is causing me to *want* to learn about CSS and PHP, so that I can make *my* bit of the web do what I want it to do.

The downside is that occasionally, the easy cut&paste stuff takes you into deeper water – and you know that panicky feeling when you suddenly realise you can’t feel the bottom any more?!

Anyway, I recognise that the support and documentation is developing apace, and *respect* to all you guys who are so phenomenally patient and generous in these forums. I am genuinely impressed with not only the software, but the whole attitude that surrounds it.

I’ll report back on that fix, once I’ve eased the brain-ache a little :o)

Moshu – hmm. Forgive me, when one cut&paste example works, I kind of assumed….

..so I followed the link to The Loop and added the code entitled “and ends here”.

So now I don’t get the parse error, but neither do I get anything else. (Stamps foot: surely an example in the codex might be expected to…. pfft. Sorry!)

Skippy: tried taking out “$query_string .” (but left the end of the loop in place). No parse error, but no nothing else neither. : (

Coffee’s on – want one?

Well, I may have trouble understanding what’s going on with CSS sometimes, and definitely am in the woods when it comes to PHP, but I’ll be pretty disappointed if it turns out that I have not, as I always thought, mastered the art of cut&paste!

Here’s what I have – straight from the page of the Codex – and taken via Notepad, just in case there were any hidden characters lurking:

‘<?php
// we add this, to show *all* posts sorted
// alphabetically by title
$posts = query_posts($query_string . ‘&orderby=title&order=asc&posts_per_page=-1’);
// here comes The Loop!
if (have_posts()) : while (have_posts()) : the_post(); ?>’

Sure enough. This gets me the parse error – context as described two posts above – simple page: header, footer, content div.

(Appreciate you returning to this, I used up my bump already!)

There are four examples on the “Alphabetizing Posts” page – the first three all return “Parse error: parse error, unexpected $” when tried – only the fourth example, cited in Post 1, works at all (for me!).

I quite expect that this is a result of me not knowing what the hell I am doing, but then that would be fairly and squarely in the context of my cry for help & guidance!

If it helps further, I am using the Archives template from the Letterhead theme – I just dumped out all the existing Archives code from the Div id=content area – leaving a header and a footer – and popped in the code in Post 1. In the same circumstances, the “parse error” occurs for the other examples.

1.5.1.3 – latest stuff : )

Polite .bump

Any pointers on this one?

The example code I cited above is from the Codex entry on “Alphabetizing_Posts” and results in a combined list (of all archives) -which is *close* to what I would like to do – but is still apparently in chronological entry order.

There is another example of code on the same page which simply results in a “parse error” when I try to include it.

Unlike other posts I have spotted here today, I am willing to increase my PHP and CSS knowledge (and am enjoying that) but I seem to have reached a personal brick wall on this one :o)

Any help appreciated. Ta!

This looks like a result – I’ve been running it for 24 hours and the 255’s have disappeared, neither have I seen any of the other problems that I encountered when trying the various php code changes mentioned elsewhere in relation to this problem.

Nice one. I have *no* idea what this database field is doing (and neither do I need to know) but if anyone knows of any good reason why this is a *bad* idea, please sing out!

Thanks, RaHarakhte!

Is it possible, bishopthom, that you could clarify the code that should be replaced in your instructions above in addition to the line number… I am using BaStats 1.0?2 build 8 but the change outlined above had no effect for me.

Line 92 for me is: $qry .= “, ” . $ua_id;

Like some of those above, I have trouble relating this to my host (Dreamhost) since it has *only* happened since I upgraded to 1.5.1.3 (after patiently waiting for the dust to settle) and *only* occurs for some IP addresses.

Failing that (and I don’t really want to abandon BaStats) any other recommended plugins to monitor visitors?

First post in these forums – be gentle.

The IE issue (whilst perfectly valid) may be a distraction. I am running two FF (1.04) sessions side-by-side here. Same theme, different versions of WP.

On the Wp 1.5 session, login/logout behaves exactly as one would expect.

On the Wp 1.5.1 session, it does *not*. Logout results in “logout” remaining on view in the meta section. Click on “logout” it takes you to the login screen (as others have already reported).

[Incidentally, in the 1.5.1 session I am also not seeing any of the Edit functions I would expect to accompany my posts once logged-in, but until I have investigated a little further would not necessarily presume to link those two events.]

Apols if there is a more current (or resolved) thread – a search on “Logout” brought me here.