Current status of the Ning Platform is always available on the Ning Status Blog.

Announcements from Ning

Network Accessibility Update II

It appears Tuesday’s changes had a positive impact on system availability and a significant reduction in 500 error’s.  From here on out, we'll be cleaning out the backlog of reported bugs.  Once caught up, we will address missing functionality in Ning 3.0, release new features, and restart the Ning 2.0 to Ning 3.0 migration process.  Please stay tuned for further updates!

You need to be a member of Ning Creators Network to add comments!

Join Ning Creators Network

Email me when people reply –

Replies

  • It appears that all content from my network created later than 27 October has disappeared from my network!!!

    It includes members, blog posts, discussions, events....
    Please restore it all and let me know why this happened.

    Also new blog posts created today are not going to the Last activity Feed
    Is someone else affected?

    • We began receiving 500 errors when posting a 'comment' on Saturday.  I filed a ticket - I suggest you do the same.  Seems like a server issue again.

  • Please make good on the missing and previously promised features as your #1 priority  these have been on the 'roadmap' as long as the road map has existing 

    The Ning Archiver so we can get access to our data.

  • I filed a ticket on Saturday as well due to missing content  and feeds not updating.

    • Hey Lorianne, have you received a reply yet regarding this issue? If not, let me know what your ticket number is so I can look into it for you!

      • got the reply, thanks.

  • Great news!

  • I'm have problems with nav bar when I'm on my mobile iPhone. When will this be fix? Some time it will not go to the next page.
    • Dan you should file a ticket.  They're not 'responding' to questions in the forums

    • Hey Dan, have you submitted a ticket about this? I'm happy to follow up with the team member that is investigating it and let you know what the status is. Thanks!

This reply was deleted.