I am having a ton of issue with attachments, I am so sick with wp import/export plugin, I feel like doing phpmyadmin is the best way to do anything. I just moved a new version of one of my themes to the live demo server and the best way to do it was via SQL and went smooth.
Now exporting the sample_data.xml does export the XML file properly but fails to import Media on a different site.
Do you know any better way to go around this? Is there a tutorial or some wp trick to do I am not aware of?
We actually made a 1 click import for some features in our new theme. Problem is, by importing the database some stuff cannot be imported, like widgets, so we end up just importing elements that we couldn’t with the wp plugin. If you find something please let me know because we couldn’t
I use a modified version of the importer plugin and changed the class name so it doesn’t conflict. You can also make it look almost exactly like the demo by using use add_option() in the importer to import data into your options panel such as social icons, fonts, colours, settings and other things that the importer wouldn’t usually do.
You can also use set_theme_mod() in the importer so it also sets the menu location, something the default importer doesn’t do.
I might post an example if you guys are interested.
EDIT: Also 1Click demo installers can drastically cut down your support tickets. It is definitely something to look into.
I use a modified version of the importer plugin and changed the class name so it doesn’t conflict. You can also make it look almost exactly like the demo by using use add_option() in the importer to import data into your options panel such as social icons, fonts, colours, settings and other things that the importer wouldn’t usually do.
You can also use set_theme_mod() in the importer so it also sets the menu location, something the default importer doesn’t do.
I might post an example if you guys are interested.
EDIT: Also 1Click demo installers can drastically cut down your support tickets. It is definitely something to look into.
I use a modified version of the importer plugin and changed the class name so it doesn’t conflict. You can also make it look almost exactly like the demo by using use add_option() in the importer to import data into your options panel such as social icons, fonts, colours, settings and other things that the importer wouldn’t usually do.
You can also use set_theme_mod() in the importer so it also sets the menu location, something the default importer doesn’t do.
I might post an example if you guys are interested.
EDIT: Also 1Click demo installers can drastically cut down your support tickets. It is definitely something to look into.
I use a modified version of the importer plugin and changed the class name so it doesn’t conflict. You can also make it look almost exactly like the demo by using use add_option() in the importer to import data into your options panel such as social icons, fonts, colours, settings and other things that the importer wouldn’t usually do.
You can also use set_theme_mod() in the importer so it also sets the menu location, something the default importer doesn’t do.
I might post an example if you guys are interested.
EDIT: Also 1Click demo installers can drastically cut down your support tickets. It is definitely something to look into.
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.
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.
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.
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.
Nobody 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.
Nobody 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.