Troubleshooting & FAQs
Know how to troubleshoot some of the common error messages and find answers to frequently asked questions for Magento extensions.
Available in
India
Malaysia
Singapore
Know how to troubleshoot some of the common error messages for Magento 1.x and 2.x extensions.
Below are some common error messages and the possible reasons and fixes:
| Error | Cause | Fix |
|---|---|---|
| Bad request error | The API keys ([KEY_ID] and [KEY_SECRET]) are not configured correctly. | Make sure that the API Keys are active and entered correctly on the Magento Settings page. |
| Bad request error | You might be using a custom checkout theme like IWD and Firecheckout. | Make sure that you are using the GitHub/master branch. |
| cURL error | You do not have PHP-cURL installed on your server. | Ensure that you have PHP-cURL installed on your server. |
| cURL error | Port 443 is blocked. | Contact your hosting service to unblock the port. |
Below are some common error messages and the possible reasons and fixes:
| Error | Cause | Fix |
|---|---|---|
| Bad request error | The API Keys ([KEY_ID] and [KEY_SECRET]) are not configured correctly. | Make sure that the API Keys are active and entered correctly on the Magento Settings page. |
| Bad request error | You may be using a custom checkout theme like IWD and Firecheckout. | Make sure that you are using the GitHub/master branch. |
| cURL error | You do not have PHP-cURL installed on your server. | Ensure that you have PHP-cURL installed on your server. |
| cURL error | Port 443 is blocked. | Contact your hosting service to unblock the port. |
| Undefined index: Razorpay in /app/code/Razorpay/Magento/ Observer/AfterConfigSaveObserver.php | This issue is due to an error in module compilation. | Run run bin/magento setup:di:compile to recompile. |
| The following modules are outdated: • Razorpay_Magento schema: Current Version - None, Required Version - 3.6.2 • Razorpay_Magento data: Current Version - None, Required Version - 3.6.2 | The Curlec Magento plugin version is outdated. | and install the latest Curlec Magento Plugin. |
| Column not found: 1054 Unknown column "'main_table.rzp_webhook_notified_at' in 'field list', query was: SELECT main_table.entity_id, main_table.rzp_webhook_notified_at FROM sales_order AS main_table." | The Razorpay Magento plugin version is outdated. | Make sure that you update the plugin to the latest version. |
Follow the troubleshooting steps given below:
- Ensure that your system meets all the requirements mentioned .
- We recommend you to keep your Magento and Curlec plugins up to date. You can find the latest versions .
- If the issue persists after following these steps, contact our . Provide the following information while creating a ticket:
- Magento version (1.x/2.x)
- Curlec Magento plugin version
- PHP version
- Steps to reproduce the issue (Screen recording/Screenshots)
- Error logs, if any
- Magento staging website credentials (login URL, login id, and password)
- SSH/FTP access to the staging server
Yes, Magento Plugin supports Progressive Web Apps (PWA) through GraphQL.
3. If you initiate a refund on the Curlec Dashboard, will the same status reflect on the Magento Dashboard?
Initiating a refund on the Curlec Dashboard does not automatically update the status on Magento. The refund process is typically managed through the Magento Dashboard. The status changes made on the Magento Dashboard are then reflected on the Curlec Dashboard.
Below are the steps to create a Custom Order Status in Curlec Magento:
Step 1: Create a customer order status.
-
Go to Stores → Order Status (under Settings) on the Magento Admin Dashboard.
-
On Order Status page, click Create New Status.
-
On the Create New Order Status page:
- Insert a Status Code under the Order Status Information section for internal reference.
Handy Tips
This field must contain letters (a-z), numbers (0-9), and the underscore. You must use letters at the first character. The rest can be a combination of letters and numbers.
- Set the Status Label for Admin and storefront.
- Set the Default Store View under Store View Specific Labels for each store view.
-
Click Save Status to complete.
Step 2: Un-assign existing status.
-
Un-assign the existing status code that is in use.
- If State Code and Title is
processing[Processing], theprocessingstatus is already in use for stateprocessing. - Un-assign this status from the existing state code
processing, so the state will be available for your custom status code.
Watch Out!
If you get the following error "The status can't be unassigned because the status is currently used by an order.", directly move to step 3.
- If State Code and Title is
Step 3: Assign an order status to a state.
- Go to the Order Status page, and click Assign Status to State.
- On the Assign Order Status to State page:
- Select the Order Status to assign from the existing order status list.
- Select the Order State as
processingto include the order status you have just assigned. - Select the Use Order Status As Default checkbox to accept the Order Status as a default.
- Select the Visible On Storefront checkbox to enable the order status on the storefront.
- Click Save Status Assignment to complete.
Step 4: Using custom order status for Curlec Magento.
- On the Magento Admin Dashboard, open Curlec payment method settings.
- On the Configuration page:
- At Enable Custom Paid Order Status field, select Yes to enable custom order status, and select No to disable custom order status.
- Insert Custom Paid Order Status value in the input field, providing the same value as the Status Code while creating custom status.
- Click Save Config and refresh the cache.
5. I am getting the following error message "Column not found: 1054 Unknown column 'main_table.rzp_webhook_notified_at' in 'field list', query was: SELECT main_table.entity_id, main_table.rzp_webhook_notified_at FROM sales_order AS main_table."
If you encounter this error message,
the plugin to the latest version to resolve the issue.Was this page helpful?