[@hnla Participant 16 years, 6 months ago]

Two threads running on same subject:

https://buddypress.org/forums/topic/there-is-a-serious-bug-in-buddypress-123-signup-validation?

[@hnla Participant 16 years, 6 months ago]

Two threads running on same subject:

https://buddypress.org/forums/topic/bug-in-check-for-illegal-names-quite-critical-bug-in-buddypress-123

[@hnla Participant 16 years, 6 months ago]

Not sure how difficult it is to code 5 e-mail-fields

Actually very easy especially if you don’t mind all sorts of potential nasties happening, on the other hand look at the testing that went on for this plugin as an example of even with what appears a trivial matter or function just how much in reality needs to be thought about and tested, the work Boone did to get to the stage he has with the plugin cost a lot in terms of time and time translates to an implicit cost that in the case of these developers is seldom recuperated.

[@hnla Participant 16 years, 6 months ago]

Erich, it can be done as is discussed on the invite-anyone thread, at the moment the best approach is create the group, then when created go to your profile from where you can then begin to send your email invites, or finish the group creation , click the send invites tab, on that screen use the link to your profile > send invites.

So Users CAN send email invites, What may be a help as I mentioned is that there is more detailed terxt guides on creation screens explaining what and how to do things.

[@hnla Participant 16 years, 6 months ago]

Is there a possible confusion here? ‘send invites’ on group creation exists in core but it’s limited to your existing friends only, it’s not something that the plugin can or should play around with? The plugin extends and adds functionality to the default ‘Send Invites’ and also adds the ‘send email invite’ but I may have misunderstood what you are asking , if so apologies, ignore me and Boone will furnish a more apt response.

[@hnla Participant 16 years, 6 months ago]

Thanks Boone, normally don’t like aps like poedit but actually it’s faster to use as it generated the .mo same time you save the working .po file so a swift upload and done, I now have the archaic British spelling of Favorite

[@hnla Participant 16 years, 6 months ago]

I’ll look into poedit then but still not 100% sure of the process/procedures behind .po/.mo files but will have to try and read up them.

[@hnla Participant 16 years, 6 months ago]

Have you verified your hidden group problem with a non-admin account?

erm… um… damn, far too early in the morning to have been thinking clearly, had only had the first cup of coffee, tying to do half a dozen things at once, lack of focus , rushing and a heap of other excuses. So you you had covered the hidden group issue then

Not sure if language files are easier? personally not really used to working with them so instinctively feel they are something that make things harder? but that might just be fear and the fact that the codex instructions rambled on about having to create .mo files from command line, which is fine can do but seems a hassle, wanted to change ‘Favorite’ site wide to the more arcane version but gave up when I saw the steps I would have to take to simply change one word!

[@hnla Participant 16 years, 6 months ago]

Where is the tabs nav string to be found? I’m going to have to truncate it to ‘Invites’ rather than ‘Send Invites’ – not really feeling the love for the WP/BP api at the moment simple things are too awkward to do

[@hnla Participant 16 years, 6 months ago]

A couple of minor? issues:

default message text has %whatever% instead of %%whatever%%

Slightly more of an issue?

enabling ‘Allow group Invites’ unfortunately drops ALL groups into screen this includes ‘Hidden Groups’ as such on production I have had to disable feature although I think I can probably get a fix in place to not show hidden groups for the interim.

Of course it might be a case that this ‘user’ has actually created the hidden group and is the owner/admin and so does want to invite to this group so simply preventing hidden groups from showing might not be the answer and things become trickier – I guess hidden groups would need to be tested to see whether the user was the owner /admin of that group and only then would that group be displayed otherwise it would be removed from the list.

Our situation is slightly different as we don’t allow users to create groups and we would never want or need to send email invites to join hidden ones so I’ll either try and run a check to see if a group is marked as hidden or failing being able to achieve that I’ll have to run with the option disabled.

