• I liked the free version so I bought the PRO version. The problems I faced are:

    1. The class attributes or other HTML attributes may break the checkout page frontend.
    2. The fields cannot be conditionally required.
    3. It displayed an “Array” on the order summary page instead of each field separately. Same for the order email.

    The support answered me on a ticket I opened but there is no solution at the moment to the above. If any updates are made I will review this again.

    • This topic was modified 3 years, 11 months ago by gtsigkourakos.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Sanesh Acowebs

    (@saneshacodez)

    Thanks for your comments and we’re glad to know that you liked the free version of our plugin. We have a lot of users with different themes using our free and pro version of our plugin.

    Regarding your comment -The class attributes or other HTML attributes may break the checkout page frontend- We use the same classes that are used by Woocommerce and added some additional classes with our own prefix (these classes are not associated with any styling). If the free version of our plugin works, then the pro version will also have no frontend issues. There may be chances like, your theme not supporting Woocommerce class styles like form-row-wide, form-row-first and form-row-last. Also there are some plugins that add their own checkout fields with priority values. In this case also you can drag and adjust fields from backend settings.

    Regarding the comment -The fields cannot be conditionally required- We already mentioned that we don’t have an option to make a field conditionally required, we only have the option to show/hide fields conditionally. And we don’t think any other checkout field editor plugins have this conditionally required option.

    Regarding the comment -It displayed an “Array” on the order summary page instead of each field separately. Same for the order email- We are saving extra fields options as a single meta data. But It will display as a separate field and its value under the corresponding sections on order summary and order emails. This may not make any issues. If you want to retrieve a single field value then it can be retrieved using the order number. Also we are hiding this extra field values from the custom fields section on the backend order detail page.

    We still believe that our plugin will work fine on your website. If there is any issue, we are happy to assist you. We provide a 30 day money back guarantee if you are not satisfied with our products. You can contact our support team for any issues and clarifications. Can you please share the ticket number if you have contacted our support team previously.

    Thread Starter gtsigkourakos

    (@gtsigkourakos)

    Good morning,
    regarding your answer:
    1. The same exact classes work for the free version but do not work for the PRO version. It should also be able to handle if I don’t use a form-row-wide, etc. and instead I use a vc_col_6 for example or any other bootstrap-logic library. And the col_6 worked perfectly on the free version but broke on the PRO version.

    2. Hiding and showing only via JavaScript is very simple to implement, but a conditional validation (at least on frontend) would be expected from a PRO plugin. I did everything by hand including a server-side validation without the usage of the plugin.

    3. I know how the order extra fields are saved in an Array type variable but on both the Order page and the Email the Array was not displayed correctly. So I assume the loop did not loop through the elements correctly.

    I tried to work with the plugin for 2 days in a clean environment but nothing went well for my case. The theme I am currently using is the7 which is a top selling theme and did not have problems with another Checkout Field Editor plugin.
    I tried to work with it but finally I decided to not use it at all. The ticked number is #4519. I answered yesterday to not go through with the refund yet via email but I finally decided to go through with it.

    Thank you for your quick response.

    Thread Starter gtsigkourakos

    (@gtsigkourakos)

    Update: The support team was really helpful and they refunded immediately.
    If the above are fixed in the future I would buy it for sure.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Mediocre plugin’ is closed to new replies.