Wedge

Removing it and making it disappear was never at any time part of the proposition. Please re-read the first post in its entirety, because as I said it would be converted into a plugin.[1] It would be available with all the features you currently have, probably get more as well, it would also make us resolve current weaknesses in the plugin system as it would force us to restructure things that haven't yet been overhauled.

Also please note the dearth of topics about our plugin manager. It generally doesn't need file edits; and nothing about the calendar makes me think it would either - which means it's a one click operation to enable - in fact putting aside the actual act of getting the plugin onto the installation, you wouldn't even notice much of a difference - it's not like you get the old install screen or anything.[2]

1.	I appreciate that it is important to you. I'm just annoyed that you appear to have replied without actually taking into account the actual meaning of my post and this conversation in general, and frankly, an uninformed opinion on a debate like this is actually worse than no opinion at all.
2.	This is the point where reading up about the plugin manager would be a good idea. I have posted several screenshots and have discussed at great length how it avoids most of the pitfalls of SMF's package manager, by generally not requiring edits while still extending the system.

How quaint, an old SMF bug back to strike again. I thought that had long since been fixed (because it is an SMF bug originally)

Anyone else want to add anything before I break out my big wire-cutters?

Eh, it's not for me, if I were doing this, I'd just set up something locally and write it there - but my friend wants something he can use while on at break at work, and he's quite keen on the fact that WP supports post by email, apparently.[1]

(This is the curse of being a technically minded friend!)

1.	Never tried it, no idea if it works or not.

I don't know for sure, so from what I can remember off the top of my head...

Theoretically, you should be able to have more than one instance of the menu per page, through the generic template. No-one has ever done it as far as I know, and in fact to the very best of my knowledge the only times there are multiple "menu" instances on a page, it's not done through the generic template.[1]

I don't know why you would do it either, because it'd be a fucking mess if you did, but theoretically you can do it - in which case, max_menu_id would always be the 'last' one created, while cur_menu_id would be the one you're currently rendering.

1.	e.g. http://www.simpledesk.net/development/api/ has the top menu, the normal main nav menu and the actual contextual nav menu. I know that's the case, because neither SleePy's code (the top menu) nor mine (the page menu) used GenericMenu to do it.

WP not only doesn't do that, it doesn't let you configure what the roles are, either. I hate WP.

I'm not baffled by the way permissions are allocated to roles. I'm baffled that you cannot actually set permissions in the core, other than setting roles to people.

The concept of roles itself doesn't bother me in the slightest, indeed it actually makes sense - even in WP's terminology it makes sense - you're not allocating permissions to users by the group they're in. Permissions are given to a role, and you give the role to a person. The fact you can group people by what role they have is actually irrelevant; you're not putting them into a group itself.

Thing is, though, WP never seems to be calling itself a barebones core, it talks up its feature set, but the more I see, the less I think of it.

A friend of mine is interested in writing a story as a series of blog posts, which is cool. I've seen their writing style, and I suggested a blog type format to let loose each of the pieces of the story over time, sort of like a classical serial.

And naturally, once I said 'blog', they went looking around, and pretty naturally hit up on WP first.

Something funky hit us though - my friend isn't particularly interested in making it public yet, not until a decent amount of the stuff is written. So he asked me to have a look at how you'd do just that.

And the more I look at it, the more confused I'm becoming with. I realise I'm not a hardcore WP user, but I'm genuinely confused by 3.2.1's permissions. Or more accurately, the lack of them.

Users can be assigned roles, that's cool. There are several roles (subscriber, contributor, author, editor, admin) but I'm mystified as to how this works.

I cannot, for example, find anywhere to actually set what these roles can actually do, let alone configure them or anything. I have no idea what the difference between them is, or even whether it's possible to make a blog sign-in-to-view or not.

Now, you'll probably say that it's in the manual, and it probably is, but I've been through the entire ACP and cannot find it, which says to me that the UI is broken.

OK... so I then looked it up in the manual. I can, fairly easily, find a list of what permissions each role has, though it's written almost more in programmer terms than anything else.[1]

But, OK, so I found what basic information I was looking for, and check this: I don't think I can probably remove the permission I want to remove from the basic subscriber role (which is after all what it seems like guests have), and even if I could, I'd have to add a plugin if I want to do anything more awkward.

Am I going mad or is this actually quite ridiculous? I have no doubt in my mind that handling permissions is complicated but to provide only the most simplistic of UIs is actually stupid... isn't it?

I've heard that it's "the greatest CMS since sliced bread" but the more I use it, the more I think it doesn't actually DO all that much, and that the only reason it's so 'great' is because there are some plugins that handle doing good stuff with it.

1.	Kid you not. http://codex.wordpress.org/Roles_and_Capabilities