• It is not a flexible plugin. Even though I bought the pro version of it but I felt handicap once it comes to the simple customization.

    We have to compulsory adjust our requirements as per their built in features.

    And it creates a bug once it comes to the user login module of Amelia user roles & WordPress user.

    It can be possible the user registered as Amelia Customer/Provider then he/she may be a WordPress user also and if the user exist on both then definitely you will face lots trouble to match your custom login(Based on WordPress login mechanism) & Amelia’s login sessions.

    Doesn’t have enough informative documentation for the developers.

    Literally frustrated with this plugin.

    Clients are having a requirements like Refund, Split payment, Custom design of booking popups. Multiple payment method support with single payment gateway.

    Even if you are using PayPal payment gateway for woo store set up & Amelia event booking, then it will leads you to the conflicts between PayPal SDKs.

    • This topic was modified 2 years, 4 months ago by krutim.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author ameliabooking

    (@ameliabooking)

    Hello there.

    We’re sorry to see you’ve been facing some issues with the plugin.

    Which bug are you referring to when it comes to WP user & Amelia user? If there’s a WP user, which is linked to Amelia Employee, or an Amelia Customer, the same login for WordPress will work for Amelia’s Employee or Customer panel. Only if your employees/customers change the password through the Employee/Customer panel will the login credentials be different, since Amelia can’t modify the password of a WordPress user, otherwise it works without issues.

    The developers’ documentation is being prepared and it should be released within a month or so unless there are some unforeseen circumstances that delay that.

    Amelia can’t work outside its logic and built-in features, so we’re not exactly sure what you mean by not being able to configure it. We’re aware that there are thousands of use cases out there, and as a WordPress plugin, it will most likely never be able to suit everyone but please let us know what you want to do with it, and we’ll see if there’s anything we can do about it.

    Refunds are only possible for online payment gateways, but in order to issue them, you need to do it through the payment gateways – there’s no way Amelia can trigger a refund for a charge since it only forwards the details for payments to the payment engines. We’ll work on this as well in the future, but we don’t have an ETA on that.

    If you’re using WooCommerce in Amelia, you can’t enable any other method of payment within the plugin, so if you wish to use PayPal, you need to configure it through WooCommerce. Amelia only sends the customer’s details and info about the appointment. Everything else you see from WooCommerce Cart or Checkout onward is coming from WooCommerce.

    Hopefully, this clears some stuff, but if you have other questions or issues, please feel free to let us know.

    Kind regards.

    Thread Starter krutim

    (@krutim)

    Thank you Team @ameliabooking .

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Requires more flexibility’ is closed to new replies.