Looks like there’s some kind of indexing bug in that code. When I hid occupation in the Admin panel, nothing happened. But when I hid employer and occupation, occupation went away (but not employer).
I’m marking that as a bug although don’t expect a fix in this version. I’m rebuilding the Admin pages using a different framework, so this particular error won’t be relevant in 4.0 (although I’m sure I’ll introduce newly relevant bugs!)
There is a temporary hack you might try (but it’s a bit dicey). You could look for the parent P tag for the input id _dgx_donate_occupation and try setting that display:none. It’s late Sunday night and I wouldn’t trust myself to try writing that CSS now, but that would pull both the field and the label out of play.
Good luck. Let me know what you think. I’m marking this as resolved because that’s the best answer I have for this issue. It’s definitely not you. It’s the code.
–David
I can do the CSS hack as a temp / eventual fix. I didn’t see a specific CSS class on the parent P so that’s why I figured I’d ask, before getting hack-y with it. Thanks man! 🙂
Yeah, I did some reading and apparently you can’t do parent selectors. There’s a lot of very geeky discussion on the interwebs about why that’s not possible, but net-net, it ain’t happening until I get a new version out.
Keep notes on where you made changes. You’ll want to be able to refactor them on a new release.
–David
Thanks David. I was able to hide the occupation label and field with css.
Here’s the code if anyone needs it. You need an !important on the input (as shown below) because there’s an !important in the plugin’s css that you need to override, otherwise it won’t work.
p > label[for=_dgx_donate_occupation] {
display: none;
}
input[name=_dgx_donate_occupation] {
display: none !important;
}
Awesome. Adding that to the FAQ. Thanks!
–David
