Skip to main content
Theme

How-to

Check pages as a signed-in person

The site check requests every page on both instances. On its own it sees what an anonymous visitor sees, and much of a site can sit behind a sign-in. A test account lets the check see the rest.

The old site is usually the live site. A test account you make there is a real account on a live site: it can sign in, it may count as a member, and it may be sent the site's emails. Make it with an email address you control, give it the least access that still shows the pages you need to check, and make it an ordinary person, not an administrator. The load copies it to the new instance like everyone else. When the migration is closed, remove it from the old site and the new one.
  1. On the source, create an account for each kind of person whose pages matter: a member, a staff member. Use a real sign-in, not an administrator's.
  2. On the plan, under Signed-in checks, add each one: who it is, its email and password, and the path of the site's sign-in page. The plan suggests the one it found in the site's code. If the path you give does not open a sign-in form, the check looks for it: the pages the old site says sign people in, then where the site sends someone who is not signed in, following the site's own redirects but never to another address. An Insites v4 site signs people in at /admin/login.
  3. Approve the plan and load. After the load the account signs in on both instances through the site's own sign-in page, and every page is compared as it sees them.

Because the account signs in on the destination with the password it has on the source, this also proves its password was copied. If it signs in on the source but not on the destination, the check says so. If the new site sends people to sign in somewhere else, such as Insites Console, the check cannot sign in there with an email and password, and says the signed-in pages were not checked rather than failing them.

On Verify, a test account reads one of three ways. Signed in. 23 of 24 pages match; 1 could not be checked is a pass: the old site did not answer that page (a 503, for example), so it could not be compared, and it is named so you can look. It is not a difference and needs nothing from you. Could not sign in means the email, password or sign-in page needs fixing: use Edit credentials, then Check this account again. Signed in. 1 page differs (or however many) means the sign-in worked, so the credentials are right, and the page it names answers differently on the new site. Open that page on both sites and fix it, or accept the difference with a reason in the signed-in Pages answer the same check.

Added an account after the load? Open Verify and click Check again. Removed one, or want to add one now? Open Verify, then Things that need you: if pages sit behind a sign-in and no test account checks them, the Add the test account form is there. Removing a test account also removes its signed-in check, so a failed check no longer counts against the result.

Pages the check never opens

Some pages act on the account the moment they are opened: signing out, resetting or changing a password, unsubscribing, deleting or closing an account, confirming or verifying an email, or sending a message again. On some sites, opening the password reset page while signed in emails the member a reset link. The tool never opens these pages, on the old site or the new one, signed in or not, and never photographs them. It knows them by their address, by their file name, and by code that ends a session, resets a password or sends an email. Each one is listed as not checked: account action page, so the page count still shows it. Open them yourself if you need to check them.

Pages that may change data

A page can also write records each time it is opened. A test page that creates a company with dummy data is one example. The tool never opens a page like this on the old site or the new one, in any check, and never photographs it, because opening it would add records to both sites. It finds them in two ways. The first is the name: a short address or file name with a word such as test, controller, debug, sandbox, seed or demo-data. The second is the page's code: a graphql mutation, a call to a function whose name says create, update or delete, or a record create, update or delete field. The plan lists each page with its reason. After a check, one To do job named Pages not opened because they may change data: review and delete or keep lists them again. These pages count as not checked, never as failed. Read each page's code on the old site. Delete it if it is an old test. Keep it if it is a real page, and check it by eye.

What happens to the password

It is encrypted like the admin keys and never shown again. It is kept like the instances' keys: for as long as the migration needs it, until you close the migration or remove the test account, so checking again weeks later works without adding it again. How long a key is kept.

If the tool no longer holds the password when the checks run, they stop and name the test account. Either go to Verify, then Things that need you, fill in the form there and click Add the test account: the account signs in on the old site and its pages are checked on both sites straight away, without running the whole verification again. Or, on the plan under Signed-in checks, remove the test account and add it again, then check again. Nothing the migration has done is lost either way. The password is removed when you remove the test account or close the migration. Remove the test accounts from the source and the destination when you are done.