Off Tangent: one further link on the account tabs is one too many, even with a generous min-width tabs now wrap which is very unfortunate as there is no real way round that short of increasing page min-width,. Now have to spend time finding an alternative approach to those tabs which I hadn’t factored into things *sigh* The tab approach laid out as is in the default layout is a flawed approach given that plugins can add their links to these tabs, as with any layout there has to be a limit if working a horizontal tab style set of nav links otherwise one has to run them vertical really.

[@hnla Participant 16 years, 6 months ago]

Chouf1 your point regarding Facebook cloning and trending is well made and perhaps ought to be stressed from time to time I’m less interested in seeing BP and it’s child plugins attempt to simply ape Facebook in every way possible than in seeing it identify and establish simply what social networking is about.

The essence of a community – especially at the outset – is about a great deal of care and nurturing, somewhat less about features than about a place for interaction between members, of good quality content and discussion and that has to be helped along initially and does require a lot of commitment on the part of the site operators.

It is therefore entirely correct to assert that the tool doesn’t make a community and to bear that in mind. BP is a great tool or potentially a great tool, but it is a tool, something that facilitates communities, growing that community into something vibrant with a soul and longevity is where the work begins.

[@hnla Participant 16 years, 6 months ago]

Something I struggled to get working :confused: the codex could do with some examples a la WP codex, but documenting is a chore isn’t it at least my heart always sinks when I realise I have to start writing stuff down rather than bashing out code.

[@hnla Participant 16 years, 7 months ago]

Sorry not Boone but your comments made me think about another logic issue for users.

Your point about standard default BP and send invites is why the original plugin was created to provide access to all members.

With the plugin activated, now when creating groups one reaches stage 4? and the send invites is the complete member base, Boone having removed link to send email invites on this screen.

Ignore step 4 and complete creation of group and you are presented with the new group main page with invite screen now having the link to send email invites taking you to profile.

The only slight issue here is that having created the group and now having the option to send email invites the user might well assume that the invite is being sent to Invite their friend to THE group they just created and from which they just navigated – however if you have the invite to group option disabled in admin config then the user can’t send an invite that explicitly invites to that group?

What would help users a lot would be a little more by way of general instruction as they perform various tasks, in this instance at stage 4 ‘invite friends’ it states simply “Select people to invite from your friends list.” there is a tonne of space to add something like :

“If you don’t wish to invite friends at this stage click ‘finish’ At a later time you can select the group tab ‘send invites’ and either select from site member list or click link to send email invites from your profile page. “

In fact the creation screens should display a step by step guide that simply details the process and options. It can easily sit there to the right (if we’re talking about default theme) This is something that I will be adding myself anyway in general terms where it might aid the user to have more detailed info.

It’s possible that simply expanding the textual guidance and instructions would at times help overcome basic newbie confusion when performing functions across BP?

[@hnla Participant 16 years, 7 months ago]

0.5.2 fixes the issue I was seeing on the user blog.

And just noticed your comment at top of file regarding $bp->action_variables so ignore my rambling comments above.

[@hnla Participant 16 years, 7 months ago]

0.5.2 fixes the issue I was seeing on the user blog.

And just noticed your comment at top of file regarding $bp->action_variables so ignore my rambling comments above.

[@hnla Participant 16 years, 7 months ago]

In_array error: I have it occurring on a user blog (subdomain) it strikes me that line 8 in cssjs.php is in_array second parameter $bp->action_variables. I’m not really up to speed with how BP is involved when one is viewing an MU blog (apart from the obvious admin bar) but is that actually available as such?

[@hnla Participant 16 years, 7 months ago]

In_array error: I have it occurring on a user blog (subdomain) it strikes me that line 8 in cssjs.php is in_array second parameter $bp->action_variables. I’m not really up to speed with how BP is involved when one is viewing an MU blog (apart from the obvious admin bar) but is that actually available as such?

[@hnla Participant 16 years, 7 months ago]

There was a thread which touched on the subject of plugin activation, I hadn’t really clearly understood the difference between ‘Site Wide’ and basic activation, or why sometimes activating a plugin using the plain link on left side actually activated the plugin sitewide placing the plugin into the list at the top of the page reserved for sitewided plugins that users cannot deactivate .

