• Good mobile nav and some improvement needed. I wish the logo and site name elements can be set to none display. My theme already has a header. Just need to only add the mobile menu component and not the entire new header. Documentation can be a bit more informative beyond just restate what the label already says.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor rajivfarwaha

    (@rajivfarwaha)

    Surprised that you posted a bad review instead of contacting free support we provide. You should have contacted our support to get what you want. Site logo and element can be set to hidden easily through settings in the plugin.

    Anyways good luck to you if you found any better free Plugin.

    Thread Starter skylabb

    (@skylabb)

    Thanks for the response. You’d contact support when you find a bug or something not working as expected. In this case, it’s a lack of feature so there isn’t something wrong to be fixed but rather to improve.

    I check and don’t see a setting to hide site title added by the plugin. The only way I see possible is by adding a CSS class to the “Hide element by classes” box which is not that much different if I were to do the same with with CSS in my template.

    There’s a setting for “Display Cart Icon on Menu Bar” with a convenient checkbox. How about adding another setting using the same method for “Display site title”?

    I’m not attempting to get what I want and simply am providing an honest review with feedback so you can continue improve the product. So don’t take it the wrong way and get defensive. It takes a lot of feedback and continual refinement to create a great product.

    Plugin Contributor rajivfarwaha

    (@rajivfarwaha)

    Hi Steven,

    Did you try this settings “Hide element with classes or Ids”, you can hide any element using class or id with this. Just write a comma separated classes or ids and it will hide the element. You should have used this feature if you wanted to hide any element. Its not that I am taking it personally, it is just that we give so much efforts to a free product and if someone giving a bad review without even trying all the settings given in the plugin, thats a bit disappointing. We would have appreciated your feedback to our support team using our support link and that would have definitely helped us to improve but your bad review will eventually slow down the downloads and in the long run it will impact adding new feature to the plugin.

    I believe giving a bad review to a product which has potential to become popular but does not have feature you are looking is like killing the product even for the other who could have used this free product. No product is perfect, its the valuable suggestion makes it perfect.

    Regards

    Thread Starter skylabb

    (@skylabb)

    Please read my last response carefully. I did mention about being aware of your method of using Hide element with classes or Ids. Point being that if I have to hide something using CSS, well I can just do it myself in template CSS as I’m a developer. I wonder why there’s a check box setting to hide other element and not for hiding site title? Therefore I suggest to provide a checkbox setting for hiding title as well so you have a more consistent UI logic.

    Reason I think hiding site title using CSS in Hide element with classes or Ids is not a good idea is because most users would think this box is for hiding the theme’s elements. Settings for the plugin’s elements should be all consistent with using checkboxes instead of being mixed in with CSS for controlling theme elements. Hope this makes sense.

    A review with questions and suggestion does not make it a “bad” review because it’s honest and fair with constructive feedback. How do you take feed back from users to improve your products?

    Plugin Contributor rajivfarwaha

    (@rajivfarwaha)

    Hello Steven,

    To get feedback or suggestion of new feature like you wanted, we have already provided answer given in our plugin’s page FAQ section, i.e. contact us for new feature suggestion. We take our support seriously and listens to our users. I believe bad review doesnt improve any product, it is the suggestion which improves the product. Consider a situation if some more bad review is given just because the feature they are looking is not available in the plugin and that ruins the review so bad nobody decide to use it even if it is a good product for other users, then why would someone spent time to improve a plugin which already have a bad reviews, instead of improving that particular plugin, one will focus on our upcoming plugins and hence a good plugin will be out of scope of improvement soon.

    What I believe if you want a new feature, you should contact the plugin provider at least once as a suggestion of new feature instead of a bad review and we have already mentioned that in our plugin’s FAQ section. A bad review subconsciously disheartens developer and he loses interest in future improvement of plugin.

    Regards

    Thread Starter skylabb

    (@skylabb)

    Hey buddy, you’re saying I should contact support for a suggestions, and if there’s a bug I should contact support as well. So what’s the purpose of review, users should only write about the best parts of the product? Anything less than ‘great’ is consider ‘bad’ review and should not be posted? I’m not asking for some new fancy feature. I’m only suggesting to improve the UI logic and it’s a simple suggestion.

    I think you got the feedback concept upside down. You improve a product through feedback, and users will take notice of the improvements in future releases. When you want everyone to say it’s the best product, what’s your incentive to improve it? If it is already a great product, there’s nothing left to improve, right?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘works as expected and some improvement needed’ is closed to new replies.