• Resolved damienlee

    (@damienlee)


    Hi!

    I was planning to purchase the pro version of this plugin once I finished integrating it fully. I initially set it up some time ago and have returned to finish off the layout of the glossary page only to discover that the plugin has been altered such that content is no longer passed (as it’s generated with Oxygen Builder) and you have changed the passing method to be more restrictive.

    I gather I could use the pro feature of the shortcode wrapper which is a messy solution and can’t be tested without purchase. I did hope to write to you directly about the problem but there is no option from your site to do so prior to purchasing. This does not promote confidence.

    All this has made me disinclined to purchase your plugin and to search for a better alternative that works out of the box.

    An approach you might consider is to have an option in the settings to force the parsing of all page content with a warning that it could cause incompatibility problems with other plugins or content, rather than using your more recent restrictive passing method.

    I would also suggest that you don’t make features critical to your plugins operation a “pro only” feature as this makes it impossible to test the software. You would be better off restricting value-added features not critical to basic functionality. It makes poor marketing sense to do otherwise.

    I am still open to revisiting this software for a short period if a solution is found to allow me to test functionality prior to purchase. Buy first and ask for a refund within 30days is not an option Ill risk at this point.

    Cheers

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi Damienlee,
    thanks for your feedback, let me answers to all the various points.

    1) What version you was using before? Just to do some comparisons and the 1.8 branch first released now was in June 2019. We are working now on a new major that will have more features.
    2) About parse all the page and be more restrictive it is very delicate question. If we parse all the page we cannot exclude areas like sidebars or stuff injected by other plugins or the theme (that happens often), so it is something that we cannot do. If we need to be restrictive because the big issue of the plugin are conflicts with other and this is the only way to make they compatible out the box without implement a specific support for a plugin.
    2bis)Our parsed ignore nested html tags because usually they are used by other plugins, and they create conflicts like with visual composer that are famous to injects a lot of nested tags (not healthy for a webpage anyway). Also cannot identify what not to parse from html and at the same time if we scan all the page this can be very heavy for performances. We have customers with like 10000 terms or with 30 but with cheap hosting, we need to be able to provide the best feature for all of them without the issues of the configuration.
    3) The ignore/parse shortcode was a solution for those cases, often with visual composers that are not WordPress standard, that change with every version and based on themes combination works differently together with the settings. Basically an impossible job to have them working with all of them. As today the one with 0 issues was Elementor that is following WordPress standard on injecting the content compare to the others.
    4) We have an email [email protected] but as we are working on the new major we are changing the plugin website, documentation and soon also the internal ticket system. Also, from the plugin itself should be the contact form to reach us.
    5) What for you are features critical on the pro version? If you are talking about that shortcodes we chose to do in that way because often who need to use it also need the premium support we offer.

    Closing after a month.

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

The topic ‘New problems passing content’ is closed to new replies.