Artillegence saidNobody spoke about using SQL dump or SQL instructions… I think that it is not even allowed as you can see here: http://support.envato.com/index.php?/Knowledgebase/Article/View/472/85/wordpress-theme-submission-requirements . At a certain point you have this rule: The database shouldn’t be accessed or modified directly. If there is a defined function that can get the data you need, that must be used instead. Use $wpdb and its methods to interface with the database instead of rolling your own.
xml import is best for importing pages and posts, there are problems when you try to insert using database options, when you save sql dump in a file , if there are extra characters present it won’t work and manipulating core tables is not recommended . Best way is to export as encoded text even serialized string wont work if there is a new line.
So, as an example, here’s how I add a page:$new_page_title = 'About Us'; $new_page_content = 'This is the page content'; $new_page = array( 'post_type' => 'page', 'post_title' => $new_page_title, 'post_content' => $new_page_content, 'post_status' => 'publish' ); $new_page_id = wp_insert_post($new_page);
Pretty simple, huh?
yeah I use that too for my express installer .. but its not usable for replicating demo as it … just my opinion
Pirenko saidxml import is best for importing pages and posts, there are problems when you try to insert using database options, when you save sql dump in a file , if there are extra characters present it won’t work and manipulating core tables is not recommended . Best way is to export as encoded text even serialized string wont work if there is a new line.
Wordpress allows us to enter posts, pages, custom post types and other into the database so that is basically what I do with some PHP instructions. We can even add images to the media library and connect them to posts using their ID.
As far as I know this is better than XML import, because it works everywhere.
Hey guys I am working on a new version of my 1 click installer .. I will try to make it as a plugin and add on git for everyone
Hey guys , recently my theme got soft disabled on the fact that theme check was taking over 30 seconds to test the theme. I would really like a clarification why this is a requirement factor as the time taken depends on factors such has number of files ( including css ,sass , js) and processor speed of Reviewers MAC or PC not that theme has bugs .
1. Simply when sass files are present in theme folder, the number of test cases increases you can see here
and without sass files
. It has nothing to do with wp standards ?
2. I can make it clock under 20 seconds by adding all code in lesser files but that goes against re usability .. I want framework to be flexible and want frontend code to be in templating form.
3. Neither in themeforest requirements or wp guidelines it is mentioned that if theme check takes more than 30 seconds theme is not complaint.
I dont mean to rant I love the standards , I would appreciate a response on why this is being counted as a requirement.