I have the pop up option ticked but have yet to see where/how these PM pop up messages happen. Any help appreciated.

Make sure you have added the Welcome center view to the page.

I am a little confused. I need to add the welcome center module to each page I want the pop up?

Yes. Or you can just create a blank custom view and add it to the page. An instance of Active Social must be on the page in order for it to work. I've actually never seen anyone use it without the Welcome Center. You may need to create a new custom view by copying the MessagePopUp template.


Moving to customization forum.

You can also set up the Welcome Center in your skin so it appears on every page. This post may help: http://www.activemodules.com/active...x/2/#61461

Looking at the modules list as admin I only see 'active social' for a module.. how do I copy the welcome center specific module to various pages I want the pop up?

Posted By Will Morgenweck on 19 Jan 2011 08:54 AM
Make sure you have added the Welcome center view to the page.

I have often wondered why this is the requirement. My thoughts are the each social view should have this code prebuilt within (code to check for email, alerts, notices etc) and the social settings could then have an option *not* to show it if required. I have pondered this as i do not want to add the welcome control to my skin header etc as it throws off the feng shui of the header.  This is *more* than just a welcome thing. Even as a user moves amongst views, if a new notice comes in, they need to know, and adding the welcome view to each seems intrusive. Just thinking aloud. drew..

It's not a requirement. It is possible and the architecture certainly supports it, I've just never had anyone request to set it up that way and never tried it myself. Also, the original intent for the welcome center was to be a skin object that replaces the user skin object in DotNetNuke. If you look on our site, that is exactly what we have done. All we added was the small envelope icon to let the user know there is a new message.

Posted By Will Morgenweck on 19 Jan 2011 04:04 PM

I have often wondered why this is the requirement.

It's not a requirement. It is possible and the architecture certainly supports it, I've just never had anyone request to set it up that way and never tried it myself. Also, the original intent for the welcome center was to be a skin object that replaces the user skin object in DotNetNuke. If you look on our site, that is exactly what we have done. All we added was the small envelope icon to let the user know there is a new message.

Perhaps I am not being clear. Not the first time for me haha. A little module, for example, that comes with the DNNForge PM module where I can put that little module on any page and it not only shows their inbox status (# of total messages and # of new messages) but gives a pop up when a new message is present. I have this module plugged into the main page, forums and AS. Pretty much the 3 places users go for PMs. Now if I could take the welcome center and place it as a module on any page I want I'd get the same result. Is that more clear?

Posted By Will Morgenweck on 19 Jan 2011 04:04 PM

I have often wondered why this is the requirement.

It's not a requirement. It is possible and the architecture certainly supports it, I've just never had anyone request to set it up that way and never tried it myself. Also, the original intent for the welcome center was to be a skin object that replaces the user skin object in DotNetNuke. If you look on our site, that is exactly what we have done. All we added was the small envelope icon to let the user know there is a new message.

Hey Will, it is a requirement if you want popup notifications from AS that you have messages waiting.

Hey Drew, No it is not a requirement. The only requirement is to have a custom view on a page that contains the message center control. The pop up notification is produced by the message center control. For convenience, based upon customer feedback, we embedded the message center control by default in the welcome center template. Add something like the code below to a custom view and you get your popups. The code below comes from the welcome center template.

Posted By Will Morgenweck on 21 Jan 2011 12:52 PM
Hey Drew, No it is not a requirement. The only requirement is to have a custom view on a page that contains the message center control. The pop up notification is produced by the message center control. For convenience, based upon customer feedback, we embedded the message center control by default in the welcome center template. Add something like the code below to a custom view and you get your popups. The code below comes from the welcome center template.

<active:messagecenter runat="server" id="ctlMsgCenter">
<displaytemplate>
<div class="asmsgcenter">
<ul class="aslistflat">
    <li><a class="CommandButton" href="[AS:PM:LINK]">Inbox: ([INBOXCOUNT])</a></li>
    <li><a class="CommandButton" href="[AS:PM:NOTIFICATIONS]">Alerts: ([NOTIFYCOUNT])</a></li>
</ul>
</div>
</displaytemplate>
</active:messagecenter>

So this would go into my skin .css file then Will? Sorry more a sys admin then developer.

Peter,
You need to look at some of the documentation for creating custom views in Active Social. You will create a custom view using the code above. Then you will be able to Active Social to a page and choose the new custom view.

Ahh but from what I am reading in the KB this is limited to AS pages. Does not help if I want PM notification popups on the main page for example.

Putting this custom view on a page effectively makes that page "AS enabled", if you will. You don't need any other AS views/controls on that page (although you may, if you choose).

Clearly I got to figure out how to do this 'custom view' never had to deal with it before. But thanks for the info :)

Lost in this thread is a simple thought: all of the AS modules should have this inherently built-in. A simple toggle within module settings should allow me to say: please display inbox notices. This seems to be a no-brainer to me given the nature of what AS is. I don't see a custom view being required. I don't think my thoughts are off-base on this one. It is a great feature, many of my users like it. Simple: keep them happy outta-da-box.  ;)