fjpoblam

In absence of a solution, I will go ahead with my personal plans and delete the email address to which the WordPress support site is sending responses. Too many email addresses to keep track of…simplicity is better!

As I cannot register a new account with one of the other addresses (erroneously) associated with that WordPress support account, I suppose I must forgo email responses. I will pursue other avenues for WordPress support and, if I absolutely mist post here, login occasionally to watch for responses.

Revisiting How can I delete my wordpress account [closed]: I changed the email address as is allowed on the profile screen. Fine. I then found I could logon via both addresses (the old and the new).

Why all this? I had thought, simply, to change the email address so I could close the former email account itself…and simplify my life by having fewer email addresses. Seeing, though, that the old email address was still available for logon, I went for the stoopid route. In the profile, I changed the email address to a “junk” address. My bad. Now, logon is allowed at three email addresses.

In addition, I had thought “gracefully” to establish a new WordPress support account using the desired (second) email address. Oops! “Taken”. So now, my WordPress support account allows logon at three email addresses.

One might with some validity think an email address change in the profile screen would not be possible if, as you say, a form account “cannot be registered to another.” It’s a great life if you don’t weaken, but who the heck wants to be strong?

Ah, Andrew, I suppose not. Yet I receive response notifications at an email address not allowed for logon (unlike the other ones). Interesting. IOW, responses arrive at one, logon is allowed at three others!

@demonboy – Oh, I humbly apologize if you took my comment as offensive or critical. Not intended that way, at all. Your code is wonderfully legible and shows an admirable knowledge of both PHP and the WordPress call-outs: I wish I had WordPress memorized as well! I will take your post under advisement. My current template is classless, id-less, divless, and spanless… You may deduce that it is an entirely simple-minded matter—inspired by Jeff Starr’s H5. I will consider either popping in your example verbatim or butchering it with love to fit my playground.

Wow, @demonboy, intense!. That’s a lotta divs and spans plopped into your code. I reckon you’re popping them by name as targets in your external either css or js, no?

Thank you, alchymyth. Especially for the link.

I suppose, in the end, all I’m asking is, is the loop a necessary component, considering (as I understand it) that the query is already done upon page display in the head section? Is not post content, next- and prev- post link info available within appropriate PHP/Wordpress functions, without having to nest them within “the loop”?

Oops, It looks as if my link was stripped from this post as well…I guess I didn’t escape correctly. The first was *intended* to be surrounded by an a href

OOPS— may I delete this thread? Resaving the template itself seems to have solved the problem, though I don’t understand why…

Superb hint. Working for me. I was looking for a way to add a “Home” link on all but the “Home” page, so the “if get_previous…” is ideal. The only conceptual case in which it *doesn’t* is, when the visitor is looping newer and newer through a category set and reaches the newest, that being *not* the home page. I’ll have to think about it…

…Okay, thanks. I’ll try to figure out how to expand upon your suggestion for my needs (given my puny knowledge of jquery and lightframe). Yep, I know, I know: “read the instructions.” Thanks again. Really. ??

Yep, I have, and am aware that the meanings of “next” and “prev” are, in effect, reversed. This’ll mean an alteration in the way I define the visible text that goes along with the links in my nav section. However, the topic I’m trying to address here is specifically, the PHP error.

The “next_post_link” function isn’t found. The “next_posts_link” is.

The “previous_post_link” function isn’t found. The “previous_posts_link” is.

Is it impossible to gain access to the “next_post_link”/”previous_post_link” functions via edit-in-place?

[added] The point is, next_posts__link yields html consisting of the *entire* a href=”…” text while next_post_link gives me more granular control over the generated html.

First, I don’t understand why it’d be a bad thing to edit main template files in place—I’ve done so many times without negative effect. (It should be noted, of course, that mine’s an extremely simple-minded template, scavenged from Jeff Starr’s H5, and simplified to the point of only index, functions (few to none) and link to master site css).

Second, yes, I am aware of the intended *use* of the two functions—i.e., providing links to either generic next/previous page in time or specifically the same in a narrowed tag/category search (in the way my template’s defined).

What am I trying to do? Simply, as I said, including the ”rel” text in the said links. That’s all. (Why? Semantics. Css styling.)

Same problem for me. Your suggestions tried. In fact, here’s what happened. Upon upgrade to 3.7.1, my blog began to yield a blank page. I started troubleshooting by deactivating the one plugin — WPSupercache — and then removing it. I set a theme different from my own custom theme. I re-uploaded my theme (more than once!) Finally, the pages are visible again. Still at great sloth. The blog has entries dating back to 2006. The template consists of a minimal 3 files (index, functions, style) based on Jeff Starr’s H5. For styling, it links to a CSS file of 19 lines also used by other static files on the site. No images. No site redesign (or, heck, even content changes) between 3.7 and 3.7.1. Has anyone else reported this?