And now finally committed it! Even adding parity with the Customizer (which was another reason the patch had been rejected before). I’d pretty much given up hope on this one, but picked it up and kept advocating for it. I forget his name, but there was a gent who was trying so hard to help me and I thanked him, but it was so discouraging to go to a Contributor day and do nothing. I ended up spending the entire day trying to get VVV setup on my Windows machine so I could have the exact same environment as everyone else. I actually went to my first contributor day to work on this specifically (it’s a 4 line patch, I thought it would be easy enough). But that was fixed and this hook still languished. Limit was exceeded and core didn’t want to make it easier for us to addįields. Originally it was blocked by another ticket concerning the limit of _POST variables… folks with ginormous menus would see their menus disappear when the _POST If you’re building a website using WordPress which requires users to login to the site, then you will most likely need to have a dynamic navigation menu, which displays different menu items to users if they are logged out, logged in or have a specific user role. I expected that to be the permanent solution as the original Trac ticket was opened by back in 2011. We essentially established a “community” action hook and it greatly reduced the number of people contacting me wondering why Nav Menu Role’s fields were not displaying. Then WordPress user Shazdeh had the brilliant idea to start inserting a standard hook in our own Walkers… figuring that if we all added that hook to our Walker and then all attached our fields to that hook, it would not matter whose Walker was being used by core all our plugins could be compatible. soooo many themes!) that also needed to add custom fields would add their own Walkers and we’d duel it out to see whose fields got displayed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |