In Wordpress, have you tried uploading a file to a post only to be told "Sorry, this file type is not permitted for security reasons". Or maybe the file upload silently fails with no visible message, and nothing attached to your post? In my case I'd defined a Book post type (using the PODS framework) and added a bunch of file upload fields to support different file extensions.
Sometimes you need to detect whether a Node.js module is installed, and print a useful error message if it isn't. For example Grunt does this. The instructions are to install "grunt-cli" then add "grunt" to the package.json for the project for which you want to use Grunt. If you haven't installed grunt locally, typing "grunt" gives you a nice error message telling you what to do.
Does buying an electronic book make you into a pawn of big brother, who knows your every book purchase, can delete any book you purchase on a whim, and can change what the books say at any time? A few years ago Richard Stallman (the famous open source advocate) wrote essentially that warning against electronic books.
I'm getting up to speed with Wordpress. One thing I wanted was to quickly get a halfway decent looking mobile responsive theme, and then get on with the business of writing my content. My belief is that it's folly spending too much time on creating the perfect theme & look & feel, and that it's the content which is more important.
As a new Wordpress site owner, I'm going over every detail of the presentation to make sure everything looks right. This evening the task is improving the per-post publishing byline, and author information. As a side task, I want to have the site display my full name anywhere it would normally show the user login name. My theory is that because my mother named me "David Herron" and not "webmaster" that my website shouldn't show my name as "webmaster".
The other night talking with my girlfriend about developing a website for her, we decided that she needed a Wordpress blog. She's done quite a lot with Blogger blogs and is very familiar with them, but the goals she had were impossible given Blogger's limitations. While Drupal is a very powerful system and could have done what she wanted, it's not exactly user friendly.
One of the pain points of Chromebook users is that certain kinds of applications either aren't available for ChromeOS or are impractical. ChromeOS is a Chrome web browser, running pre-packaged on top of Linux, with a bunch of security goodness backed up by Google cloud services. It's an amazing environment but the applications are limited to running inside Chrome. Well, unless you jailbreak the device and install Crouton allowing you to run Linux.
Wake up! Theocracy is on the march in Indiana and Arkansas in the guise of protecting the right to practice ones religion. Unfortunately the law is being spun in the press as "anti-gay-rights" when in fact it's much more disturbing than that. This law says that "a governmental entity may not substantially burden a person’s exercise of religion" - in other words, Indiana and Arkansas residents now have free reign to flout laws in the name of exercise of religion.
A crazy limitation of Chromebooks has been the inability to access remote file systems (other than Google Drive). While Google Drive is a fine cloud oriented file system, and works great with Google Docs, I need to access files on my Drobo (with SMB/CIFS protocol), or various remote services like Dropbox or an SFTP connection to webservers. My needs may be a little more complex than most because of the web development work I do. Anyone contemplating adopting a Chromebook in a business would have to be nervous about handing company documents or other files over to Google for safekeeping.
Something we geeks need to do all the time is deploy files between machines. Such as, deploying a directory hierarchy over to a server for staging or production use. There's a ton of ways to do this. The old-school way is a shell script with carefully crafted rsync commands. In my case I build websites using AkashaCMS and need to deploy them to the destination webserver.