Jump to content

Brooke Linden

Retired Linden
  • Posts

    213
  • Joined

Posts posted by Brooke Linden

  1. Unfortunately, we need to delay the Marketplace release until next week. The target release date is October 11, 2011. Here is a complete list of the changes that will be released:

    • WEB-4138 (Order confirmation email failures)
    • WEB-2920 (Add item number to distributions): The listing ID will appear on distribution transactions. As part of this fix, we will also include the Merchant name on distributions you receive, and will update the transaction type for revenue from sales.
    • WEB-4143 (L$ balance not updating automatically inworld)
    • WEB-4152 (Listing count and pagination in merchant admin inventory)
    • WEB-4150 (Unavailable and unlisted are incorrect in inventory view)

    We apologize for the delay. Thank you for your patience and let us know if you have additional questions about what we are planning to fix in next week's release.

    Brooke


    

  2. I'm working on prepping an update on Direct Delivery. The server changes that are rolling out are changes to existing APIs and functionality to support Direct Delivery--that should be clarified in the release notes. I will make sure that happens going forward.

    Thanks for pointing this out, Arwen!

    Brooke

  3. Here’s a quick update on where we are with some of the issues that we have been seeing since the Marketplace release a couple of weeks ago.

    • WEB-4138 (Order confirmation email failures): we are still investigating the issue and hope to get a fix deployed next week.
    • WEB-2920 (Add item number to distributions): This has been fixed in our development environment (with the listing id) and is being tested for a release to production next week. The order number portion of this issue was already deployed to production last week. As part of the deploy next week, we will be including the Merchant name on distributions you receive.
    • WEB-4143 (L$ balance not updating automatically inworld): This has been fixed in our development environment and is currently being tested for a release to production next week.
    • WEB-4152 (Listing count and pagination in merchant admin inventory): this has been fixed in our development environment and is currently being tested for a release to production next week.
    • WEB-4150 (Unavailable and unlisted are incorrect in inventory view): This is the same underlying issue as WEB-4152 and will be addressed with that fix.

    We will post an update here once we get these fixes deployed (we are currently targeting Oct. 5, but this is not a confirmed deploy date) or if there will be a delay in getting these fixes out.

    Brooke

    UPDATE: Unfortunately, we will need to delay this release until next week. All of the above JIRAs are a part of this release. The target for next week's deployment is Tuesday, October 11, 2011.

  4. I haven't had a chance to look in detail at your case in particular, but do note that we currently have a bug open related to this issue: WEB-4152. The count of items in your inventory is currently inflated and pagination will not be correct (i.e. you will see fewer items per page than you are supposed to when you look in merchant admin at your inventory).

    We are working on this and other issues and expect this issue to be resolved next week, but you should look at the JIRA for up to date details on when this fix will go out.

    Thanks for letting us know about this issue--and please do let us know if it is a problem separate from WEB-4152.

    Brooke

  5. Mac, thanks for reporting this issue. Here's a bit more context and the way to recoup missing funds.

    This is a very rare issue with Magic Box delivery and pre-dates XStreet becoming part of the Second Life Marketplace.  Addressing this issue is a part of our overall effort to make Marketplace deliveries more reliable with Direct Delivery.

    In the past, we have asked you to file a CSR ticket to request a refund from Linden Lab to recover your lost revenue. Please continue to do this. If you see an increase in the number of these cases, please add the order number and item name to WEB-4162.  If you’d like more details on this issue, please see WEB-4162.

    Thanks!
    Brooke

  6. Hi all,

    This morning we deployed the first part of a fix to the problem of duplicate listings appearing in merchant inventory (WEB-4125).  We have a remaining issue with the number of items displayed per page (WEB-4152), which will also show an incorrect total number of listings. We are currently working to complete these fixes.

    Thank you for your continued patience with these issues. If you see new or ongoing problems, please file a JIRA or contact Customer Service.

    Brooke

  7. Hi all,

    Since the deploy yesterday, we have been monitoring Marketplace and JIRA for any issues that have arisen. We were able to get an emergency fix deployed this evening to address WEB-4134. We continue to monitor performance and error rates, as well as JIRA throughout the weekend. 

    Please continue to use JIRA for reporting bugs and customer service for issues that need immediate attention.

    Brooke

  8. Hi all,

    With today’s release, we were able to deploy the following fixes:

    • WEB-4123: "Order number no longer included in secondlife.com account history.”  The order number now appears in the transaction history on secondlife.com. Amounts are not split up by line items in this report, so the product ID is not included. See the new report (detailed below) for this data.
    • WEB-4119: "ANS system bug after Marketplace Maintenance.”  ANS (find more details on ANS here) now has values when notifications are sent.
    • WEB-4122: "Permissions reset when editing listing.”  Permissions and listing name are no longer reset when the listing is edited.

    In addition to these bug fixes, there is a new downloadable report for you to use; the XStreet report is still available, but it shows only historical data from before the deploy on September 13, 2011. The new report keeps the same format, with some additional data pulled out into separate columns. Those columns appear at the end, so you can remove them if you prefer the XStreet format.

    • Recipient/Purchaser: This column shows the name of the recipient of the funds in the case of a distribution payout or commission. In the case of a sale, it shows the name of the purchaser.
    • Order #: this is pulled out separately.
    • Product: product name pulled out separately.
    • Product ID: this is the listing ID (the unique number in the listing URL).
    • Status: the status of the order. Note that no fully failed orders will appear on this report now. To track refunds on failed orders, please use the transaction report on secondlife.com.

    To download this report, go to My Marketplace->Merchant home and select Reports->Orders. Select the time period for the data you would like to download then click the “Go” button. In order to download the detailed report with distributions and commissions, click on the “Download Txn CSV” link. This report does include historical data. Currently, there is no way to filter out L$0 transactions or to view this report without downloading.

    The remaining issues from Tuesday’s release are:

    • WEB-4121: "L$0 are appearing in transaction history."  If there are any areas this is resulting in problems besides the secondlife.com transaction report or the Marketplace reports, please add comments to the JIRA.
    • WEB-4125: "The same listing shows up twice in my inventory.”  Though there is no data duplication, this is a painful issue, so we are planning to address it in the next release (early next week).



    Thank you all for your patience with these issues. If you see new or continued problems, please file a JIRA or contact Customer Service.

    Thanks!
    Brooke 

  9. Hi all,

    First of all, we apologize for the extended downtime this morning and the lingering slowness on the Marketplace web site. The issues were related to hardware downtime and database issues hit during the deploy. We will update this forum once we have addressed the slowness on the Marketplace.

    Now for the details on the deploy.

    With today’s deploy, all payments will now move into and out of the Commerce Linden account, and Marketplace Linden will no longer be used. (Currently only listing enhancements are paid to Commerce Linden.) Going forward, you will see money getting paid to Commerce Linden, as opposed to Marketplace Linden, when you make a purchase, and money moving into your account from Commerce Linden when you receive payments or distributions from Marketplace sales.

    Here is an overview of the changes in this release:

    • All payments now go through Commerce Linden.
    • New transactions will no longer appear on XStreet L$ transaction reports, though historical transactions will continue to be available. The next deploy will include a downloadable CSV with the same data for all new transactions. This report will be available with the next Marketplace deploy later this week or early next week.
    • Fixes have been made for WEB-3446. Please see the JIRA for details on the corrected rounding logic.

    This change in the way payments are processed is necessary groundwork for moving forward with Direct Delivery. With this release, the way objects are listed on the Marketplace and delivered to customers has NOT changed. Please continue to list and purchase items as you always have.

    For those who would like to read more about Direct Delivery, please see the Direct Delivery FAQ.

    Please contact Customer Service or file a JIRA if you see additional issues with this latest release. Note that an index is in the process of being updated, so you may see duplicate listings in your merchant admin. These are not duplicates, and will be cleaned up as the index completes.

    Thank you!
    Brooke

    UPDATED

    We are currently testing the following items and will deploy fixes tomorrow (Sept. 15) if these pass testing (there will be no downtime):

    In addition, we have an outstanding internal JIRA for the new report with transaction details, which has been completed, but is still being tested. This report is part of the planned release for Sept. 15.

    The following issues are still under investigation. If we have fixes ready, we will deploy them early next week:

    

×
×
  • Create New...