I ran into the following problem when installing Yeoman:
/usr/local/bin/yo -> /usr/local/lib/node_modules/yo/cli.js
> firstname.lastname@example.org postinstall /usr/local/lib/node_modules/yo
> node ./scripts/doctor
sh: node: command not found
npm ERR! email@example.com postinstall: `node ./scripts/doctor`
npm ERR! Exit status 127
npm ERR! Failed at the firstname.lastname@example.org postinstall script.
It turns out the problem was a permissions error with my node_modules directory. The following command fixed it:
sudo chown -R `whoami` /usr/local/lib/node_modules
If you think this may be the problem you can check the ownership of your directories with:
ls -l ~/.npm and
ls -l /usr/local/lib/node_modules
||24 Apr 21:56
Check that owner of the files match the
whoami command. In this case, it is indeed me. But if it isn’t you then above command will fix your
node_modules directory permissions and
sudo chown -R `whoami` ~/.npm
I like using Zurb’s fantastic Foundation framework. I’ve been using it heavily over the last year for many projects.
One of my favourite parts is their Reveal modal box. It’s fast, responsive and looks pretty slick. However, in versions prior to the latest version 5, it doesn’t play nicely with WordPress, if you want to add a modal box inline in your content it falls over.
In Foundation versions 3 & 4, Reveal modal content needs to be placed before the closing
</body> tag, else your modal box ends up displaying in some pretty awkward places. Not so slick.
I couldn’t find any plugins at the time to handle this functionality so I wrote a simple one to allow myself and my team to quickly and simply add modal box content in the WordPress editor using shortcodes. This prevented us having to spend time handling copy and allow editors to edit their modal box content within WordPress. It also prevents delineating otherwise well written copy.
Here's a working example
Highlight the text your’d like to place in your modal box.
Click the reveal icon in your editor toolbar.
Enter a unique ID for the Reveal.
Optionally enter some link text to replace the modal content, or manually place it wherever you like in your content.
<a href="#" data-reveal-id="yourUniqueId" data-reveal>Link Text</a>
You can also manually create a modal box like this.
Your content goes here
See my amazing modal box content by <a href="#" title="reveal-example">clicking me</a>.
The plugin can be found on my GitHub account. If anyone has any suggestions for improvements please let me know or make some pull requests.
Edit: I’ve now added a simple editor plugin for TinyMCE to make it extra easy to drop in the shortcode to your editor.
If you are receiving the
Warning: strtotime() It is not safe to rely on the system's timezone settings warning. You can solve this in several ways.
It’s a widely known fact that page speed is an important factor in most search engines’ ranking algorithms, Google has categorically stated as much in their developer guidelines.
Google’s goal is to provide users with the most relevant results and a great user experience. Fast sites increase user satisfaction and improve the overall quality of the web
Plus, we are all instinctively aware that visiting a site which loads faster is a much more pleasant experience than one which takes several seconds. A factor that should make page speed a priority regardless of any benefit to search engine ranking.
Scripts block the rendering of a page until each has been parsed in turn by the browser. Therefore, deferring the loading of non-essential scripts until after the page has loaded is a critical step in optimising a users experience of your site.
Oftentimes, with Subversion it’s pretty handy to ignore the status of files in your working copy. Cache files or other auto-generated data files can quickly become a pain to other users of your repository.
If you’re using SASS for example, that creates a lot of cache files in the
.sass-cache folder that can take a long time to checkout and generally make the place look untidy especially when you’re viewing your
Git has the useful
.gitignore file, but you can do the same tricks with Subversion it’s just not quite so obvious.
When including files within your WordPress theme use
locate_template() to allow them to be overridden by child themes.
locate_template() will search for the file within STYLESHEETPATH and TEMPLATEPATH, returning the path as a string if it exists.
Instead of going over the benefits of using a css preprocessor or the advantages of using a framework like Compass, I’ll dive right in.
I recently completed my new Hackintosh build after a couple of false starts.
I’ve put the spec and details of the build in a gist on GitHub which you can read here.
Hopefully, it will serve as a reference for my next project and maybe help someone else get started too.
The root directory of your WordPress theme can get pretty crowded pretty fast as a project get steadily more complex. One thing that I found used to frustrate me was differentiating at a glance, my partial template files, from my page template files, from all the others that find their way in there.
De-cluttering your workspace makes it easier to spot items you require at a glance, helping you to avoid losing concentration whilst you’re working.
This becomes especially true when you start collaborating on a project, using task runners and css pre-compilers. All these things can make a theme fairly bulky, so if you know where everything is going to be in advance then it can help to speed up your work process. Continue reading
In the event a client or user needs to have access to edit only the contents of a specific post, page or other custom post type without having access to edit any other posts of that type.
Say for example we have a single page in our site called ‘About Us’ which the client would like to edit, but we don’t want them to be able to edit or see our other pages from inside the admin area.
We can achieve this using the map_meta_cap filter. Continue reading