標題: The script 13 [打印本頁] 作者: tlegpjem 時間: 2016-3-7 11:20 標題: The script 13
Importing archives into WordPress
That a fairly simple usage of WordPress XML, and when we imported our content from the Bangor Daily Media we did a lot more.
For example, we imported all our content with a hidden post meta (_old_id) price of the article ID in our outdated CMS. Then, we utilised the CP Redirect plug-in as a template for a completely new plugin to redirect people today clicking on old links towards the new URL.
We also found that using the tag quickly bogged down us. As with any newspaper, there are plenty of people who have written just one or simply a few articles for us, and we didn want to create accounts for all of them.
Most people don embed images within posts. Rather, we problem for all images attached to the submit and display them in first place on the post and in this sidebar (more about this in a afterwards post). So we natively imported the photographs so they would become contraptions. WordPress automatically copies almost all attachments onto the server, so that we didn have to worry about getting all the pictures off our old server. Importing the images is just as straightforward. is set to the ID on the post, is set to receive and is set to add-on. The image path goes in, and the caption goes in.
We broke your XML files up by 1,000 posts at a time. Overall, we had more than 100 XML data files. We also imported everything onto a local machine and then forced the database back up to our webserver. All told, importing everything had taken several solid days of operate.
If you working on a site much wider than ours, you might look at importing posts directly into Wp using the API, but to be honest I actually not sure how much overhead that will save.
The script, that you've to modify a bit but i hope not too much, is on github.
This can be great stuff! While it is fairly easy to import archives in this way, I do share your soreness as Kamagra Oral Jelly we suffered through converting 20+ sites to WP. Love the idea of this blog, really need we could have started with variation 3.0.
Have you came across any performance issues in the course of peak times yet? In that case, care to share what measures you took to keep your web servers from tilting?
We had to do some major caching work to preserve our sites up and running. Figured out fairly quickly that a single website with 100k posts, 700k meta during excessive traffic times was not an excellent combination!
