1. That still works to remove the docs menu item (I’m using it on 3 sites). However, to make it easier, I just added an option to disable the automatic menu link. This will be available in version 2.0.2 which will be released within the hour.
2. Do you mean that you have a the Docs widget added to that page? The plugin doesn’t add widgets to the Docs main page. I would have to see a link to this page to investigate further.
3. The page that your provide a link for is full of semi-parsed code which may have (almost definitely) affected the display of that page. If you are trying to show code on your page, see this from WordPress:
Using the code tag doesn’t tell WordPress to encode HTML markup within the tag or strip it from the post. WordPress thinks that you are using this markup for formatting, leaving it untouched. A web browser then sees a code tag followed by a div tag and so it responds by creating a new container in your web page. Similarly afterwards, it sees the start of an h1 tag which will screw up your entire web page layout and design…
So, I really can’t investigate until that code is removed, or even better, use a SyntaxHighlighter plugin from WordPress.
Thread Starter
sroser
(@supawiz6991)
1. Scratch this one. It wasnt working on the live site but works on the Developement site so ill troubleshoot it on the live site.
2 & 3 I removed the code. Prior to the update the way I entered that in there worked fine. The reason for that code is I was documenting the custom changes I made to the themes php files. Even though I removed the code the page is still messed up -> http://gihomes.promediaonline.com/docs/sidebar-php/
Also if you look on the right side you will see “Table of Contents” on some browser the text is black so you have to highlight it to see it. I didnt add that and have no Idea how it got there.
2. Yes, the Table of Contents widget gets added to single Docs posts (not the Docs main page). That is the default behavior of the plugin (please see plugin the description).
3. I cannot reproduce this. The plugin works fine on many themes, but only guaranteed to work with default WordPress themes.
Here is how a single Docs post looks with Twenty Fourteen theme.
Here is how a single Docs post looks with Twenty Twelve theme.
The problem you’re having may be due to a theme conflict, or maybe another plugin conflict. Please follow WordPress default troubleshooting steps which include reverting back to the default WordPress theme and deactivating other plugins to see if the problem persists. If the problem still persists, then I can investigate to see if the plugin is causing this. Otherwise, it really appears to be a conflict with your theme.
Thread Starter
sroser
(@supawiz6991)
2. Is there a way I can hide it?
3. I’ll start going through and disabling plugins. If I had to choose between bad theme interaction and plugin interaction I would choose plugin as Organized Docs worked fine with my theme prior to the 3.9.1 update. I’ll let you know what I find.
Thanks for your help with this.
Thread Starter
sroser
(@supawiz6991)
3. It’s a theme conflict. Bummer.
In an sidenote I noticed this in my error log even when using Twenty Fourteen Theme:
mod_fcgid: stderr: PHP Warning: Invalid argument supplied for foreach() in /var/www/vhosts/promediaonline.com/domains/gihomes.promediaonline.com/wp-content/plugins/organized-docs/organized-docs.php on line 301, referer: http://gihomes.promediaonline.com/docs/category/opendoorv1-4/
Thanks.
2. Since version 2.0 (yesterday), the plugin uses a template system which you can override in your theme (as noted in the very long changelog for 2.0). For step-by-step instructions to override the sidebar and remove the Table of Contents widget, please see: Remove the Table of Contents Widget.
3. The PHP Warning is not an error; it’s a warning. It’s only there because you are not using the plugin the way it was intended. The warning is there because you did not create a top-level Docs category to be the parent of a “subheading” (a.k.a. child-category). I can see that you only have the top-level category assigned to that Doc. Instead, you’re supposed to assign the “subheading” category to the Doc.
For example, the plugin is intended to have a top-level item, then sub-headings, then individual articles under each sub-heading, like this:
Top-Level Item
Subheading (or Section or Chapter)
- Individual Title
- Individual Title
- Individual Title
Subheading (or Section or Chapter)
- Individual Title
- Individual Title
- Individual Title
But, I can see that you only assigned a “top-level” category to the article, but no subheading (child-category). You did this:
Top-Level Item
- Individual Title
- Individual Title
- Individual Title
To fix that (and remove the PHP Notice), please see How To Set Up Categories For Docs, or the Installation Steps for the plugin.
Thread Starter
sroser
(@supawiz6991)
Update on #3. I finally sat down and took another look at this. (I’ve been using the plugin despite my menu bar not working 🙂 )
What I found is, the div container (id: primary) was overlapping the menu bar which caused it to be unresponsive. I change position: relative; to position: static; for that div container and problem solved. The div container stays where it should be and allows the menu to work.
Just thought I’d post my solution in case anyone else has the same issue.
