In a previous blog post, I added a custom class to a menu item so we could show that a menu item was unpublished. This blog post builds on the code from that blog post.
In addition to showing sighted users when a menu item is unpublished, we also need to show it to screen readers. We figured the best solution is to add some text to the link and wrap it in a <span> visible only to screen readers. So, I did the following after adding the class for sighted users:
We had a requirement to indicate weather a menu item was unpublished when a user who has access to unpublished content was logged in. Drupal will not display the menu item if the user doesn't have access, but if the user does have access, it will display the menu item like normal. We needed to make it clear to the user that the menu item is representing something unpublished and will not be shown to anonymous visitors. To do this we wanted to put a dashed border around the menu item.
I was working on a view that listed faculty members on a Drupal site. The request was pretty straightforward. We have profiles on the site and each profile has one or more categories such as "Core Faculty", "Affiliate Faculty", "Administration", "Staff", "Graduate Student", "PhD Student", etc. This is done with a taxonomy term on the profile content type.
I recently gave a presentation at the Central Iowa Drupal User's Group about configuration management in Drupal 8. Below are links to the slides and some resources mentioned during the presentation.
Sometimes it can be useful have more than one version of Drush globally available. In my situation, we have servers with old versions of Drush and a bunch of scripts that expect Drush to behave in a certain way. None of this can be upgraded overnight. We also want to move forward and develop on the latest stuff. So, we need several versions of Drush available to bridge the gap between maintaining what we have and upgrading to the latest and greatest.
I have a 1TB hard drive, but I'm not really using much of it, so when I started getting warnings about my disk space filling up, I was confused. I went and got Disk Inventory X to see what was using all this space. I found this:
I found some strange rendering issues happening with a site on IE that we couldn't replicate in our test environment. We finally found out those who were experiencing the issue were on the Active Directory for the same domain. Turns out, one of the group policies is to automatically set compatibility mode to on for everything in their domain. Turns out IE will respond to specific headers in order to forcefully define the compatibility mode to a specific version.