#2963 closed defect (bug) (invalid)
WordPress importer issue - Doesn't import Links
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | high | |
Severity: | normal | Version: | |
Component: | Administration | Keywords: | has-patch |
Focuses: | Cc: |
Description
Greets:
It appears that the new XML importer is not importing links.
For example, when I exported out of kpremixed.tdjc.be into kpremixed.daria.be, the links did not come over. I did confirm that the links are in the exporter file though.
Please note that I do not use the alpha version so I couldn't tell you if this has been worked on already. Please excuse me if it has. I do not see any other tickets here though discussing this issue though.
Original ticket on the MU trac: http://trac.mu.wordpress.org/ticket/82
Thanks,
-drmike
Change History (9)
#7
@
17 years ago
- Milestone 2.5 deleted
- Resolution set to invalid
- Status changed from new to closed
Importer doesn't import links, primarily because the exporter doesn't export links by design. I don't know if in a previous version links were exported but never imported but it's not the case now.
Links are exportable by OPML. See http://your.wp-blog.com/wp-links-opml.php
This ticket was mentioned in PR #2972 on WordPress/wordpress-develop by Luc45.
3 years ago
#9
- Keywords has-patch added
This PR is an alternative to #2963 using PHPCBF instead of PHP-CS-Fixer. The advantage is that it leverages the existing PHPCS/PHPCBF without adding any new tool to the stack.
It allows open PRs to resolve merge conflicts resulting from the Yoda removal proposed in this PR: https://github.com/WordPress/wordpress-develop/pull/2962
It's easy as 1, 2, 3:
- Merge this branch into the PR branch
- Run
composer update ./vendor/bin/phpcbf }}}` 3. Done.
This should be fixed for the 2.1 release. I think this would be a problem with the import then right? If the links were in the file that was exported.