Order Now:-http://www.worldcarestore.com/auras-wave-keto/







Order Now:-http://www.worldcarestore.com/auras-wave-keto/

How do i add new order statuses in the dropdown other then “Pending”

I tried going through these steps here but it didn’t seem to work. I want Check / Money order to have a default status as processing instead of pending.

Enterprise/Commerce 2.2.6


Go to System -> Order Statuses

Click – Create New Status

Status code enter ‘pendingcheque’

Status Label enter ‘Pending Cheque Payment’ (Or whatever you want it to say)

Save the Status


Go to System -> Order Statuses

Click – Assign status to the state

Select your new created status from the drop down

Select ‘New’ from the Order State drop down


Go to System -> Configuration

Click Payment Methods on left

Select Check/Money Order

Your new Order Status should now be available in the New Order status Drop Down.enter image description here

The above steps were from this post: "Pending Payment" status for Check/Money Order payment method

When i change it “new” in the DB it creates processing in the dropdown like so:

enter image description here

Unfortunately, i believe that’s going to make every order go straight to processing which is not the desired outcome. Also there is only one status now which is processing. There has to be a way to append more than one status and be able to select which one you want. Otherwise why would they of created these as dropdowns.

enter image description here

Postgesql non-deterministic order of result with LIMIT and ORDER BY

I understand that Postgresql may return results in non-deterministic order when the query parameters are non-unique. This is especially a problem when we use LIMIT since this may return entirely different results. So the suggestion for safety is to use ORDER BY with LIMIT.

However, what if we use ORDER BY on an non-unique column name? Will this produce a deterministic result or no? Let me demonstrate with an example:

We have the following data:

id | name | index 1    foo     5 1    bar     2 1    test    5 

If I query SELECT * FROM <table> WHERE id = 1 ORDER BY index LIMIT 1;. Will this produce the same result every time?

Magento2.3: Order not Place and Redirect to checkout/cart page

I have upload my Magento2.3 site on site ground. Others things are working fine but order not place redirect to checkout cart page.


 [2019-04-19 12:15:47] main.INFO: Broken reference: the 'div.sidebar.main' tries to reorder itself towards 'main', but their parents are different: 'div.sidebar' and 'div.col-main' respectively. [] []     [2019-04-19 12:15:47] main.INFO: Broken reference: the 'currency' tries to reorder itself towards 'store_language', but their parents are different: 'header.panel' and 'theme_header' respectively. [] [] 

live site link


But same project working fine on staging site.


It hosted on digital ocean .Working fine every thing .kindly describe the issue

magento 2 : Place order using REST API and stripe payment method

We are working on mobile which use magento 2 REST API. In which we are facing issue while try to place order using Stripe payment method. For stripe we are using magenest stripe extension.

REST API call for guest user is : https://example.com/index.php/rest/V1/guest-carts/aHdNbZDggtknHuhZWwEfQvvHQz8JVZnb/order

Parameter is :

{   "paymentMethod": {        "additional_data":{            "number": "4111111111111111",            "exp_month": "10",            "exp_year": "30",            "cvv": "123",          }     "method": "magenest_stripe"   } } 


{     "massage" : "No such token: false" } 

So please help us to fix this issue.

Disable Next button to prevent order placement based on shipping address information in Magento 2

We need to disable Next button on the shipping page to prevent fraud orders to certain addresses like carry forwarders and out of country. Are there any open source or paid extensions to disable order placement or disable Next button based on restricted addresses data lookup from a custom table?

What is the right place if this has to be done in a custom module and approach, without any product attributes and customer group data, since customer(s) can create new account each time they order?