There is a configuration option in the plugin primary file hat should ensure that the plugin is activated sitewide regardless, it doesn’t always work and must be only half the issue, but I raised that on the other thread.

My approach to BP plugins is NOT to upgarde them automatically but manually deactivate, remove old folder to safe area outside doc root; upload new plugin reactivate using sitewide link, even though most BP plugins should or even ought to activate sitewide; there’s no reason for any general member to have access to BP or any of it’s plugins, and I don’t want to chance to having people access and deactivate a BP plugin

[@hnla Participant 16 years, 7 months ago]

There was a thread which touched on the subject of plugin activation, I hadn’t really clearly understood the difference between ‘Site Wide’ and basic activation, or why sometimes activating a plugin using the plain link on left side actually activated the plugin sitewide placing the plugin into the list at the top of the page reserved for sitewided plugins that users cannot deactivate .

There is a configuration option in the plugin primary file hat should ensure that the plugin is activated sitewide regardless, it doesn’t always work and must be only half the issue, but I raised that on the other thread.

My approach to BP plugins is NOT to upgarde them automatically but manually deactivate, remove old folder to safe area outside doc root; upload new plugin reactivate using sitewide link, even though most BP plugins should or even ought to activate sitewide; there’s no reason for any general member to have access to BP or any of it’s plugins, and I don’t want to chance to having people access and deactivate a BP plugin

[@hnla Participant 16 years, 7 months ago]

@Erich73 – Good call on the group creation issue. I think the answer is just to turn off the message for the group creation process. I’m about to check in version 0.5.2, which makes this correction. Email invitation can only be done from the normal Send Invites screen, so the confusion shouldn’t happen.

fwiw that would have been my call as well, there’s enough to do creating the group, let the creator have a breather and come back to the newly created group to decide who to invite send mail to.

Apropos the ‘in_array() expects parameter’ I too have this occurring on one of my local test installs but not another and can’t really see what is different between the two but it’s not happened live, it feels like a loading order issue but haven’t had time to investigate the cause

[@hnla Participant 16 years, 7 months ago]

@Erich73 – Good call on the group creation issue. I think the answer is just to turn off the message for the group creation process. I’m about to check in version 0.5.2, which makes this correction. Email invitation can only be done from the normal Send Invites screen, so the confusion shouldn’t happen.

fwiw that would have been my call as well, there’s enough to do creating the group, let the creator have a breather and come back to the newly created group to decide who to invite send mail to.

Apropos the ‘in_array() expects parameter’ I too have this occurring on one of my local test installs but not another and can’t really see what is different between the two but it’s not happened live, it feels like a loading order issue but haven’t had time to investigate the cause

[@hnla Participant 16 years, 7 months ago]

Have a look through the files it will only take a second

[@hnla Participant 16 years, 7 months ago]

Have a look through the files it will only take a second

[@hnla Participant 16 years, 7 months ago]

edit/ hmm far too slow

Use a conditional template tag

For reference they are found here:

https://codex.buddypress.org/developer-docs/conditional-template-tags/

You will want something like:

bp_is_front_page()

Wrap the div#search-bar in an:

<?php if(!bp_is_front_page()): ?>

<div id="search-bar">



</div><!-- #search-bar -->

<?php endif; ?>

Something like that anyway.

Am awaiting how it’s done!

Surely Gpo1 you had an inkling how to do this hadn’t you?

[@hnla Participant 16 years, 7 months ago]

edit/ hmm far too slow

Use a conditional template tag

For reference they are found here:

https://codex.buddypress.org/developer-docs/conditional-template-tags/

You will want something like:

bp_is_front_page()

Wrap the div#search-bar in an:

<?php if(!bp_is_front_page()): ?>

<div id="search-bar">



</div><!-- #search-bar -->

<?php endif; ?>

Something like that anyway.

Am awaiting how it’s done!

Surely Gpo1 you had an inkling how to do this hadn’t you?