AI助手支持GPT4.0
Allparcels.com shipping module is a versatile solution for any e-shop owner or administrator looking for a flexible, yet effective delivery system.
Allparcels.com的运输模块是寻求灵活而有效的交付系统的任何电子商店所有者或管理员的通用解决方案。
With allparcels.com module you will be able to:
使用allparcels.com模块，您将能够：
The module contains a huge number of different courier integrations, including all couriers in the Baltic States and other countries, therefore allowing for you to select the ones you require without installing numerous plugins, wasting money or time.
该模块包含大量不同的快递集成，包括波罗的海国家和其他国家/地区的所有快递，因此，您无需安装大量插件即可选择所需的快递，而不会浪费金钱或时间。
Install once and use anything you want in one place;
安装一次并在一个地方使用所需的任何东西；
Allparcels.com module will provide you with complete flexibility and control regarding your deliveries.
Allparcelss.com模块将为您提供完全的灵活性和对交货的控制。
Get all couriers and delivery methods with one plugin here and now.
现在就使用一个插件获取所有快递和送货方式。
Try any combinations that you wish and select what works best for you!
尝试任何您想要的组合，然后选择最适合您的组合！
Moreover, you will be able to use additional allparcels.com services like storage, packaging etc.
此外，您将能够使用其他allparcels.com服务，例如存储，包装等。
A few notes about the sections above:
关于以上部分的几点说明：
Note that it might work on
请注意，它可能适用于
higher versions… this is just the highest one you’ve verified.
更高的版本...这只是您已验证的最高版本。
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for
/trunk/
如果您对使用 / trunk / ，Stable标记应指示最新稳定版本的Subversion“标记”或“ trunk”stable.稳定。Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so请注意，稳定标签的 readme.txt 是被认为是插件定义之一的标签，因此if the /trunkeadme.txt file says that the stable tag is 4.3, then it is /tags/4.3eadme.txt that如果 /trunkeadme.txt 文件说稳定标签是 4.3 ，则 /tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
/ trunk / ，Stable标记应指示最新稳定版本的Subversion“标记”或“ trunk”stable.稳定。Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so请注意，稳定标签的 readme.txt 是被认为是插件定义之一的标签，因此if the /trunkeadme.txt file says that the stable tag is 4.3, then it is /tags/4.3eadme.txt that如果 /trunkeadme.txt 文件说稳定标签是 4.3 ，则 /tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
stable.
稳定。
Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so
readme.txt
请注意，稳定标签的 readme.txt 是被认为是插件定义之一的标签，因此if the /trunkeadme.txt file says that the stable tag is 4.3, then it is /tags/4.3eadme.txt that如果 /trunkeadme.txt 文件说稳定标签是 4.3 ，则 /tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
readme.txt 是被认为是插件定义之一的标签，因此if the /trunkeadme.txt file says that the stable tag is 4.3, then it is /tags/4.3eadme.txt that如果 /trunkeadme.txt 文件说稳定标签是 4.3 ，则 /tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
if the /trunkeadme.txt file says that the stable tag is 4.3, then it is /tags/4.3eadme.txt that
/trunkeadme.txt
4.3
/tags/4.3eadme.txt
如果 /trunkeadme.txt 文件说稳定标签是 4.3 ，则 /tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
/trunkeadme.txt 文件说稳定标签是 4.3 ，则 /tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
4.3 ，则 /tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
/tags/4.3eadme.txt 'll be used将被使用for displaying information about the plugin.用于显示有关插件的信息。In this situation, the only thing considered from the trunk readme.txt在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
'll be used
将被使用
for displaying information about the plugin.
用于显示有关插件的信息。
In this situation, the only thing considered from the trunk readme.txt
在这种情况下，唯一考虑的是主干 readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
readme.txt is the stable tag pointer.是稳定的标记指针。Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
is the stable tag pointer.
是稳定的标记指针。
Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in
因此，如果您在主干中进行开发，则可以更新主干 readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
readme.txt 以反映中的更改your in-development version, without having that information incorrectly disclosed about the current stable version您的开发中版本，而不会错误地披露有关当前稳定版本的信息that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
your in-development version, without having that information incorrectly disclosed about the current stable version
您的开发中版本，而不会错误地披露有关当前稳定版本的信息
that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.
缺少这些更改-只要中继线的 readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
readme.txt 指向正确的稳定标签即可。If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk” you put the stable version, in order to eliminate any doubt.您放置了稳定版本，以便消除任何疑问。
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where
如果未提供稳定标签，则认为中继线是稳定的，但如果在此处，则应指定“ trunk”
you put the stable version, in order to eliminate any doubt.
您放置了稳定版本，以便消除任何疑问。
Module Configuration
模块配置
You can enter your API code by going to WooComerce -> Allparcels settings.
您可以通过转到WooComerce-> Allparcels设置来输入API代码。
To configure delivery methods you need to go to: WooCommerce -> Settings, and select �Shipping�.
要配置交付方式，您需要转到：WooCommerce->设置，然后选择``发货''。
Choose one of the delivery methods, that you added to a selected shipping zone earlier:
选择您之前添加到选定送货区域的一种送货方式：
Enter the title (it will be visible on the checkout page);
输入标题（它将在结帐页面上显示）；
Define delivery price;
定义交货价格；
Choose a carrier;
选择一个运营商；
Choose additional services (take note that you may be charged extra for using these options);
选择其他服务（请注意，使用这些选项可能会向您收取额外费用）；
After all the selections are made, do not forget to click �Save�.
完成所有选择后，请不要忘记单击``保存''。
Ordered list:
订购清单：
Markdown uses email style notation for blockquotes and I’ve been told:
Markdown对块引用使用电子邮件样式表示法，并且被告知：
Asterisks for emphasis.强调的星号。Double it up for strong.将其加倍以得到 strong 。 <？php code（）; // goes in backticks ?>//放在反引号中？>
Asterisks for emphasis.强调的星号。Double it up for strong.将其加倍以得到 strong 。
Asterisks for emphasis.
强调的星号。
Double it up for strong.
将其加倍以得到 strong 。
<？php code（）; // goes in backticks ?>//放在反引号中？>
// goes in backticks ?>
//放在反引号中？>
This section describes how to install the plugin and get it working.
本节介绍如何安装插件并使其正常工作。
e.g.
例如
Before installing allparcels.com module into your e-store, you must:
在将allparcels.com模块安装到电子商店之前，您必须：
1. have Login information of your e-store administrator account;
1.拥有您的电子商店管理员帐户的登录信息；
2. delete the modules of previously used carriers, e.g.: DPD or LP Express;
2.删除以前使用的运营商的模块，例如：DPD或LP Express;
3. obtain allparcels.com API key.
3.获取allparcels.com API密钥。
It will be supplied by allparcels.com representative.
它将由allparcels.com代表提供。
How to install allparcels.com module:
如何安装allparcels.com模块：
原文出处:http://www.sanshu.cn/a/2107.html
群主管理都是支付大佬
