- Quint A. Rahaman, Jr. on September 13, 2022 at 10:41 am #46498
Ugh. This should be an item for the core team to resolve. Because of this inconsistency, the visibility field is also underneath the input field which may lead to two pieces of data that the user has to process in the same spot. The visibility info is in the right spot and the info field should be directly under the legend since that’s what it is meant to explain and/or set the stage for the upcoming input.
An ugly recommendation would be adding a setting to the Add/Edit xProfile field page which is set to default and provides the user with the option to reverse the default whatever that may be.
The other ugly suggestion is to execute code to relocate the element after the page has been rendered. Unfortunately, this movement would be visible to the user.
Or if there’s a hook for the field group pages before it renders, run the relocation code then? Do you know if there’s such a hook?
- Quint A. Rahaman, Jr. on July 2, 2022 at 6:00 am #45602
I’ve figured it out. In the BuddyBoss Locations Autocomplete plugin Settings page, if the Locations field for Country is selected, which is what I had done, then autocomplete is targeted for that field. And since I had already designated your Country field, that means two options were being offered. So, I deselected autocomplete for that field and now it works like it should.
- Quint A. Rahaman, Jr. on June 22, 2022 at 10:10 am #45473
I understand the thought behind that approach. The one disadvantage I see is documentation that advises the user regarding the use of specific tabs, when eventually, the Admin may decide to remove all tabs but one, yet the documentation still refers to the tab label that the user can no longer see.
It’s an outlier given the extremely low probability of occurring. No change recommended other than a note/text making the Admin aware that if only one subtab exists, then its label will not render since it’s not necessary.
- Quint A. Rahaman, Jr. on June 22, 2022 at 9:59 am #45471
Thanks for quickly circling back. This almost worked. The subtab that you added was not visible when I navigated to the Test Group. See attachment.
Only when I added a second subtab did they both became visible. See attachment.
- Quint A. Rahaman, Jr. on June 22, 2022 at 12:03 am #45466This reply has been marked as private.
- Quint A. Rahaman, Jr. on June 13, 2022 at 1:17 pm #45360
Thanks for the explanation. Then, that won’t work for us from a “messaging” standpoint. However, from a curation of “friends,” or whatever categorization they invent, then it fits the bill. And since I have control over notifications, my previous concern has been addressed.
Thanks for writing it,
- Quint A. Rahaman, Jr. on June 13, 2022 at 11:11 am #45348
One more observation: on the Members Directory, the Add to Circle button should only be visible/available to the logged in user when that target Member has Connected. If not, that interaction is a bit like stalking. Just an opinion.
- Quint A. Rahaman, Jr. on June 13, 2022 at 1:43 am #45334
You’re right, my apologies.
- Quint A. Rahaman, Jr. on June 12, 2022 at 12:18 pm #45319
I don’t see where that capability lies. Andrea, in Italy, is the plugin developer and is the one who performed the troubleshooting which lead to the code and recommendation provided earlier.
Where on here is it? I must be missing something or looking at the wrong spot.
- Quint A. Rahaman, Jr. on June 11, 2022 at 1:17 am #45292
On a lark, I just tried using the Xprofile Fields – Decimal Field again. I specified a precision of 4 and step size of .0001. It worked!
Why? I think that the first time I tried it, I did not specify the precision, only the step size. So far, it fails if those are mismatched.
If you like, this topic can be “resolved.”
P.S. It may be helpful to add this info/direction for that field in the plugin’s FAQ.