Helen Hou-Sandi

To answer some of this:

For the framework version – perhaps a constant would work? E.g. something like MY_FRAMEWORK_VERSION, which you could then compare against.

To exclude things from update checks: https://markjaquith.wordpress.com/2009/12/14/excluding-your-plugin-or-theme-from-update-checks/

Hi Ross,

Thank you for your quick response! I understand the reasoning, and figured out why one of my rules was being overridden, so all seems well in my particular use case.

And yes, I did mean the theme’s style.css (not styles.css, oops!). I use WordPress largely as a CMS for clients, so the chances of custom stylesheets being overwritten is (almost) non-existent. But, just deregistering things in that case works just as well as any option ??

Actually, even better, you can add it to the network menu instead. Use

add_submenu_page('settings.php', 'New Blog Defaults',
                 'New Blog Defaults',
                 'manage_network_options',
                 'cets_blog_defaults_management_page',
                 array(&$this,
                       'cets_blog_defaults_management_page'));

for the add_siteadmin_page() function. Then, where the action for admin_menu is called using the function, use network_admin_menu instead.

Yes, this is a small plugin indeed. However, it addresses the following:

• Not all people are comfortable editing their CSS
• It also hides the search in the admin/dashboard, which is not a CSS file you should be editing
• One may want it to be network-wide regardless of what theme is being used in a multisite situation (which was my reason for writing this in the first place)

There is no way to remove it using PHP – it’s baked directly in the render() method for the admin bar class. Believe me, if I could have done it that way, I would, and then would have titled the plugin “Remove Admin Bar Search” instead of “Hide Admin Bar Search”.

There are no plans to expand this plugin beyond using WordPress’s built-in attachment functionality. There are methods out there to grab the first image source URL from your post that you can use, but it’s very unlikely that will make its way into Really Simple Gallery Widget.

Thank YOU, and you’re very welcome!

You should be able to just copy a fresh wp-includes over (the same version as what you were backing up, of course). There’s nothing in there that would be site-specific; all of that should be in wp-content.

Thank you – I appreciate it. I also understand your intent now! Believe me, some of us working in academia share your feelings about stupidly long names ??

I don’t think it’s okay to take the choice away from the user and for you to decide what the “only good title” is for a subsite – not all multisite setups are the same. It also can potentially make the breadcrumb unusably long when an accepted abbreviation for the subsite’s name can be used instead.

In my case, we are using subsites for departments/offices within a university, with the main school site as the main site. If we have Jazz Studies and Contemporary Media as the subsite title, the breadcrumb becomes effectively useless because it has already nearly exceeded the horizontal space allotted. I think just the word “Jazz” would suffice in such a case, especially given the context (header graphic, other visual elements).

If you allow the main site to be labeled differently when that option is filled, then the same should apply for the subsite. I personally can survive with working around it using the Home Prefix instead, but I would love to streamline our site setup process (done only by web admins) and don’t see why it would cause any harm to use options that are already set in your plugin.

Okay, I think I understand. I was just confused because some options save where others don’t, so my initial thought was that it was a bug rather than expected behavior related to the network site. Deactivating and reactivating did not fix my problem. I found the blog breadcrumb option, which was what I needed and the option did save, so I personally have found my way.

Thank you for this great plugin – I look forward to the next release, as well!

Well, it does seem to work just fine for the individual site, with the exception of the page/post settings that aren’t saving. The settings that do save work correctly. I’m not sure what you mean by individual sites vs. new network site setups.

A couple of things I noticed while digging:

• The site that is working has a custom post type; the site that is not does not.
• The post/page options are actually saved as post_post_OPTION and post_page_OPTION in the database, as opposed to post_OPTION or page_OPTION
• The site whose settings are not being saved does not have any reference to post_post_OPTION in the database, and manually editing post_OPTION does nothing to the output. Attempting to add the post_post_OPTION breaks the breadcrumb output (although I could be missing a semicolon or colon).

Is post_post_OPTION the expected behavior?

The media picker is showing up in the thickbox – it just doesn’t have the “insert into post” button unless you enable the editor, so attempting to insert anything into a custom field doesn’t work with editor disabled.

Aha, I found a plugin I hadn’t tried disabling and it was the problem – Active Directory Integration. I wonder if explicitly declaring the rest of the UI tab CSS would ensure that this doesn’t happen to other users, since many other plugins load their admin CSS in all admin areas.

Anyway, that’s my mistake – thank you for the 3.6 update! It’s working perfectly otherwise.

I’m having the same problem with using the media button without editor enabled. I tried leup’s fix but it’s not working for me, though enabling the editor does allow me to insert media into a TinyMCE area. I put those lines after the endif; – is that correct?

All pages show for all users, even if they do not have editing permissions for that particular page. I think it should probably only show pages for which that user has permission to edit.

Previously a non-admin, non-editor user who had scoped permissions was able to only see pages that they could edit.