I have created my website in demo folder using wordpress. I have used "Layers WordPress site builder". The problem is when I transfer all data and database to new server, pages show no data.
This is quite a big problem with LayersWP it seems. I don't know for sure what the cause is but I've noticed that the database after the import is a different size to the database exported
Not the perfect solution to the problem... but this was a good work around for me:
This plugin
https://wordpress.org/plugins/widget-settings-importexport/
Let's you import and export widgets. I'd advise leaving the working site in tact and only importing into a new database.
Related
I have the following problem - I am migrating website database from other platform to Opencart.
When I imported the images in oc_product using PHP, they are not showing in the website. The real issue is that if I manually change or type the image path, it works. Maybe it's some cache problem, but I cannot figure out why.
The images are not showing even in the admin panel - attaching picture
Here is also how my database look like - the image path is correct
My Opencart version is 1.5.6.4
Any ideas?
obviously, the image path differs for the images, when we import and thus the imagepath has to be taken care before we actually import the data.And after importing then we have to run a sql query to change the imagepath in the database.
In the question you mention an import step performed using php.
I'm doing a wild guess but maybe that for whatever reason some unprintable character has been added and is messing up the whole thing.
The easiest way to check if this is the case is to analyze the html produced to verify if there is anything odd in the img tag path.
Another quick check is to export a few rows of data that are currently acting weird and analyze the content with a smart (that show special chars) text editor.
I have been trying to import or migrate the Codeigniter database into wordpress. Is that possible to do by any means? I have searched for the solution for it at many places but was unable to find a relevant solution to it.
The real problem is that I have already got a website created in CodeIgniter but now I am making a new site for the same using Wordpress. I need to import all the data and posts contained in the older site into the new one. Maybe database migration can be a easier idea. How will be doing so??
Codeigniter is a development framework for building applications. WordPress is a system that's already built. I think you could build a large application like WordPress with Codeigniter. But it would then rely on Codeigniter's libraries and framework, so to make that happen I think you would have to rebuild WordPress from scratch. Unless Codeigniter can be used as more of a PHP editing framework as well?
Maybe a Codeigniter guru will weigh in.
Source https://wordpress.org/support/topic/codeigniter-wordpress
The main issue with this is that your CI database is not structured the same as wordpress database.
There are some tools that help you import databases in wordpress like this plugins:
WP Ultimate CSV Importer Plugin
Really Simple CSV Importer
CSV Importer
but you will have to provide them the CSV file, that you'll have to export from your CI website. I don't think the import process is very complicated but it's sure easier if you spend some time understanding wordpress databse structure, for that a great resource is the wordpress code and the Database Description page.
The complexity of the CSV file is determined by the objects that you have to import in WordPress here is a check list that its good to have when you start building a CSV file:
1) Are you importing custom post types or just blog entires?
2) Do you have extra info on your import objects that have to be imported as custom fields?
3) Do you have users that you need to import? if you do, what roles do you need to have? do you require custom roles (this makes things very complicated)
4) Do you objects have images attached to them? if they do you'll have to make sure that the import plugin is able to import images!
5) Do you have categories and tags? do they have extra info besides wordpress default info?
When I have to import data to WordPress I try to keep it as simple as possible, I'm trying to import only blog posts and their images if possible depending on the complexity of the initial website I might import categories and tags too but I might split the process before adding this and process them after I have the posts in my wordpress site (this is because I'm more comfortable working with wordpress database and functions then with 3rd party CSV generated files - it might not be your case since you have full access to the initial CI website)
In the end have a look at the plugins I've linked or search yourself some import plugins and check the CSV files they need and try to make the CI website generate a CSV file that is similar with the ones in the examples.
If you have experience with the WordPress databse structure then you can also create a script that loads your data from one database to the other one (I recommend this approach for developers that have experience with both the old websites and WordPress at code/database structure level.
if you can share your databse scheme some extra info might be given.
Export posts from CI database in CSV/XML format or SQL and then change it to CSV accordingly. after that, use WP all import plugin and select the columns correctly. Easy as that..
Ok guys, so i am 50% the way through creating a "content manager" plugin for wordpress (mainly for the internal benefit of the company i work for) that can create custom post types, taonamies and meta boes with a prety interface.
At the moment im using XML files created through php to parse and hold the data relating to "post types", "Taxonamies" and "metaboxes". The main reason i began down the xml road was so i could allow users to export to an xml file and import on another wordpress install. simple.
Although no im not sure? is it too server heavy to have the plugin recursing through directorys every each time to init the post types, taxonamies and meta boxes? would i be better served to crete 3 db tables and when i need to import or export simple do the XML from there?
would love to hear our opions?!
I would go with the database-solution. When the XML-File grows size, the parsing will take more and more time, as the whole file is read every time.
In a Database, you can select only the values you need and don't need to parse the whole document every time.
Also, realizing a XML import/export from the values stored in the database shouldn't be that much of a problem.
But if you have very tiny XML-files (like less then 100 chars) and they don't grow much, you'll have to decide if it's worth the time to change to a database.
I'm moving a site over that is currently setup in wordpress. I've not got a great knowledge on how WP works but the database all makes sense to me. I've built a custom blogging engine for the new site but I need to transfer all the old posts into the new site.
Before I go writing a script to loop through each posts then grab the image url etc and then match that up to the columns in my own database is there anything that exists already? I can't imagine I'm the first to do this!
Also - am I right in thinking that the image(s) for the post are _wp_attached_file with the corresponding post_id in the wp_postmeta table?
I've tagged this with php for Wordpress but happy for scripts in Python or RoR too if they exist.
Thanks
Is the standard wordpress export not detailed enough? I find this a very handy tool: http://en.support.wordpress.com/export
There is a plugin that imports your posts into a CSV file. It would be simpler to write a parser for that, I think - instead of writing a script to query the WP DB
I'm developing an image gallery for one of my customers, they want a very minimal, simple and easy user experience. The image gallery must contain a title and description of each image, we have created a app to upload the images and set titles and descriptions this is stored in a mySQL database. We're developing this site with php.
Before I go off and develop this, does anyone know of any opensource galleries that tie into a mySQL database with similar functionality? Or maybe this approach is naive? Maybe I should approach this from a different direction and not use a mySQL backend..
Any advice is very welcome.
Josh
This one looks decent: http://gallery.menalto.com/. It supports MySQL and a bunch of other DBs.
For something this simple, you could get by without a database (however I doubt you would be able to have a title and description for the images without using a flat-file database; not recommended). To do it without a database, try this: http://spgm.sourceforge.net/.
However, if you already have written the uploader which works with MySQL, I would go with the database option and tweak it if necessary to work with the first link I posted.