Convert posts from an existing WPML multilingual site via WXR Export/Import for MultilingualPress
Home Page: https://wordpress.org/plugins/wpml-to-multilingualpress/
License: GNU General Public License v2.0
This. When a user import fails due to duplicate login/e-mail, it will not reachable by any reference like post-author or something else as it is «unknown» for the ID map.
If wpml2mlp in a Multisite aktiv also there have to exisxts under (Tools/import)[wp-admin/import.php]a section for the wpml2mlp wxr parser.
Despite the Readme says it is possible to activate the plugin on a single site, this does not work. The export should be accessible on a single site, the import functions must be disabled then.
We have to implement a custom wxr importer for the created wxr export files from single wmpl installation. We could not use the WordPress Importer-Plugin, there is no Hook to parse custom wxr elements.
If wpml2mlp in a Multisite aktiv also there have to exisxts under (Tools/import)[wp-admin/import.php]a section for the wpml2mlp wxr parser.
At the 0.0.1.2 version of wpml2mlp we have turned the xliff export format to the WordPress defauld wxr. On every Post there have Translations that are appended at the post item.
<wp:translation lang="en" post_id="2401"/>
<wp:translation lang="de" post_id="2491"/>
<wp:translation lang="nl" post_id="2071"/>
<wp:translation lang="es" post_id="2566"/>
<wp:translation lang="fr" post_id="2593"/>
Our wxr parser have to map the Translations to mlp.
Subtasks:
Whenever element IDs are stored as meta data value, the relation will break on import when these IDs changes. So right before we import meta data we provide a filter passing the meta data and the instance of the ID mapper.
As everything else, this API has to be independent of the progress of the import, so it is not stated that the ID is available at the moment of the first processing.
This will be part of the meta-data importer described in #57
Todo:
Import\Filter\ValueFilterableInterface.SingleIdMetaValueFilter, RecursiveIdMetaValueFilterImport\Data\MetaFilterListInterface and Import\Data\MetaFilterListInterfaceImport\Service\ImportMetaFilterInterface and Import\Service\ImportMetaFilterw2m_import_meta_not_filterable (in the connector service) when a filter is not filterable right nowImport\Data\ImportListeningMetaFilterListImport\Module\ResolvingPendingMetaFilterController\MetaFilterApiw2m_import_meta_filterData\MetaFilterList to have only one filter instance per type/key pair. If one of the composed filter is not able to filter the value, no other filter must be applied in the first time (Service\ImportMetaFilter). Otherwise we would get in trouble with multiple record metas on clean-up.at the current solution we work with an array like this:
'locale_relations' => array(
'en_US' => 13,
'fr_CH' => 32
)
A better way is working in this case with an object:
interface W2M\Import\Type\LocaleRelationInterface {
/**
* @return int
*/
public function origin_id();
/**
* @return string
*/
public function locale();
}<guid isPermaLink="false">https://some-url.de//?p=44330</guid>
The current readme.txt needs a better description and probably a screenshot.
If the Plugin aktivated in Singlesite with wmpl we show a splesh screen with informations to install a neu Multisite oder setup a multisite from the current Installation.
At the splash Screen are the Exportfiles linked. At the end of the Screen is a Button like Plugin deactivate now click on it the export files will deleted and the Plugin turns off.
The current idea of the observer interface depends on the mutable behavior of the Type\WpImport{TYPE} objects. This has two downsides:
$importType->id( $new_id ); which breaks encapsulation.w2m_{TYPE}_imported actions.Further, the current Import\Data\IdObserverInterface is limited to be used for all types. Listeners to single types are not designated, which violates the interface-segregation principle.
The refactored structure:
interface Import\Data\PostImportListenerInterface {
/**
* @wp-hook w2m_post_imported
*
* @param WP_Post $wp_post
* @param Import\Type\ImportPostInterface $import_post
*
* @return void
*/
public function record_post( WP_Post $wp_post, Type\ImportPostInterface $import_post );
}
along with that there are Import\Data\ImportTermListenerInterface, Import\Data\ImportUserListenerInterface and of course Import\Data\ImportCommentListenerInterface.
The Import\Data\IdObserverInterface will be replaced by Import\Data\ImportListenerInterface which is just a »semantic« interface and extends all these new four types:
interface ImportListenerInterface extends
ImportPostListenerInterface,
ImportTermListenerInterface,
ImportUserListenerInterface,
ImportCommentListenerInterface
{}
This requires also a refactoring of Import\Data\PresetUserTypeIdMapper, Import\Data\ImportListeningTypeIdMapper and Controller\DataIdObserverProvider.
The destination language on xliff-files is wrong.
Note: wpml set the current lang at admin area by Filter at the post overview and at the admin bar!
In this case the current lang is set by the method Wpml2mlp_Helper::get_main_language(); here is going some wrong, so that we get not the real current lang.
Solution
A save way to get the current lang-code is to use the constant ICL_LANGUAGE_CODE lock at the wpml API
At the moment, there will be no warning, when date strings are not parsable for some reason in Comment-, Post-, User- and Term parsers.
When we run the Import more then one time, then we get doublicated data.
At the current version terms has no translation relation at the export.
Notice: Undefined variable: wp_is_multisite_check in /var/www/wp-plugins/wpml2mlp/inc/Wpml2mlp_Prerequisites.php on line 24
at the load after login on Dashboard.
WP_DEBUG is TRUE and xdebug is active
When the Multisite is already installed, the WPML and WPML2MLP plugins need to be activated on the main single site that needs to be exported, not network wide. I got confused that the export didn't work.
To do: Enhance the documentation and maybe adding a admin notice that both plugins need to be installed at the main sub-site when activating them network wide.
I'm not sure if the wp: namespace in the xml should be used by our import. It might lead to incompatibilities with the default WP importer.
https://en.wikipedia.org/wiki/XML_namespace
https://stackoverflow.com/questions/5071948/set-up-my-own-xml-namespace
Currently the structure of an exported term looks like this:
<wp:category>
<wp:term_id />
<wp:category_nicename />
<wp:category_parent />
<wp:cat_name />
<wp:category_description />
</wp:category>This forces the importer to tread terms depending on their taxonomy.
It would be way easier to pass the taxonomy as a separate node to the complete term:
<wp:category>
<wp:term_id />
<wp:category_nicename />
<wp:category_parent />
<wp:cat_name />
<wp:category_description />
<wp:taxonomy>category</wp:taxonomy>
</wp:category>At the current version of wpml2mlp is no export data for authors.
Remove minimum-stability as it makes only sense for root packages: https://getcomposer.org/doc/04-schema.md#minimum-stability
Remove version as suggested in the docs: https://getcomposer.org/doc/04-schema.md#version
Currently there are several error actions for errors that may occur during one logical process (importing post, importing file, importing term).
I would like to see them combined to one action per entity:
wp_import_post_error when something went wrong with the post importing process (including set term relations and meta) The domain should be handled by WP_Errors error code (post, post_meta, post_terms).wp_import_file_error. This includes errors on any file system operation as well as HTTP.The signature should follow the those of the other importers (described in #39 ): First parameter is an instance of WP_Error followed by the import object. Any other contextual data (response values, IDs, etc.) can be passed as data with the WP_Error object.
Subtask of this: #51
Add the Author-ID to the Posts in the export file.
<item>
<!-- ... -->
<wp:post_author>1</wp:post_author>
<!-- ... -->
</item>In inc/Wpml2mlp_Helper.php the function get_language_info() retrieves the language for the given post. The SQL retrieves the first entry it gets by the post ID from the database. However, in the wp_icl_translations table there can be more than one entry for the post ID, with a different element_type, on grown WPML installations:
As you can see in the above screenshot, the row with the element_type comment has a different language_code as the second entry, which is the one we need. As in the get_language_info() function the SQL only gets the first row, the exported XLIFF files are completely mixed up with wrong entries on each language file.
To do: The SQL does not only need to check on the correct post ID, but also on the correct post type. In the function get_all_posts() of the inc/Wpml2mlp_Helper.php file, the post types are selected and used to retrieve the posts needed for the export. The same get_post_types() function can be used to check on all possible post types within the wp_icl_translations table for retrieving the correct language of each post.
The import and export tool is currently on a settings page. Should we move to the tools page?
After updating the dependencies I get the following errors:
$ composer update --prefer-dist
Loading composer repositories with package information
Updating dependencies (including require-dev)
- Removing antecedent/patchwork (1.3.5)
- Installing antecedent/patchwork (1.4.0)
Loading from cache
$ phpunit -c phpunit-integration.xml
Warning: flock(): Illegal operation argument in /var/www/projects/inpsyde/wpml-to-mlp/wp-content/plugins/wpml2mlp/vendor/antecedent/patchwork/src/CodeManipulation/Stream.php on line 185
Warning: file_put_contents(): Exclusive locks are not supported for this stream in /var/www/projects/inpsyde/wpml-to-mlp/wp-content/plugins/wpml2mlp/vendor/inpsyde/wp-tests-starter/src/WpTestsStarter/WpTestsStarter.php on line 304
When setting the dependencies back to the previous state, the errors not longer appears.
Reflect the structure from the parsed data #25 in an API. Don't deal with arrays.
Hi,
I've got an empty site.
Just installed Multilingual Press (free version) and WPML to MLP.
When I "network activate" wpml to mlp I've got this error
Fatal error: Call to a member function get_name() on string in /mysite/wp-content/plugins/multilingual-press/inc/db/Mlp_Content_Relations.php on line 47
Currently there's the Service\ObjectImporterInterface with the methods import_post() and import_term() (and later there would have been import_author().
For many reasons it makes more sense to split these interface into three separate ones:
namespace W2M\Import\Service;
use
W2M\Import\Type;
interface PostImporterInterface {
public function import_post( Type\ImportPostInterface $post );
}namespace W2M\Import\Service;
use
W2M\Import\Type;
interface TermImporterInterface {
public function import_post( Type\ImportTermInterface $term );
}namespace W2M\Import\Service;
use
W2M\Import\Type;
interface UserImporterInterface {
public function import_post( Type\ImportUserInterface $post );
}The implementations should have the names WpPostImporter, WpTermImporter and WpUserImporter.
When the post importer don't find any local author ID with the mapper, trigger an error. Follow the scheme described in #48
Format for Ex-Import is XLIFF.
<?xml version="1.0" encoding="utf-8" ?>
<xliff version="1.1" xml:lang='en'>
<file source-language='en' target-language='de' datatype="plaintext" original="Sample.po">
...
<body>
<trans-unit id="1" restype="button" resname="IDC_TITLE">
<source>Title</source>
</trans-unit>
<trans-unit id="2" restype="label" resname="IDC_STATIC">
<source>&Path:</source>
</trans-unit>
...
</file>
<file source-language='en' target-language='fr' datatype="plaintext" original="Sample.po">
<trans-unit id="1" restype="button" resname="IDC_TITLE">
...
</body>
</file>
</xliff><?xml version="1.0" ?>
<xliff version="1.0">
<file original="global" source-language="en_US" target="fi" datatype="plaintext">
<body>
<trans-unit id="1">
<source>Application Name</source>
<target>Sovelluksen nimi</target>
</trans-unit>
<trans-unit id="2">
<source>Home</source>
<target>Koti</target>
</trans-unit>
<trans-unit id="3">
<source>Exit</source>
<target>Poistua</target>
</trans-unit>
</body>
</file>
</xliff><xliff xmlns='urn:oasis:names:tc:xliff:document:2.0' version='2.0'
srcLang='en' trgLang='fr'>
<file id='1'>
<val:validation xmlns:val='urn:oasis:names:tc:xliff:validation:2.0'>
<val:rule startsWith='*'/>
</val:validation>
<unit id='1'>
<originalData>
<data id='d1'><B></data>
<data id='d2'></B></data>
</originalData>
<segment>
<source>* Hello <pc id='1' dataRefStart='d1' dataRefEnd='d2' type='fmt' subType='xlf:b'>World</pc>! </source>
<target>* Bonjour <pc id='1' dataRefStart='d1' dataRefEnd='d2' type='fmt' subType='xlf:b'>tout le monde</pc> ! </target>
</segment>
<segment>
<source>Welcome in the universe of <pc id='2' dataRefStart='d1' dataRefEnd='d2' type='fmt' subType='xlf:b'>XLIFF 2</pc>.</source>
</segment>
</unit>
</file>
</xliff>What happens when the new MultiSite is different to the source?
Example: Pictures are loaded from the source by there `attachment_url ' and imported to WordPress with default sizes. Is on the source a Theme activated, which uses its own thumbnail formats and this is not installed or active on the target Thumbnails are not generated.
Question: Should wpml2mlp migrate not only the content but remember also to characteristics of the source, when differences block the import and provide instructions to the user?
Fact is: the real problem arises if the new multisite characteristics are not equal to the source. Users perform a export/import and expect that everything works as before. In some cases that will not work because the user forgot to set your systems equal. This affects not only that thumbnail example!
Was passiert eigentlich wenn die neu aufgesetzt Multisite sich von der Quelle unterscheidet?
**Beispiel:** Es werden Bilder anhand der `attachment_url’ von der Quelle geladen und nach WP-Standard Importiert. Hat die Quelle nun ein Theme, welches eigene thumbnail formate nutzt und ist dieses auf dem Ziel nicht installiert oder aktive werden Thumbnails nicht erzeugt.
**Frage:** Sollte wpml2mlp nicht nur die Inhalte migrieren sondern sich auch auf Eigenschaften der Quelle merken, Prüfen, bei Differenzen den Import blockieren und dem Benutzer Handlungsanweisungen geben?
Fakt ist: das eigentliche Problem entsteht denn wenn die neue Multisite installiert wird. Benutzer führen einen Export, einen Import durch und erwarten, dass alles wie gehabt funktioniert. Es wird Anwendungsfälle geben, bei den das nicht funktionieren wird, weil die Benutzer vergessen Ihre Systeme gleich einzustellen. Das betrifft nicht nur, dass Thumbnail Beipsiel!
Implement attachment import.
Example on how to use wp_handle_sideload(): http://wordpress.stackexchange.com/a/36083/31323 (the answer shows the usage of media_handle_sideload() but the structure of the parameter is identical to the one for wp_handle_sideload().
W2M\Import\Type\ImportPostInterface:namespace W2M\Import\Type;
interface ImportPostInterface {
/**
* ...
*/
/**
* @return string
*/
public function remote_attachment_url();
}W2M\Import\Type\WpImportPost.<wp:attachment_url> in W2M\Import\Service\WpPostParser if exists. Propagate an error if it not exists and the post is of type attachment.W2M\Import\Service\WpPostImporter to handle the file:
_wp_attached_file if we cannot force a 1:1 mirror of the file paths of the remote system)Fatal error: Maximum execution time of 30 seconds exceeded ...
If we have a lot of content at the source blog the execution needs more time we have.
refactor the export see https://stackoverflow.com/questions/3212982/need-to-write-xml-using-php-how and http://php.net/XMLWriter
Hi,
the following notes are the result of a short review. They are in no particular order.
mlp_ is reserved for the main plugin.WPML2MLP_Importer to a separate file.Mlp_Site_Relations or Mlp_Content_Relations, they are provided by MultilingualPress.add_action() and add_filter()) in constructors, this is not testable./**
* Adds the menu option to the settings
*
* @wp-hook network_admin_menu
*/
public function add_menu_option() {
}_e( 'WPML 2 MLP' ) is not translatable.WPML2MLP_Importer::run_import(), move the POST handling to a separate method or class, make sure you do not import everything again after a page reload. Use admin-post.php as form action, and redirect the user back to the settings page when you are done. For the export, see this instruction.PclZip, can we use that instead?At the current version is no custom term support implemented. Custom terms have to included at the export files. Custom term support have to implement as a additional service via filter or something like else.
The following structures has to be read out of the XML-File:
wp:userwp:category, wp:tag(?), wp:nav_menu_item(?), wp:term(?)
item
The interface format of the entities…
Attributes:
int: origin_user_id
string: name
string: email
string: display_name
[string: first_name]
[string: last_name]
[object: roles]
[]… maybe empty values
roles has to be defined later
Attributes:
int: origin_term_id
string: taxonomy
string: name
string: slug
[string: description]
[int: origin_parent_term_id]
[array: locale_relations]
int: origin_post_id
string: locale
Attributes:
int: origin_post_id
string: post_title
string: post_guid
DateTime: post_date
string: comment_status
string: ping_status
string: post_status
string: post_type
bool: is_sticky
[string: origin_link]
[string: post_excerpt]
[string: post_content]
[string: post_name]
[int: origin_post_parent_id]
[int: menu_order]
[string: post_password]
[array: terms]
[array: meta]
[array: locale_relations]
Attributes:
string: meta_key
mixed: meta_value
Attributes:
int: origin_term_id
string: taxonomy
string: name
string: slug
Attributes:
int: origin_post_id
string: locale
Attributes:
int origin_post_id
string author_name
string author_email
string author_url
string author_ip
DateTime date
string content
int karma
string approved
string agent
string type
int origin_user_id
int origin_parent_comment_id
array meta
Replace {TYPE} with
usertermpostcommentUse always singular unless it is specified in a different way!
wp_insert_{TYPE}) failed/**
* Attach error handler/logger here
*
* @param WP_Error $error
* @param Type\Import{TYPE}Interface $import_{TYPE}
*/
do_action( 'w2m_import_{TYPE}_error', $error, $import_{TYPE} );
(Only for term, post and comment.)
/**
* @param WP_{TYPE} $wp_{TYPE}
* @param Type\Import{TYPE}Interface $import_{TYPE}
*/
do_action( 'w2m_import_missing_{TYPE}_ancestor', $wp_{TYPE}, $import_{TYPE} );
/**
* @param WP_{TYPE} $wp_{TYPE}
* @param Type\Import{TYPE}Interface $import_{TYPE}
*/
do_action( 'w2m_{TYPE}_imported', $wp_{TYPE}, $import_{TYPE} );
E.g. when linking of terms or insertion of meta data fails.
Please use the following scheme for the parameter signature of any actions:
WP_Error, Import_Element
Pass any contextual data with the WP_Error object like it's done in the parsers.
I tried to activate the plugin on a single site install:
In both cases I couldn't return to the plugin list, to deactivate the plugin. The wp_die() always blocked access. Needed to rename the plugins folder. -> Possible but annoying.
Auto deactivate the plugin on fail with an error on top of the list would be nice.
When uploading an WPML2MLP generated ZIP file, the following error occurs:
This is the output of the plugin Debug Bar. The WPML2MLP plugin does not give any error messages to the user.
This.
at the current version of export files the translation relations will saved as a single tag with attributes.
<wp:translation lang="de" post_id="2485"/>
<wp:translation lang="nl" post_id="769"/>
<wp:translation lang="es" post_id="2563"/>
<wp:translation lang="fr" post_id="2594"/>
<wp:translation lang="it" post_id="2546"/>
For consistency parsing we want use this format.
<wp:translation>
<wp:locale>nl_NL</wp:locale>
<wp:element_id>4711</wp:element_id>
</wp:translation>
I converted a lower german website with the plugin and the categories didn't make it into the new sites. There is just the uncategorized category.
Here the original category list, it's still complete in the base site:
Apply namespaces and PSR 4 autoloading using composer.
Base namespace: W2M\
I've used the theme demo data:
https://wpcom-themes.svn.automattic.com/demo/theme-unit-test-data.xml
And my local apache is not tweaked. So it reached the LimitRequestLine with 8190 Bytes:
http://httpd.apache.org/docs/2.0/mod/core.html#limitrequestline
We should switch to instant download instead of generating the whole data and encode it into the request uri.
When we create the new sites and we start to import data my local errorlog files up with requests for wp_3_icl_translations tables. We should advice the users not to enable WPML for the network.
Currently in //item/link there are some unescaped ampersands:
<link>http://wpml.to.mlp/?post_type=product&p=2938</link>
It should be either printed as CDATA or escaped.
Hello,
Missing file /inc/Wpml2mlp_Categorie_Creator.php in wordpress package at https://downloads.wordpress.org/plugin/wpml-to-multilingualpress.zip
Link from https://wordpress.org/plugins/wpml-to-multilingualpress/
Thanks
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.