search

jmuspratt / craft-fieldguide

A simple Craft CMS plugin that lists all your fields and their handles, grouped by section
33 stars 6 forks source link

Nothing shown on Field Guide tab? #5

Closed superwick closed 9 years ago

superwick commented 9 years ago

Not seeing anything listed on the Field Guide tab in my CP (it just shows the "FieldGuide Dashboard" heading and nothing under it), and I have several fields set up. Not seeing anything in the Chrome console, or any errors in craft/storage/logs/phperrors.log. Anywhere else I can look to help troubleshoot? I've also uninstalled/removed and re-installed to see if that would work.

jmuspratt commented 9 years ago

Hmmm, have you added those fields to a section yet? Nothing else comes to mind.

superwick commented 9 years ago

Yep. Sections are added and being used in entries. Weird.

On Thu Feb 05 2015 at 11:58:47 AM James Muspratt notifications@github.com wrote:

Hmmm, have you added those fields to a section yet? Nothing else comes to mind.

— Reply to this email directly or view it on GitHub https://github.com/jmuspratt/craft-fieldguide/issues/5#issuecomment-73080362 .

jmuspratt commented 9 years ago

Darn. I'm not a plugin expert, but I suppose you could try commenting out sections of the plugin code and see if you can get anything to output (using dump() if you have to). Or try it on another Craft installation to see if you can target what's different about the problematic one.

superwick commented 9 years ago

Well I've tracked down the culprit... the plugin is getting all the data fine. It's just that it's not being displayed because of this CSS in cp.css: 

.grid > .item {
  display: none;   /* here be the culprit */
  padding: 7px;
  -webkit-box-sizing: border-box;
  -moz-box-sizing: border-box;
  box-sizing: border-box;
}

See the above commit on my fork for fix that worked for me.

superwick commented 9 years ago

...and I just figured out WHY that worked for me. I had an unescaped HTML tag in the instructions for one of my fields, so that was invalidating the rendered HTML on the Field Guide page. When I properly formatted that field's instructions with Markdown, it all works as it should. Derp. Fee free to deny/ignore that pull request. Thanks