Bentrem

@rove from the site it looks like kardworx has things sorted, so I’m going to risk hijacking this thread; re-direct me as required.

The page I want folk to land on (FrontPage aka Home) already exists, so I skipped your step 1.

A little quibble with your step 2: when you write “a page called …”, you mean “titled”; its nice when what we see matches the instructions. (Easy for you? Very glad to hear it. But I’m dealing with frustration/confusion just ATM.)

Things work immediately but break down right away.

On bentrem.wordpress.com I had Blog, About, and Page3. I created a page titled Blog Posts. In Options > Reading I selected Static, set FrontPage to “About”, set PostsPage to “Blog Posts”, and viewed the site.

Goodness: Home defaulted to About. Goodness: BlogPosts displayed posts. Goodness: Page3 is happily blithe.
But then *Whaaduh’aey?!* I see that there’s that 4th tab … the original “Blog” tab remains.

A new tab was created for BlogPosts; fine.
No damage that “About” still has it’s own tab, since in this test case things are a little confounded.
But this 4th one? That’s the sorta brain-damage stuff I diss other people’s work.

Doesn’t matter what things are called, you still end up with 2 tabs pointing to the same spot. (For my money pages should never point to themselves, so this is actually doubly wrong, but I won’t go there. Not right now.)

The same is true about karworx’s http://tellurideblog.com/ but on his/her site it isn’t so painfully obvious since his links are in the sidebar.

RFE?
Whatever page is set as Static FrontPage should have itself removed from the listed pages.

Seems like the real thing; Support 154139 (started 6 days ago) reports the same trick.

Time for someone to open a Ticket? one already opened?

@duskglow Yes, you’re right, it’s true. But not always. 😉

1) concensus seems to be “left in Draft”; you wrote “managed to do so in such a way that it stayed published” … have there been others reports of “left as Published”? did the test scenario you blogged leave things as Published?

2) do you think it’s two separate scenarios?

In TRAC the call seems to be for more hard data.

Wait a minute … if we’re talking about security then we’re talking about something like strict logic. (Someone mentioned “audit”? I’m available … I won’t tell you what I wrote for optimizing VB5 shiet. As for normalizing a commodity trading shop’s QuatroPro and Paradox? $250/day 14 years ago. And I did MEL-SPEC FMECA at fed rates. You wanna wade into that swamp, get yourself a good boat. Or skis.)

I don’t see anything here like fault-isolation and identification. /Not saying it’s not; saying don’t see./

Here’s the noisy bit I found in VillageIdiots’ thread:
“they managed to edit mine in place and leave it published.”
Well ok: if that’s so, then we’ve got A.
But if it’s “the posts end up being changed to drafts” (That’d be nice!) then we’ve got B.

So: if we reporter could re-iterate again, for once more time, reduntantly, that’s verified as a UserCase.
When someone maps out how to disconfirm that, they should publish IEEE.

Point is: it’s distinct scenarios; either they’re left in / toggled to Draft (1 chain) or they remain Publish (1 chain … a different one).
The facts merely collapse the probability wave and provide a link back to the failure node, they don’t fix the fault.

*I’m not much into coaxing a worm to squirm or a cat to stray … call me old-fashion.*

–bentrem

Geeez … this guy posted 3 months ago and got no reply. Am I outta luck?

V2.3.1, Acitivating SideBar Widgets produces the following:

“Plugin could not be activated because it triggered a fatal error.”

Error text is as follows:
“Fatal error: Cannot redeclare register_sidebars() (previously declared in [correct directories here]/blog/wp-includes/widgets.php:15) in [correct directories here]/wp-content/plugins/widgets/widgets.php on line 42”

Everything has been working fine, but I want to install MyBlogLog widget … which requires that this be activated …

‘Sup?

–bentrem
bentrem.sycks.net/blog/

Addendum (got caught by “post too old”):
In “How to stop TinyMCE from pulling MS styles from Word docs” azaozz points to a potent functionality:
Rich Text Editor Filters states “mce_valid_elements – applied to the comma-delimited list of valid HTML tags for the rich editor. Any elements not in this list will automatically be removed …” and then *sigh* points to a TinyMCE doc that is 404 at the moment.

What I’m listing as my promising candidates on my “Editor” scratch page in Wiki are these:

AreaEdit, spartan and well behaved from FormVista (modified BSD?), and perhaps ManInBlue (gave it only a quick looks but it seemed sweet).