Just a quick note here that I’ll close I Code Your Design at the end of this month. The service will of course continue but I think it doesn’t really need a separate domain to host it. Will update the URL after I’ve done the migration.
In short, I didn’t fall in love with designers (as a WordPress developer) until I found they are actually my ideal and favorite clients.
Here’s the story how I figured that out and hence created my first productized service – I Code Your Design.
In this post, I want to introduce you a soon-to-be-launched productized service. It helps designers to convert their beautiful work into a fully functional but also light-weighted WordPress theme.
I know it doesn’t sound that charming, but if you are a designer who’ve ever sworn you’ll never purchase from any theme shop again, please read this up, I might have something for you.
The following snippet saved me a bunch time when dealing with a recent project. The scenario was I created 2 custom post types and they share the default “category” taxonomy with Posts. On the post type archive page, I have to display the category links so users can filter the posts.
The difficult part was I wanted to only show categories that have posts in the current post type. The following snippet came from StackExchange, with the function hook to the terms_clauses filter, now we can use a custom argument called post_types in the function get_terms.
The post_types can be an array so you can get terms like this:
get_terms( array( 'post_types' => array('post', 'cpt1', 'cpt2'), 'taxonomy' => 'category' ) );
or just:
get_terms( array( 'post_types' => 'cpt1', 'taxonomy' => 'category' ) );
Please go to StackExchange to upvote the answer if you find it helpful to you too.
For years I thought I understood “cookie” very well. Especially when I figured out it’s a great way to share data between JavaScript and PHP. I always got results as I expected in many projects with this approach.
“Why not just saving the values to database and just use PHP to access it?” you might be asking. Most of the cases are because we need to access such values in JavaScript. For example, we have an eCommerce website and we let the user chooses her location with a lightbox window. The lightbox should only appear once and after the user makes the choice, it just goes away. Read More…
When working with Gravity Forms, to get your post data updated at the front end, it can’t happen without this great plugin: Gravity Forms: Post Updates.
While it’s really awesome (and free) but like every (free) plugin in the wild, there is always one or two (…or three) things just can’t work as we expected.
The problem I met is, when updating the post, the post tags and some custom fields kept got wiped out. Because the post tags field was not added to the form and I hide those custom fields conditionally, I thought they got wiped out just for they didn’t exist in the form.
But soon I found the custom fields were in the form but got hidden with inline CSS “display:none” (added by Gravity Forms). Then I went back to the source code, realised the Post Update plugin deletes meta values if you check the “Unique Custom Field?” box in the field settings. By unchecking this box, my data is safe now.
As to the post tags, I had to add it to the form and applied a CSS class “gform_hidden” to get it hidden. (If I just set it to “Admin Only”, it still got wiped out after form submission.)
So lessons learned here:
gform_hidden“, set it visible to “Admin Only” won’t work, it would still get wiped out.