Issue with responsive and else

Hi,
let me answers the various issues reported:

Text placed wrongly inside the tooltip

Some terms are inside a strong html tag that create a lot of problems. If you need that the term is bold you don’t need to do it manually for all of them, this is already happening with the css.
This css rules will fix the problem of the text wrongly placed inside the tooltip:

.glossary-tooltip-content {
height: 170px;
}
.glossary-tooltip-text {
line-height: 16px;
}

About responsiveness there is a JS code that is used to fix some issue with specific themes and resolution that change the position of the tooltip itself but is available with the pro version.
With the pro version we offer the priority support and the reimburse is possible inside the 30 days after the purchase if it is not working for you.

Thanks but you realized that responsiveness shouldn’t be a pay feature (overall on desktop)? And that you are definitely going to lose potential client because of this. You have plenty of other features that could lead prospect to pay the Pro version. My experience on that is that you just driving them away. Overall when you competitors like [ removed ] have their free version full responsive and has more features than yours on their Pro version. Just saying… After I’m not omniscience. You should maybe do an A/B test to check what drives you more sales…

• This reply was modified 4 years, 9 months ago by Jan Dembowski.
• This reply was modified 4 years, 9 months ago by Jan Dembowski.

*Reads*

Thanks but you realized that responsiveness shouldn’t be a pay feature (overall on desktop)?

Why not? The author can put whatever feature they want in the free version. Or not.

And that you are definitely going to lose potential client because of this.

That makes no sense.

You point out that if the open source user wants that feature then they need to get the “pro” version. I don’t that makes you a potential customer though you do seem to want that feature for free.

*Drinks coffee*

I’ve removed reference to the author’s “competitors”. This is a support forum and not a forum for discussing features you want and how to coax the author to provide them.

Actually I’m going to buy one glossary plugin yes or yes, because it will be an important feature on my website and I will need all the feature I can get. Just pointing out to help the author, not to drive people to the competition and by the way didn’t mention the name of the competition completely in purpose.

If you’re targeting spontaneous buyers be my guess but when something is not working with a plugin most of the time you check if another work better so yes a basic feature like responsiveness (nowadays) not working fine can drive lots of potential client away without having them enjoying the free and get an idea of the plugin features and what he could get out of the Pro version.

Anyway kinda rude of you to moderate my post like this when I was just giving legit advices to another professional in sales. I have 10 years of experiences in UX&UI and ads advertisement behind me but I guess you know better…

Hello @adskiller ,
thank you for your feedback.

I think that Jan moderated your link/reference because it’s not pertinent with a technical support request, and I think it’s a wise move to not allow people discussing business/marketing choices here.

This doesn’t mean we are not open to discuss it at all.
I perfectly understand what you are trying to explain to us about the responsiveness but let me explain why some features are paid and some others are not. The Pro version of our plugin was born not for profit but just because the free version needed some sustainability in supporting users. At the time (something like 3-4 years ago) we started keep track of all the time-consuming task we use to do everyday in order to provide a good level of support and we found out that the front-end tasks are the most annoying one!
There are tons of page-builders and literally millions of different themes out there. We spend a lot of time fixing crappy code in themes or JavaScript conflict caused by some page-builder script. Our policy is “If it’s front-end, consider the pro version with the full support”.

I don’t know if you already bought a glossary license but if you did it or you are planning to buy, please drop us a line in the support area and I will very happy to go deep in this topic with you.

• This reply was modified 4 years, 9 months ago by Eugenio Petulla'.

Closing after 3 weeks of silence.