eLeXeM

omg, I’m so embarrassed right now. Found it, thank you.

I was only looking in the admin pages content area and completetely missed out on the menu in the sidebar.

Best regards + please pardon my dumb ?? Cheers – LX

thanks for getting back to me re this.
sadly, your suggested solution causes the explanation bubble to not be shown above the other content as well :/

However, setting
.glossary-tooltip {z-index:2 !important;}
in combination with settting
#main-nav higher than 2
did the trick then, bey the looks of it now.
??
so, cheers – lx & team

sure. ??

observable functionality:
• On the front-end, the plugin adds a select as #whats-new-options under BuddyPress’ #whats-new-form’s #whats-new-textarea, which allows the user to select to whom the currently created post should become visible.
• If so set in the plugin’s backend, the select remains visible under published activities, allowing each activity’s owner to change their mind later and set the select to a different option.
• as far as was scrutable so far this does not only govern visibility on-site, but also flow into RSS outputs (which is one of my personal primary concerns).
  Both appear to be working as one would expect from the plugin’s self-description.
• Its backend options page is actually quite well-thought out, too; it even recognizes other relevant 3rd party add-ons (at least I could see that happening for BuddyPress Follow, another nice addition (maintained by your BP-team-mates @apeatling and @r-a-y btw, afaik)).

observable misconduct/s:
• The most noticeable was that a selected option is not not properly reflected on the frontend after saving, even though the selected option appears to be heeded system-side. Example:

• I wish to post a new status / activity, type something into the text box, then wish to make it available to Friends Only and pick the relevant option on the privacy select dropdown, then I hit ‘publish update’. The update is saved as expected
  but
  the after-save representation of the select now says “Anyone” (I am unsure whether it just jumps back to some default or does something even quirkier (more below)).
• Checking the activities’ feed RSS-output however gave me the impression that the item in question does not get served out (which is good, being the desired behaviour). I tested this 2 times + saved another public one after that, to give me a visual event bracketing the ealier updates.

• Another notable occurence is that updates published earlier (before arrival of “BuddyPress Activity Privacy” are reflected as “Only Me” – which is clearly wrong, since there was no way to set that and b) other (dummy) users can still see those items.
  This is why my initial bet is on an issue with “only” outward representation of what still appears to be working under the hood.

You can have a look at our prototypes’ activity page @ https://liberal.is/aktivitaet (which does look rather botchy yet, as I’m still pottering about quite a few odds and ends); I also suppose you’ll need a logon to actually see the privacy interface’s controls. Let me know if you get stuck somewhere signing up – it’s all still a bit wobbly.

#hth; please let me know if I can help you with anything further from my end.
Best – LX

• This reply was modified 5 years, 11 months ago by eLeXeM. Reason: mended missing indentation
• This reply was modified 5 years, 11 months ago by eLeXeM.

Hello there, @boonebgorges;
thank you for getting back to me re this + the kind offer you’re making.
Since I personally don’t have the level of competence to entrust said ‘heavy lifting’ to myself, I’d be thinking the second angle to appear more promising. If someone with your insight were to have a look into why / where this plugin is misbehaving
and maybe giving a hint as to what to adjust
that might already prove useful. I wouldn’t even know how to determine whether “the current plugin isn’t working anymore because of some recent changes in BP”. :/

Speaking of potential findings I figure, since this plug-in hasn’t been updated in a while, it won’t hurt for admins using it to dive into the bowels and wrench in suggested changes by themselves, if they’re not overwhelmingly complex for mere mortals?

How about you count the cups of coffees you kill while you look into this + I’ll cover them ?? to coax you in, heh ?? A box of Oreos or 2 for thoughtful dipping on top if we end up with a viable fix? [ I’m not particularly affluent, otherwise I’d be putting something more akin to an actually substantial offer on the table – but I’m trying to sweeten the effort to the best of my abilities anyhow; perhaps there is some credit to be had for that. ?? ]

Cheers – LX

just a quick thank you to @howdy_mcgee ??

your solution suggested above worked like a charm for me;
cheers a ton! LX

thank you for your swift reaction, Maciej.
/closed ??
Best – eLeX

acknowledged.

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

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

cheers ??

hmmmkay, it seems to be running alright currently; I only forwarded this to your attention since this was the first time, Shield ran into that sort of trouble. So I guess this can be regarded as resolved, then.

+1 to what @gillesgagnon said ?? + goes both ways (y) Cheers – LX

Hello, Maciej +
thank you for addressing this so quickly (y).

I have done as you suggested +
it appears that what you did resolved the issue.

Cheers ?? LX

• This reply was modified 6 years, 2 months ago by eLeXeM.

Hey Rob + thanks for getting back to me re this.
As I had the same issue affecting another plugin as well, I have in the meantime received the tip from @freemius in that other thread to run their dedicated fixer pluggie. Ran that and the other plugin could be reactivated without crashing the site anymore.

To see if the cleanup also healed yours from throwing fatals, I have re-activated that, too, and loaded the front page a few times. It seems that cleaning up Freemius did the trick here as well, as the site didn’t crash so far.
Will keep you posted if it breaks any of yours again, but for now I think we look ok.

Cheers – LX

Have done so (data dump in your mail) + got the response ”Freemius records successfully cleared! You are now safe to activate any Freemius-powered plugin or theme.”
Have re-activated Glossary and the site is so far accessible without crashing, so that’s good. Will monitor the debug log for anything related coming up + let you know if anything does.