AMember中构建域名包的技巧是什么？
我想使用 AMember 让人们购买 WordPress 插件和主题。然而，我想为单个域出售不同的价格，而不是让它们像 5 域包（以及多个域包）一样安装。人们可以通过 AMember 工作流程来购买商品，然后根据购买情况收到一个序列号。他们激活主题或插件，然后将此序列号放入选项面板中，然后他们就可以关闭并运行功能正常的插件或主题。
调整 AMember 的编程以适应通过 AMember 销售的产品的每个域安装的最有效方法是什么？
例如，我在想也许我需要使用此“添加字段”功能，但然后对该字段使用自定义编程。
I want to use AMember to have people purchase WordPress plugins and themes. However, I want to sell different prices for single domain vs. letting them install like 5-domain packs (and multiples of those). One would go through the AMember workflow to purchase something, and then receive a serial number based on their purchase. They activate the theme or plugin and then put in this serial number in an options panel, and they're off and running with a functioning plugin or theme.
What is the most efficient way to tweak the programming of AMember to accommodate per-domain installations of stuff sold through AMember?
For instance, I was thinking perhaps I need to use this Add Field feature, but then use custom programming against that field.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
目前，aMember Pro v4 处理数量产品的功能被禁用。我现在正在努力重新设计并启用此功能。一旦完成，就很容易做到你所要求的，我将提供一个带有解释的代码片段。
如果您需要尽快，请直接通过服务台联系我（联系人：Alex Scott），我将帮助您解决您的任务。
currently, aMember Pro v4 ability to handle products with quantity is disabled. I am working right now to rework and enable this functionality. Once it is done, it will be easy to do what you are asking for, and I will provide a code snippet with explanation.
If you need it ASAP, contact me directly via helpdesk (attn. to Alex Scott) and I will help you to solve you task.
老实说，我已经很长一段时间没有使用会员了（如果我需要一个会员区，我会立即使用它，但我现在不需要会员区）所以我真的不太了解发生了什么代码，因为我已经很久没有看到它了。
我假设您会编写一个自定义解决方案来创建序列号，然后在付款时，您只需触发对自定义代码的调用即可创建序列并将其添加到数据库中，自定义归档将完美地保持该价值。如果我理解正确的话，aMember 基本上只是用来处理该用户的序列号，他们通过 aMember 购买序列号，aMember 会为您处理购买和过期等所有事宜，所以这听起来像是一个非常简单的交易
如果我误解了您的问题请告诉我，我会尽力为您改进我的答案
Honestly I haven't used amember in a long time ( I would use it in a heartbeat if I need a member area I just don't need one at the moment) so I really don't know a lot about whats going on in the code as I haven't seen it in so long.
I would assume you would code a custom solution to create the serial numbers and then when a payment is made, you would just have it fire off a call to your custom code to create the serial and add it into the DB, a custom filed would be perfect to hold that value. If I understand you correctly aMember would be basically used just to handle that serial number for that user, they buy the serial through aMember, aMember handles the buying and expiring and all that for you so it sounds like a pretty straight forward deal
If I misunderstood your question let me know and I will try to improve my answer for you