咨询：nopCommerce 3.9支付方式友好名称重建后恢复默认值的解决方法

Hey, let's break down why your custom friendly name keeps reverting to the default after rebuilding your nopCommerce 3.9 project, and how to stop it:

Why This Happens #

nopCommerce runs data seeding logic when you rebuild and start the project. This logic is meant to set up default data (like payment methods) if they don't exist—but in some cases, it’s configured to overwrite existing values, including your custom friendly name stored in the database.

Alternatively, some payment method labels are pulled from localization resource files instead of the database. If that’s the case, your backend edits won’t stick because the system prioritizes the resource file values over database changes.

Step-by-Step Solutions #

1. Modify the Payment Method Seed Data Code #

This is the most common fix for database-overwrite issues:

• Navigate to your project's Nop.Services/Payment folder, and find the class related to the Check/Money Order payment method (usually CheckMoneyOrderPaymentMethod.cs) or check the general data seeding files (like Nop.Data/Initialization/SeedData.cs).
• Locate the code that initializes the Check/Money Order payment method. It’ll look something like this:

  var checkMoneyOrder = _paymentMethodService.GetPaymentMethodBySystemName("Payment.CheckMoneyOrder");
  if (checkMoneyOrder == null)
  {
      // Create the payment method if it doesn't exist
      _paymentMethodService.InsertPaymentMethod(new PaymentMethod
      {
          SystemName = "Payment.CheckMoneyOrder",
          FriendlyName = "Check/Money Order",
          IsActive = true,
          // Other required properties...
      });
  }
  // Remove or comment out this update block if it exists!
  // else
  // {
  //     checkMoneyOrder.FriendlyName = "Check/Money Order";
  //     _paymentMethodService.UpdatePaymentMethod(checkMoneyOrder);
  // }
  

• Delete or comment out the else block that overwrites the FriendlyName for existing payment methods. This way, the seed logic only creates the method if it’s missing, and leaves your custom edits intact.

2. Update the Localization Resource File (If Labels Come From Resources) #

If your backend edits don’t change the database's PaymentMethod.FriendlyName value, the system is pulling the name from a resource file:

• Go to Nop.Web/App_GlobalResources in your project.
• Open Payment.resx (or language-specific files like Payment.en-US.resx for English).
• Find the resource key for the Check/Money Order friendly name—it’ll be something like Payment.CheckMoneyOrder.FriendlyName.
• Edit the value to your desired friendly name (e.g., "Check / Money Order") and save the file.
• Rebuild the project; the custom name will now load directly from the resource file and won’t reset.

3. Disable Specific Data Initialization (Advanced) #

If the above fixes don’t work, you can disable the payment method seed logic entirely:

• Open Global.asax.cs in the Nop.Web project, or look for the initialization pipeline code.
• Find the section that runs payment module seed data (usually called via _paymentMethodService.InstallPaymentMethod() or similar).
• Comment out the line that triggers the Check/Money Order seed logic.
• Note: Only do this if you’re sure you won’t need the default payment method setup again, as it could break other payment-related initialization.

4. Database-Level Lock (Emergency Fix, Not Recommended) #

As a last resort, you can directly edit the database and prevent overwrites:

• Open your nopCommerce database, find the PaymentMethod table.
• Locate the row where SystemName = 'Payment.CheckMoneyOrder', and update the FriendlyName column to your desired value.
• To prevent future overwrites, you could add a database trigger that blocks updates to this specific row's FriendlyName field—but this is risky, as it might interfere with normal system operations.

How to Confirm Which Issue You Have #

To tell if it’s a seed data overwrite or resource file issue:

1. Edit the friendly name via the backend.
2. Check the PaymentMethod table in your database.
   • If the FriendlyName column matches your edit but resets after rebuild: It’s seed data overwriting. Use solution 1 or 3.
   • If the FriendlyName column never changes from the default: The system is using resource files. Use solution 2.

内容的提问来源于stack exchange，提问作者Milad Shafik