Password Protect Posts Created via Gravity Forms
A quick little plugin that sets the password for posts created via Gravity Forms. This came about as the result of a faculty request today. In this case it’ll grab the first form field and use that for the password. You could hardcode it into the plugin itself but I thought this gave a bit more flexibility. With this option you can make that field something that the user could set or you can make it hidden and set it consistently for all submissions.
Simple but maybe handy for someone else.
Here are a few plugins I’ve got in the WPMU install I’m running. Most, if not all, were a result of my sordid association with WPMU cult leader, Jim Groom. He’s likely posted on each multiple times but it’s hard to find them among all the old cartoons and toy posts- besides I had to make a list to send to our people so I figured I might as well post it. These are all installed in the mu-plugins folder. More Privacy Options This let’s users set up additional options in the privacy page for blog admins. You can make sure the blog is visible only to those logged into your WPMU site, only visible to members of the blog, or only visible to admins. User Themes Revisited This plugin gives individual blog admins the ability to tweak CSS or theme templates individually- the edit theme ability in single user. It’s a little awkward at first but really a key plugin for me. Essentially, you copy the theme over to the individual blog and then can edit it without changing things for everyone on the WPMU install. New Blog Defaults This plugin lets you customize how the new blogs are created. You can customize a lot of key elements and do things like putting the initial “Hello World” post in […]
If you’ve got a site running on HTTPS and you try to throw in some HTTP content, the browser gets nervous. If you’ve recently made a shift to HTTPS you might notice content that was successfully embedded disappearing. If you look in the browser (right click>inspect element in Chrome), you’ll see an error like the one above. What you want in this scenario is protocol relative URLS . . . essentially a URL without the leading http/https. That lets the page load via the one protocol that matches (assuming it exists- some sites won’t supply HTTPS options).Reading more about it, it seems forcing the HTTPS connection where available is encouraged. I’ll think about that more later. I ran into this problem with files we uploaded via Gravity Forms prior to the switch to HTTPS. There are a number of ways to deal with this (including search/replace at the database level) but we’re under a very heavy load at the moment and I just needed a quick fix. This solution will also allow people to do whatever they want on an ongoing basis better than a database response. This tiny little filter plugin is the result. All it does is use PHP’s preg_replace (regex) function to find any instances of HTTP or HTTPS (capital or lowercase) and remove them. I’m still […]
flickr photo shared by Little Orange Crow under a Creative Commons ( BY-NC ) license The goal here was simply to take the Flickr API knowledge I’d gained earlier and apply it within a WordPress widget. In doing so, I learned a few things. The primary one being that I often harm myself by being fairly good at making stuff work rather than understanding what I’m doing. That’s what I did here. The Flickr API thing was pretty legitimate. I knew what I was doing there but I pretty much crammed it into a widget plugin template without really understanding the whole thing. That led to more confusion around print