Replies to This Discussion

Permalink Reply by JenSocial on July 2, 2013 at 10:13pm

It appears you are asking how to do this in Ning 2.0, so I will change the category to Ning 2.0.

For Ning 2.0, unfortunately you can't change the header or masthead with CSS. It takes custom script in the Custom Code Box. We will be able to change this in Ning 3.0 quite easily, once Ning adds a CSS selector ID for the body tag of the home page.

Best,

Jen

• ▶ Reply

Permalink Reply by Matthew Smith on July 2, 2013 at 10:51pm

Thanks Jen!  When will we all get converted to Ning 3.0?  

• ▶ Reply

Permalink Reply by JenSocial on July 3, 2013 at 11:55am

Hi Matthew,

We need to move over to Ning 3.0, when Ning has the import tool ready so we can move all members and content. Ning has forecast the following timeline:

Ning 2.0 to 3.0 Upgrade Process

A tool for Ning 2.0 Networks to import members and content to Ning 3.0. (It will not be possible to transfer subdomains at the time of initial release.)

Managed Beta in September
Full release in October

http://creators.ning.com/forum/topics/upcoming-ning-releases-and-ro...

Ning 2.0 to 3.0 Upgrade Process

Our back-end engineering team has been hard at work developing the infrastructure to import content and members from a Ning 2.0 Network to a Ning 3.0 Network. Interested NCs should be able to upgrade their Ning 2.0 Networks in a process closely managed by Ning in September. Note: it will not be possible to transfer a network subdomain at the time of this initial release (see this comment for further explanation).

Clarification of the initial Ning 2.0 to 3.0 Import Process

Development of a seamless import process is complex and involves building multiple tools.  We know many NCs are eager to import their Ning 2.0 Networks to Ning 3.0, so we wanted to release an import process as soon as possible.  This initial process will be most suited for NCs using custom domains.  We will not be able to transfer subdomains yet from a Ning 2.0 Network to a Ning 3.0 Network.  We hope to develop this capability late this year.  It’s quite complex, so we aren’t able to set a release date yet.

What does this mean?  In the initial import process, an NC with a Ning 2.0 Network will first create a new Ning 3.0 Network (they can use the Sandbox Network they’re already experimenting with).  Because two networks can’t share the same Ning subdomain (subdomain.ning.com), this new Ning 3.0 Network will have a different subdomain.  The NC will customize the design and layout of their new Ning 3.0 Network.  When they are ready, they will contact Ning Advocacy and we will assist them with importing all members and content from their Ning 2.0 Network to their new Ning 3.0 Network.  During this process, the Ning 2.0 Network will be unaffected – members will continue to post and comment.  When all members and content have been imported to the new Ning 3.0 Network, the NC will simply change the DNS settings for their custom domain and map it to their new Ning 3.0 Network.  Members will then start seeing the new network, including their profile and all of their content – and they can continue posting and commenting where they left off.

We eventually plan to release an import process that is more seamless.  We envision an NC will be able to choose “standard” import.  After they customize the design and layout of their new Ning 3.0 Network, they will simply push a button and Ning will automatically import all members and content to the new network and switch the subdomain from their Ning 2.0 Network.

• ▶ Reply