Magento 2 Custom Module (Admin) Spinner never disappear

Magento 2 Custom Module (Admin) Spinner never disappear

July 24, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento 2 Custom Module (Admin) Spinner never disappear

Based on the provided XML configuration files for your custom Payment Confirmation module, it appears that you have properly set up the UI component listing to display relevant data from your custom database table. The listing includes columns for ID, account number, account holder, transfer date, created date, status, and actions.

Each column is configured with appropriate data types such as text, select, or date, along with validation rules like required-entry. The “actionsColumn” at the end of the listing configuration suggests that you have defined custom actions to perform on each row of the Payment Confirmation grid.

Now, let’s take a closer look at the dependencies and configurations in your di.xml file:

  1. Preference for PaymentConfirmationInterface: You have mapped the PaymentConfirmationInterface to your PaymentConfirmation model using the preference tag. This ensures that when you use the interface in your code, it will be resolved and instantiated with your custom implementation.

  2. VirtualType definitions:

    • PaymentConfirmationFilterPool: Defines a filter pool that includes regular and fulltext filters for the Payment Confirmation data provider.
    • PaymentConfirmationDataProvider: Configures the data provider for the Payment Confirmation listing. It specifies the collection and filter pool to be used.
    • RepublikFiksi\ConfirmPayment\Model\ResourceModel\PaymentConfirmation\Collection: Defines a virtual type that represents the Payment Confirmation collection. It specifies the main table name as “payment_confirmation” and maps it to your custom resource model.
  3. Type mapping for CollectionFactory:

    • Magento\Framework\View\Element\UiComponent\DataProvider\CollectionFactory: Maps your custom collection factory to handle the data provider collections, specifically for the Payment Confirmation listing data source.

Based on this analysis, it seems that you have correctly configured the necessary dependencies and virtual types required for the Payment Confirmation module’s UI component listing. You have set up the database table mapping, column configurations, filters, and actions needed for a functional listing grid in Magento 2.

To ensure everything works as expected:

  1. Make sure you have properly registered your custom Payment Confirmation module in the config.xml or app/etc/modules/RepublikFiksi_ConfirmPayment.xml file.
  2. Check if there are any typos or syntax errors in the XML files provided.
  3. Verify that your database table “payment_confirmation” is created and populated with data.
  4. Navigate to the Payment Confirmation grid in the Magento admin panel to test the listing.

If you encounter any issues, double-check the configuration files for accuracy and ensure that the necessary permissions are granted for accessing the database and performing actions on the Payment Confirmation records.

Remember, proper error handling and validation should be implemented in your custom code to handle any potential issues or exceptions that may arise during the processing of payment confirmations.

Magento 2 Database Extensions Admin

Our network