Last couple of days I’ve been reviewing the gSearch Plus WordPress plugin code based on some support issues raised by the community and I thought it would be interesting to write a post about this plugin. Last year, when trying to find a suitable search plugin to a client’s website I struggled a lot. Again
One of the simplest and powerful WordPress APIs is the so called Options API. It allows one to store data in the database easily, in a standardised way. One of the most used functions within this API is the get_option( $option_name ) which retrieves the value stored in DB. For one of my last projects I
I’m taking some days off on the sunny Aljezur, a small village at the south of Portugal near great beaches. Apart from all the relax, I’m also catching up with all the twitter and feedly buzz from last weeks. One of the topics that caught my attention was a tiny survey that is going on about WordPress
Fact. To build a multilingual (or multi-language?) website is hard. Much harder than a single language website version. Fact. The current available solutions to simplify designers/developers life when building multi-language websites are…very complex. Multi-language websites are probably more common outside US, and maybe, more complex in the European territory, since over here we share a
Lately, I’ve been struggling a lot with permalinks, permastructures, hierarchy slugs, and so on, for a plugin I’m working on. During these days of core reading I’ve bumped into a function called get_page_uri(), a super simple function but still deserving a full post about it. From the Codex you’ll get: Builds and returns a URI for