Forum Replies Created

Viewing 15 replies - 16 through 30 (of 80 total)
  • Forum: Plugins
    In reply to: [Glossary] Upgrade
    Plugin Author Eugenio Petulla’

    (@igenius)

    First of all, thank you for the review!

    I just checked and don’t worry @sunshine4nikki you didn’t pay anything at the moment. 🙂

    Did you opted-in or did you skip the registration in our system the first time you activated the plugin?

    Mail us your website URL at [email protected] so we can investigate your problem.

    Plugin Author Eugenio Petulla’

    (@igenius)

    Hi @sunshine4nikki,
    don’t worry, your glossary terms, categories and settings are in the DataBase not in the filesystem so you can delete the plugin folder and upload the new one without any problem using your FTP.

    We provide premium support directly from the dashboard to our Pro users, I strongly recommend this plan for people that are not used to perform this kind of operations in safe by themselves.

    Let us know if everything is ok after the plugin restore. 🙂

    Plugin Author Eugenio Petulla’

    (@igenius)

    It will work excatcly like you described in the post, if you wrap some content with the shortcode our search engine will ignore ALL the content inside it. We are planning to implement it as a shortcode just because this kind of markers are easy to detect if mixed in HTML (and this is the reason why not only WordPress used square brackets for this purpose).

    Better Eg. [glossary-ignore]A lot of text mixed with some terms that we have to ignore and some HTML <a href="#" target="_blank" rel="nofollow">tags</a> that I don't want to pass to our plugin's parser[/glossary-ignore]

    Talking about the workaround, I’m honestly confused because I can’t recognize this editor. Is it some sort of page builder? How the content is passed to front-end? Is it a shortcode based editor?

    It looks like the builder passes the values you put inside it to front-end using shortcodes. This is not a great solution in my personal opinion, our engine actually avoids to parse links and <a> tags if you put it in the content directly (you can try with the classic WordPress editor) so it’s a very strange behavior. In first instance I thought that you had a simple <button> tag to ignore but now I understood that you have an anchor with a button class.
    This depends a lot on your page builder. Page builders are the evil in my opinion because you lose control on filters priority, specially the builders that make an intensive use of shortcodes in order to render the content.

    By the way, let us know what builder is so we can try to find a specific solution (if it’s open source and free) or just wait for our wrapping shortcode so you can use what you want in the page without any hassle. 🙂

    Forum: Plugins
    In reply to: [Glossary] Revisions
    Plugin Author Eugenio Petulla’

    (@igenius)

    Hello @art180,
    thank you for reporting this. We are discussing about this feature internally because we want to let user choose if enable or disable revisions for glossary terms by the plugin option panel.

    Personally I hate auto-enabled revisions because mostly of the time are useless and heavy on the DB but I know that sometime are a life saver! 🙂

    We are just figure out how to implement this in the correct way, but I think this will be in the next release for sure! 🙂

    Plugin Author Eugenio Petulla’

    (@igenius)

    @sjf I think that a class is not a viable option because people are not used to put HTML attributes directly in the content and generally it’s not a good practice to do it. We are discussing on our internal tracker about implementing a specific shortcode in order to ignore terms in the content.

    Eg. [glossary-ignore]TERM TO IGNORE[/glossary-ignore]

    For your last request I think it’s not possible to provide you a filter or something similar in order to be used in your functions.php because of the nature of our “term search engine” that is a very complex Regex that parses the content.

    Feel free to report here all the edge cases you found and we will be happy to work on the regex in order to catch those exceptions with the engine. I hope the new shortcode will easily do the rest of the work 🙂

    Plugin Author Eugenio Petulla’

    (@igenius)

    Hello SJF, thank you for reporting this.

    I can suggest another tweak in order to avoid this behaviour, just wrap the term between an anchor like this:

    <button><a>DoNotLinkThis</a></button>

    This will prevent the spawn of the term. Obviously is just a tweak and we’ll have to work on this in order to fix it and detect also button elements but for the moment could be a good go-to option 🙂

    I’m going to open an issue on our tracker and probably this fix will be in the next release.

    Plugin Author Eugenio Petulla’

    (@igenius)

    So YOU were not able to make it works for YOUR website and instead of open a support thread just leave a bad review on the plugin?? What’s that, a sort of revenge?

    Open a thread if you want solve issue instead of dropping bad reviews out of nothing, we worked a lot on the plugin and also we are here in first line for support, but you have to be enough smart in order to ask for it!

    Ok, this looks like you have too clean your cache before cleaning the Facebook one. Let us know if you solve the problem in this way.

    Plugin Author Eugenio Petulla’

    (@igenius)

    I think you can try to import the terms using WP All Import plugin (https://ww.wp.xz.cn/plugins/wp-all-import/) , the only think you have to do is just to separate the items and create a properly CSV file. After done this you can import your text file into WordPress but 82.000 seems to be a lot of terms in order to perfrom a good import so maybe is better than you split the file in more small chunks or your server will be dead soon! 😉

    Plugin Author Eugenio Petulla’

    (@igenius)

    Hello acokaj,
    thank you for the time you dedicated to our piece of code 🙂

    1. We really don’t know, personally I’ve tested it with a lot of terms (something like 10.000) and the results were amazing, everything runs smooth. We use Query Monitor in order to do performances tests but I have to say that I’m on a vps server so results may vary from hosting to hosting, if you are on a quite good one I think you can easily try and report to us if you have some sort of performance issue! We are very curious about it! 🙂

    2. We are improving also specific language matching but it’s hard with all the alphabets that exists nowdays, so we are tring to work close to our customer in order to get more accurate feedback about their native language. If you want to report a bug on this maybe it’s better to open a new one so we can discuss on the implementation.

    3. For the free version of the plugin it’s quite easy, you can directly go on translate WordPress website and you can do it from there! Here is the link already set up for contributing on albanian translation: https://translate.ww.wp.xz.cn/locale/sq/default/wp-plugins/glossary-by-codeat

    The Pro version has some features like case sensitive matching, more tooltip templates and a customizer, Pro shortcodes and widgets, plus there is direct support and customer care. You can find more info on the dedicated website: https://codeat.co/glossary

    P.s. we really love Albania and we are involved in OSCAL Tirana almost every year! 🙂

    Plugin Author Eugenio Petulla’

    (@igenius)

    In order to solve your broken links issue I ask you to try refresh your permalinks. Just go under your wordpress permalink settings and push the save button. Then test your term’s links again.

    I’m sorry to hear about your frustration on our pricing policy and I hope you will have the occasion to get some discount for the upgrade.

    Let me know if you solve the broken links issue,
    Eugenio Petullà – codeat

    Plugin Author Eugenio Petulla’

    (@igenius)

    Welcome narasicoaching,
    thank you for using our plugin and for your feedback.

    I cannot understand if there is a bug to fix for your free installation or is just a lack of features in the free version?

    The feature you are looking for (case sensitive matching) is a pro feature because it causes to us more work/test than usual, we have to parse the content of text twice and in a more specific way than the standard one. Due to the nature of our plugin we have a lot of specific work to do in order to check the compatibility of other plugins and themes with our auto-link engine and it’s a time consuming activity, so we switched to this freemium revenue model in order to continue develop and maintain the code.

    To us 29 USD is a fair price in order to activate some Pro features and get access to direct support on your specific website. We also provide some promotional discounts sometimes so if you are using our free plugin maybe you have just to wait for a newsletter with a coupon in it so you can switch to the pro version gaining a reduced price per year.

    Thank you for providing us a feedback,
    Eugenio Petullà – Codeat

    Plugin Author Eugenio Petulla’

    (@igenius)

    It’s in the code, is an option that we have to add to our code in order to make it compatible with YARPP. I was just talking with Daniele, sorry. By the way… we are working on it! 🙂

    Plugin Author Eugenio Petulla’

    (@igenius)

    I never used this combination but I have to ask if you checked the CPT you created into the settings panel of the plugin before starting investigating on this issue.

    Maybe I didn’t understand what’s the goal, can you give me a more detailed example?

    Plugin Author Eugenio Petulla’

    (@igenius)

    Very strange behavour but I have to ask if you did clean the cache. On some server can pass a little bit more time in order it reloads, maybe you can force it by purging the cache and solve the problem suddently, give a try!

Viewing 15 replies - 16 through 30 (of 80 total)