Dr Fragen in the operating room


  • GitHub Updater & GitLab

    GitLab Support

    I’ve finally been able to add support for GitLab in the GitHub Updater v4.5.0. Additionally, support for GitLab CE and GitLab Enterprise are also included. All that’s required is an additional header with the base URI for the GitLab server. As an example, GitLab CE: https://gitlab.example.com or GitLab Enterprise: https://gitlab.example.com.

    Extras for GitHub

    Support for GitHub Enterprise is also included using a similar header, GitHub Enterprise: https://github.example.com.
    Support for updating from GitHub assets is also included if an asset exists for a tagged release. It will be preferentially used for the update. Using an asset’s URI for the remote installation of a plugin or theme will also function as expected.

    Under the Hood

    A bit of refactoring has been done as well. An abstract class API has been created to simplify the structure of all the git server API classes. Additionally a class Messages has been created to hold admin notices.
    The class Base has been refactored to hold information regarding the added APIs in static arrays for use throughout the codebase.
    I hope everyone likes the changes and updates. As always, if there are problems or improvements, please create an issue on GitHub.

  • Add Custom Header Images

    After using this plugin for quite a while I decided to refactor it and submit it to the WordPress Plugin repo. I figured maybe someone else might find it useful.
    What the plugin does is add all images that have been uploaded to a page titled The Headers to the header image array and allows for the selection of any of them or a randomized selection via the Customize > Header Image menu on the front end of the site.
    First the plugin removes any of the default header images, if present, and then adds all the images that have been uploaded to The Headers page as the new header images. If you don’t have a page named The Headers then the plugin will not activate. The Headers may be a private page.
    The idea for the plugin came from the article written by Julio Biason who was inspired by wpti.ps.

  • The Events Calendar Category Colors Plugin

    It’s been a wild couple of days figuring this one out. Special thanks to Jonah West for all the help and encouragement. This plugin seeks to greatly simplify the ability to create background colors for your categories in the month view when using The Events Calendar plugin. It requires The Events Calendar v2.0.5 or greater.
    TEC Category Colors uses the Tribe Setting API to integrate its settings into TEC’s settings page.
    You can grab it from the WordPress Repository.

  • Add Alarm to Events Calendar PRO

    Thanks to Joey Kudish and Jonah at Modern Tribe, Inc., I’ve converted my original hacked together code to add an alarm to a calendar event created using the Events Calendar PRO WordPress plugin into a plugin of my own. You can see/follow the original discussion on the Modern Tribe forum.
    This plugin requires the Events Calendar PRO plugin. You will have to create an Additional Field from The Events Calendar Settings page.

    You can then download, install and activate the The Events Calendar PRO Alarm plugin. If/when this functionality ever becomes part of Events Calendar PRO simply deactivate the plugin.

  • WordPress Automatic Updates

    I think I finally have the automatic updates feature of WordPress working. Previously, when asked for my login info for the FTP connection I would get some vague connection error. It’s a permissions issue. Some permissions for files/folders need to be set for web server user, in my case Apache2, or _www on OS X Server.
    The answer mostly comes from looking for why WordPress asks for connection information. Be sure to read the comments. Definitely add the following to wp-config.php.

    define('FS_METHOD', 'direct');

    So far, my solution seems to be something like the following, from the wordpress directory.

    sudo chown -R _www ./wp-content*
    sudo chown _www ./wp-admin/update*

    It seems to work, however, the information about what should be happening with the update seems to be in an endless loop. I let it run for a bit and when I check to see if the plugin or theme is updated it seems to have the newer version, but I’ve no real way to check or to know how long to let the process run.
    Very confusing.
    When I encounter more updates I’ll see if this really does work. BTW, updated to WordPress 3.0 for all the new goodness.
    This works fine for plugins and themes but not for the actual WP updates. Also, I just let it run until the browser doesn’t seem to be loading the page any longer and the updates are done. Something’s clearly not working as expected with this and OS X Server but I don’t know what it is.
    Update 2
    Thanks epor for the missing piece.