Problem/Motivation

I just realized that there is in fact an alert for a new registration, but.....!


However it appears at the very bottom of the Open Social Home Stream below the pager.

Thank you for applying for an account. Your account is currently pending approval by the site administrator.
In the meantime, a welcome message with further instructions has been sent to your email address.

Success alert at bottom of stream

How do I ensure that the Alert shows up on TOP of the Stream Page where the applicant can be assured that their registration went through?

Steps to reproduce

  1. Insure that Admin approval is required for new membership registrations.
  2. Register as a new member
  3. Unless there is something wrong in my setup, the success alert will be at the bottom of the page

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

bas123 created an issue. See original summary.

ronaldtebrake’s picture

Category: Bug report » Support request
StatusFileSize
new434.22 KB

If i'm not mistaken these are blocks you could configure within the Block layout section.
It's likely the Status Messages block is rendered below the Activity Stream homepage block due to the order of blocks.

Could you confirm this?

screenshot

ronaldtebrake’s picture

Status: Active » Postponed (maintainer needs more info)
bas123’s picture

StatusFileSize
new122.14 KB

Indeed Ronaldtebrake, I have checked that and confirmed the placement of the "Membership requests notification - Social Group request" is in fact placed above the main content, however I see that "status messages" are somehow below the 'Homepage Activity Stream' block...

Could that be the issue?
Block Layout

Here is the entire Region, please advise on:
1) The duplicate
2) Any recommended order changes etc.

Region for Main page content block

  • Membership invite notification - Social Group Invite
  • Membership invite notification - Social Group Invite (Repeated ???) ***
  • Membership requests notification - Social Group request
  • Activity Stream: Homepage stream block - Lists (Views)
  • Status messages - System
  • Main page content - System
  • Group Managers: Block List managers - Lists (Views)
  • ActivityStreamGroup - Lists (Views)
  • Event requests notification - Social Event
  • ActivityStreamProfile - Lists (Views)

*** The duplicates do have some (unique) differences in "Page types" and Page restrictions!
To be honest, I am not quite sure why I would have done this, but there is some logic based upon the different configs

ronaldtebrake’s picture

Sorry yeah dont know why that Membership Request Group block was highlighted in my screenshot, but its indeed the status message block which should be rendered above the Homepage Activity Stream' block that will fix this for you.

These duplicates I cant really help you with, that could be a perfectly fine use case to have especially considering the individual differences.

bas123’s picture

StatusFileSize
new170.43 KB

Let me ask you a question RonaldteBrake,

First, yes that fixed the problem for the most part, however, because I had received some complaints that the status messages weren't visible at all (because they were on the bottom of the stream), I moved that status block just above the "AN homepage hero block" in the Hero region. And now I would think there can be no complaints as it appears like a banner across the page!

In our use case, we also have an Adsense Advert block above that, but I am pretty sure that the status messages will now be loud and clear for most cases!

What do you think?
Status Message fixed

ronaldtebrake’s picture

Status: Postponed (maintainer needs more info) » Fixed

I would imagine that to be true, obviously can't tell for all use cases of your custom community, but my gut feeling is that that would work.

Alternatively you could play around with adding more blocks, you can make sure those blocks are not rendering as duplicate by configuring the visibility. So they are only added to some pages or removed from others.

bas123’s picture

I have now had a chance to monitor this in realtime and highly recommend placing the :Status Block" above the 'Contend Region' simply because it renders a full-width Alert that is more visible and is far less likely to be missed.

Even the notice that a post or topic has been added, edited, or deleted is now clear and noticible, but more importantly the red warnings such as a missed field are now more obvious in this position.

In our use case, the bottom of the Hero Region works best, but any of the higher/wider regions would work IMO

Thank you RonaldteBrake for your prompt attention to this as it actually was helpful in resolving a dispute I was having with the Facebook/Meta Developer Team when they were claiming that my site was broken and difficult to navigate and justifying rejecting some APP Appeals I had for OEmbed etc.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.