Has anyone else noticed the following note on http://codex.wordpress.org/Function_Reference/WP_Query#Interacting_with_WP_Query
Pagination Note: You should set get_query_var( ‘page’ ); if you want your query to work with pagination. Since Wordpress 3.0.2, you do get_query_var( ‘page’ ) instead of get_query_var( ‘paged’ ).
Well, I just tried it and it does not work but the old way [ get_query_var( ‘paged’ ) ] still does.
Anyone else observed this too?
saw your email and replied to it just now. I send the attachment you send me back with my notes on it
Hey Kevin, just replied to your email!
Yep! definitely child themes is the way to go. I’ve been using them for quite sometime now and it works really good.
Of course don’t forget to “educate” your buyers by providing enough documentation of practical “How to’s” examples that they can use as a basis for their own modifications. There’s no need to go overboard because support is one thing and custom work is another.
I aim to provide enough (basic) information for those that have some average ability with code. Those that know their way around with development anyway don’t need me and those that don’t, well… that would be custom work right? (who does the work in the end is a different matter.)
In any event, the point is that WordPress does offer the capability to completely separate your customizations in a very smart fashion.
Exactly! And this is how I release my themes. A parent theme with at least one or 2 child themes
What do you guys think? Too complicated?
No, but authors need to remember that people will need some guidance (some tutorials with practical examples) on how to go about editing template code in the child theme.
This is what I do and it works quite well
I don’t know if this may help but if you have a look here: http://codex.wordpress.org/Function_Reference/wp_insert_post
you’ll see the following said about pages:
NOTE (added 10/1/2009): The page_template key was removed from the $post table and is now located in the wp_postmeta table. To set the page template of a page, use update_post_meta instead.
Thanks for that but I’m still stuck
I would even pay for someone to help if there was someone willing to. Anyone?
The Special characters are not correctly encoded.
What I’m using:
I am using
encodeURI(); which encodes but wrongly and therefore the parameters cannot be used in my database query later on.
Does anyone have any suggestions on how to solve the problem? Please?
I had the same question a while ago and I just downloaded the html version of the panel using a Firefox plugin and I placed the files in my server. Problem solved.
Ivor, can you please tell me what Firefox plugin you used for this? I might do the same for my themes as I do get a number of requests from people that want to see the backend.