Custom profile fields do not show up on the registration form

@michaelschutz ,

i Cannot tell you how relieved I am to finally get a response on this and that it is a known issue by the Drupal team!
I was unable to find that resource via my searches!

However I must ask!
At https://github.com/goalgorilla/open_social/pull/1407 /
Issue #3056814 by truls1502: Update drupal/field_group from 3.0-beta1 to 3.0-rc1 #1407 the status is Closed

I reported this here over 19 days ago and even farther back in the Open Social channel on Slack, with no responses!

Indeed the error code validates your analysis!
See: https://www.drupal.org/project/social/issues/3121043

And in my case, yes I need both, in fact I am hoping they spend even more time developing the capabilities of adding the attachments to extend to posts (at least increase the limit above one) as my goal is to emulate as much of a Facebook experience as possible in order to attract as many users from that platform in my demographic as possible :)

In that I am willing to wait for a resolution (even though its been over two weeks since YOUR reply in #3056814 has gone unanswered), my first instinct is to let this issue sit because it seems to have no other ramifications for the site I am developing in an online subfolder/domain with no real users and no applicants!

I did start another instance online just to try and troubleshoot the problem and one or two locally that I could experiment with as well so I could verify this but I must ask you if you think updating Field Group from 8.x-3.0-beta1 to its latest stable incarnation of 8.x-3.0 - 28 January 2020 OR if disabling the social_comment_upload module is a viable choice at least to test this!

I suspect that in the final analysis the answer is to update the field_group to fix that issue at the EXPENSE of losing the attachments in comments, and hope that the Open Social team picks up the ball on the conflict!

What do YOU think?

@michaelschutz,

First I wish to thank and commend you for your technique of stepping through my concerns.
This is a method I wish more folks would use in addressing others' discussions!

Second, I wish to clarify what seems to be an overall misconception about my understanding or appreciation of the process of cooperation and sharing of information in the Community Commons Space!

I am fully aware of the prioritization of efforts the developers of this now "monetized" distribution had adopted and fully understand and appreciate the time they commit to serving the Open Source aspect.

I just wish that rather than ignore a request regardless of its duplication, they would take 10 seconds to say: "We are aware of this and have it in queue, see xyz-[link] to follow its progress", or similar. It just seems to me that by doing so would save a great deal of their time as well as those of us who are dependent upon their feedback!

I have followed this Drupal Distribution for several years now, since it's initial release which predates their current business model. It wasn't only until just recently that the Distribution evolved into the viable product that it has become!

What do YOU think?

What I think doesn't matter much, as I'm not a coder and can't help actually solve the coding problem. Also, I'm just a free user of the OpenSocial distribution, so I don't have much pull. :)

My question referred specifically to the two choices that had preceded that:

but I must ask you if you think updating Field Group from 8.x-3.0-beta1 to its latest stable incarnation of 8.x-3.0 - 28 January 2020 OR if disabling the social_comment_upload module is a viable choice at least to test this!

I don't have time to test immediately - maybe next week - but yes, that's what I am planning to do on a test site - set it up the way I wish it worked, then update field_group to 3.0 stable, and see what happens. If it doesn't work, disable the ability to add attachments on comments, and see what happens. I can offer reports on testing, but I can't tell you from the code *why* it's not working. If you can, all the better!

I can report that:
With my thanks again to you, I HAVE tested this on two distributions and can report that you are 100% correct that by updating the Field Group module, the Profile Fields are indeed rendered in the Registration form!

Secondly, the comment attachments and the ability to add new ones have disappeared from the reply forms!
As if they were never there!

And in addition, the functionality of the 'Filed Grouping' capabilities in the forms seems to be greatly improved and self correcting!

I don't know how much time you have spend setting up Vertical/Horizontal Tabs, Accordions, Fieldsets etc. with Open Social and particularly in the Profile form and display, but for me it has been a struggle and any hierarchical misstep or coding error could potentially throw errors or even lock up the form completely... This seems to have been resolved as in my hour or so in working with it, found it to be a much smoother operation!

My only other frustration is that the only technique this module offers of Horizontal Tabs (that I have successfully used in other distributions) simply does not work in Open Social and the next best thing is Accordion Items which in the event of a lengthy Introduction (Which I provide as a means for the user to enter a Biography and Resume) can get quite lengthy an thus using the accordion, can be a browser scrolling issue!

So, I too would like to share this with the O.S. Team and if nothing else validate that the issue with the Profile Fields is indeed resolved with the Field Group Module upgrade HOWEVER, by doing so, that wonderful feature of Comment Attachments has been lost!

But I am not sure if you were suggesting in confirming that:

It's a known issue by the Open Social team, just for clarification.

You were suggesting that my feedback would not be of value as they are already aware of and have performed these tests themselves but have down priortized it in their "grand scheme"!

Best Regards!

Thank you @Kingdutch for lending your attention to this!

I leave it to you and your wonderful team members to determine the priority of making coding fixes, however for our purposes the ability to have the Profile Fields appear in the registration process is essential to us as we must approve applicants on the basis of certain criteria that cannot be determined by a Username and or email address!

I have solved this in the short term by following the advice provided above in updating the Field Group module at the Loss of users having the ability to upload attachments in comments which I can only assume is something you may already be working on... No?

And my apologies for utilizing the "all caps" in the thread's headline (now corrected) as I was of the impression that doing so was only considered "Shouting" in chat rooms etc. - by using it in this application I considered it a means of "headlining" (drawing attention to) the subject as in the of the attribute: text-transform: uppercase; which is commonly used for that purpose. I will rely on the use of the 'heading' and 'strong' attributes in the future!

Agreed on this, comments are indeed back in play!

As well as what appears to have been a lot of other fixes :)

@MCMLB,

Thank you for your reply, however that setting was activated! See screenshot: https://www.drupal.org/files/issues/2020-04-07/settings-no-profile-field...

This was a coding issue that was resolved by the Open Social Developers and rolled out in a new release!

That is why you see at the top of this thread that is says "Closed (fixed)"