Friday, March 21, 2014

The Forum is Moving!

This article is a Catch 22 Inhibitor... On March 29 the much-beloved SQLAnywhere-forum.sybase.com will be moving to a different domain: SQLAnywhere-forum.sap.com. Graeme Perrow has posted detailed instructions about what's happening and what you should do to prepare . . . plus what you should do in case anything goes wrong.

Of course, if something goes very wrong, you won't be able to read Graeme's post (the Catch 22), so here it is (Graeme's post), on a website (this one) that isn't going anywhere . . .

What must I do to prepare for the forum migration to sap.com?


The SQL Anywhere forum will be migrating to sqlanywhere-forum.sap.com on Saturday March 29, 2014. Existing questions, answers, comments, users, reputation, etc. will be retained and aside from some cosmetic changes there will be no significant changes to the web site. Any links and bookmarks to the existing sqlanywhere-forum.sybase.com site will automatically be redirected to the new site.

On the day of the migration, both sites will be shut down for several hours while the data is moved.

Note that the new site is already up and running and you can head over there and check it out. If you have trouble logging in there please email sqlanywhere-forum-admin@sap.com and I'll try to get you fixed up. Please feel free to add questions and answers for testing purposes (there are already a few such questions there) but anything added there will be deleted when the migration happens. If you have a legitimate SQL Anywhere question for which you need a real answer, ask it here on this site.

Also, please note that email has been disabled on the new site so you cannot use the temporary login feature, and you will not receive daily digests or notifications of any kind. This is only during the beta period.

What must you do to ensure that you can log in once the migration is complete? See answer below.

Graeme Perrow

One Answer:


There is really only one thing you need to do in order to make sure that you can log in once the migration is complete, and that's to make sure your email address is correct. Click on your login name at the very top of the screen (next to the Logout, About, and FAQ links), then click "User Tools" and then "edit profile". Make sure the email address is correct, and click Update.

Note that logging into the forum through the MySybase provider will no longer be available in the new forum. Instead, you will be able to log in using your SCN (SAP Community Network) user ID. This is entirely optional. In order to make this work, you need to have an SCN account but you do not need to add a new provider. You simply have to make sure that your email address in your SCN account matches the one in your forum account.

Once the new forum is available, you have three options to log in for the first time:
  1. Use an existing OpenID provider other than Google. The cookie that the Google OpenID provider gives us is specific to the old forum URL and so it will not work in the new forum.

  2. Use the SCN to log in. This assumes that you have an SCN account and that your email address in your forum account is the same as the one in your SCN account.

  3. Use the temporary login procedure. Near the bottom of the login page, you will see "Click here if you're having trouble logging in". Click there, and then enter your email address. The system will send you an email containing a link that you can use once to log into the forum.
Once you're logged into the new forum, go to your user page by clicking on your name at the top of the page and then click "User tools" and "authentication settings". If you have a provider that begins with "https://www.google.com", click "remove" since that provider will no longer work. If you still want to use Google as a provider, you can then click "Add new provider" and then click the Google logo on the next page. If you have a provider marked "Unknown", you can remove that as well; that is for the MySybase option which is no longer available.

Graeme Perrow

Remember, this is NOT Graeme's fault.


Dilbert.com 2013-02-05

No comments: