davehprohoods

The custom theme is based on the Twenty Eleven theme. We can’t just change to the Twenty Twelve theme, it will break the whole site.

The function it uses is get_template_part(‘content’, ‘page’)

It’s a custom theme. What does that have to do with the Text editor? The theme doesn’t add tags in the middle of Page content, it just includes the content like every other WordPress theme.

Yes, the Text tab in the Page editor. That’s what I mentioned in the title.

That’s not the WordPress solution. Like I say, this may not be for the average WordPress user.

Can anyone please provide any suggestions for a plugin or how to hook the WP_Image_Editor class to the TinyMCE editor?

This is good, but it’s not in a Post, just in a theme file, and Javascript works, but jQuery doesn’t even though it’s included successfully in the head.

Would WordPress prevent one of the theme files (which is actually a template) from running jQuery but not Javascript? I think I’m missing something on understanding on how it puts the page together somewhere.

OK I discovered that Screen Options just shows/hides options I can set for the page or post, so I enabled Discussion in the Screen Options on the page edit screen and unchecked “Allow comments” in the Discussion section that popped up below the edit box. That set “Leave a reply” to “Comments are closed”.

Unchecking everything in Discussion did nothing.

Right, I know it’s supposed to be a capability, that’s what it says in WordPress’ source code comments for that function; I don’t know why it was a 1, I didn’t code it, I just want to know what values I can put there, and I’m not sure why ‘manage_network’ would be adequate for that when there’s a zillion capabilities and 5 for Super Admin… what if I wanted other capabilities for that option page? What I’m saying is the explanations for this in the code and the codex aren’t clear and I’m trying to make sense of them.

We’re using version 3.5 (which my original post conveniently didn’t specify even though I selected it from the drop-down), the code I inherited uses the number 1, and the codex doesn’t specify what to use instead. ‘Super Admin’?

I don’t understand what you mean by use current_user_can instead of a capability number for the add_options_page function call… that doesn’t seem to apply here. I need to know what exactly I can put in for the capability parameter on the add_options_page, and the WordPress codex and the code is not telling me.

This is the code I inherited:

add_action(‘admin_menu’, ‘new_admin_actions’);

function new_admin_actions() {
add_options_page(‘new_admin’, ‘new_admin’, 1, ‘new_admin’, ‘new_admin’);
}

Thank you!

Uh, yes, I have made a bunch of sites for other people, just not through WordPress (this is my first time managing it, including multi-site, and in fact I took over for an entire development team that worked on this, left it a mess for us, and is not in contact with us anymore because of reasons I had nothing to do with), but thanks for the overly-broad assertion.

Anyways, thanks for the information, it is helpful, and I am learning as I go, but please don’t take my comments about WordPress’ way of doing things personally or make generalizations about somebody’s experience level.

That’s a bizarre way to do it. Why am I able to create a site as a super user but not see it on my sites list without adding myself as a user to the site? Isn’t a super user supposed to see everything? Seems like a design flaw.

I don’t understand what you’re asking. We created a site, made it a multi-site, added the Domain Mapping plugin, created sites with sub-folders and mapped domains to them. When I log into the main site, hover over My Sites at the top, and it only shows the sites created before I started, not the one I created. I hover over Network Admin and click Sites, and it shows all the sites including the one I created. The previous developer did something I haven’t yet, and I’m not sure what that is. Everything else looks fine.

Yes. I added the site through the Network admin and then mapped the domain through the sub-site.