Earlier I received a webcast that a colleague of mine wanted me to review to see if a certain service would be a fit for our network. The file he sent over had a .WRF file ending which after some research I found out was a WebEx file meaning WebEx Recording Format. To play this type of file you need the WebEx .WRF Player which can be downloaded here or the files can be converted to WMV (Windows Media Format) to play in the Windows Media Player. To convert the file you have to use the WebEx Editor which allows you to open a .WRF file and export to WMV format. When I attempted to export to WMV I received an error which I describe below along with how I was able to resolve the error.
Setting up Virtual Private Network (VPN) connections to your office is becoming more common as work from home jobs expand. Typically the IT guy at your work should be able to provide you the necessary information needed to connect to your office securely such as IP address to connect to, username, password, and possibly domain. Once you make the VPN connection it will be as if you are working on a computer at the office so you can use things at the office such as network printers, file servers, etc.
To convert multiple <img> tags in a single HTML file such as
<img src =”hello.jpg” alt = “hello” />
to Ruby on Rails ERB helpers in your .html.erb file like this:
<%= image_tag(“hello.jpg”) %>
If you are using Git for version control then it is likely at some point you will have a project with multiple branches of code. The benefit of this is allowing various developers to work on different projects while providing an easier way to merge the code when the developers tasks are completed. One developer may be working strictly on big fixes that could need to be checked in daily while another developer may be working on a project that may take months to complete and git provides a system to merge these code branches together. Below is a quick reference for switching between Git code branches.
I knew that one of my clients web sites is running an older version of WordPress. When I upgrade WordPress I like to know exactly what version is running so I can use something like WinMerge to compare every single file in the WordPress installation to verify specifically what is going to be upgraded. This is useful if you run into any problems you can attempt to only roll back specific files to see if it resolves the WordPress upgrade issue.