Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter basilas

    (@basilas)

    Okay, I figure it out now. Ready Ecommerce will use WordPress user’s email as a default. If the wordpress email empty, Ready Commerce will use shipping or billing email as a lower priority. Anyway, the WordPress user’s email is required at registration. So, Ready Ecommerce will always use WordPress’s user email.
    The workaround is to comment out a few lines of code in user->getCurrentEmail().
    It would be great if Ready! developer customize the notification function to let an admin choose the default email account.

    Thank you

    Thread Starter basilas

    (@basilas)

    Thanks ukrainecmk. I have done those steps. Anyway, I found the root cause of the problem now. It’s because the function getRelatedProducts() and getNotRelatedProducts() has a fix DB query for “wp_” table. In my case, I change the db prefix to something else. That’s why I can’t add a related product. And anyone else who change DB prefix at the time installing WordPress would face the same problem.

    Although changing DB qeury from “wp_” to the correct one can solve the problem, hopefully the query string is fixed in the future version; to get the actual db prefix instead of “wp_”

    Regards,
    basilas

    Thread Starter basilas

    (@basilas)

    I did some further investigation and found that getRelatedProducts($id) and getNotRelatedProducts($id) in related_widget\mod.php did not return query results from DB. That make dialog “Related Product” in product admin page empty and I can’t add a related product.
    I also did some manual DB adding to toe_related_widget table and the Widget can display related products properly.
    So, seems like the db query strings in getRelatedProducts and getNotRelatedProducts are the problem. Anyone can confirm/advice?

Viewing 3 replies - 1 through 3 (of 3 total)