Support » Plugin: Glossary » Conflicting with BuddyPress after (their) last update

  • Resolved eLeXeM

    (@elexem)


    Ciao, Daniele;
    I have pitched the issue to @buddypress already, but I’m thinking you may be interested in the portion directly clashing with Glossary;
    cheers –

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hi,
    this is probably an our issues then Buddypress.
    In the 1.7 version we added the buddypress support on the activity stream, this line is the guilty one https://plugins.trac.wordpress.org/browser/glossary-by-codeat/trunk/public/includes/Glossary_Search_Engine.php#L47
    If you comment it this will remove the execution of Glossary inside buddypress.

    We will investigate but Glossary is very intensive on doing queries so this is the big problem.

    Hello, Daniele + thanks for getting back to me re this.

    I navigated down there and commented out line 47 + yes, that allowed Glossary to be active and BuddyPress to list activities at the same time. Thank you for pointing us there.

    Bit of a bummer, tho. Of course it would be fab to have auto-linking available also on UGC / community-generated contributions.

    I heard you saying that you’ll be investigating this further + thanks for that. Do you perhaps have any perspective on the chances + timeframe for getting this tackled?

    Mille Grazie – LX

    Probably after this issue we have to rethink how we integrate with Buddypress because can be very high consuming for resources.
    We have to do a query for all the terms and later parse all the content that change quite a lot because is social stuff, maybe also without a cache on the website is consuming.
    So no we don’t have any timeframe right now because we have to study how to improve our implementation.

    thank you nonetheless, Daniele;

    it’ll be most interesting to observe how you will be tackling this.
    I realize that reconciling highly dynamic functions with performance requirements is a tough thing to do.

    Buona fortuna for now 🙂 + best regards. LX

    I am closing because we have no time right now to sutdy and do an implementation that fix this kind of issues.

    hm.
    “resolved” is not quite what it is, tho’.

    If you’re not tackling an improved implementation of BuddyPress Support – don’t you think you should at least remove BuddyPress”Support” (at the very minimum: sustainably comment out the offending line (as referred to above) so it doesn’t get reinstated with each new update) from your fine plugin until this is actually resolved?

    /2 cents + regards – LX

    Hi elexem, in the readme is not specified that buddypress is supported, I am missing some other part where this is mentioned?

    hey, Daniele;
    sorry, I misspoke, then. I was going from that one line of code that had to be removed to get that earlier version of Glossary to play nice with BuddyPress + assumed (apparently: wrongly) that line was still there, potentially causing havoc.

    If it isn’t, all is well. 🙂 Cheers – LX

    Hi elexem, we removed that line that for various releases was only commented because we tried to investigate it and find a solution and we chosen to remove it.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Conflicting with BuddyPress after (their) last update’ is closed to new replies.