borangeatx

Thank you. I have now created a ticket for you on this. Someone will be in contact as soon as possible

Thank you!

ACP > System > Settings > Login & Registration.
Click on the registration tab.  For each registration method, make sure "Allow New Registrations" is set to no. 

Hey @Jordan Invision Please pass along my thanks to the team and congratulate them on a great job, both on running through the beta process at a good pace (unlike the app 😉) and still managing to push an enormous amount of features, fixes and improvements. It absolutely cannot be taken for granted. 
We're itching to upgrade but since we didn't take part in the beta we're still unable to do it without it being a small pain, so we're putting it off at the moment. Do you guys have a target date for a full release or will it be taken step-by-step like you did with the betas?

Check fields permissions in your database. 

Good to hear..you basically ended up with 2 sites fighting over the same database hehe.

FWIW - I solved my own issue.  I left the /forums directory on the server (with nothing in it) and that was causing all sorts of issues.  I deleted it and the site came back.

Go to the client area, click the "Support" button in the bottom right, then click on 'Email' and tap away.

 

You can check Hidden (right column) when saving the article:

Or you activate the field Publish Date in your database fields settings. This way you can set a date when the article should be published. Until it is published, it is a draft.

No. Hidden means, only administrators and those with moderator permissions can see it. It is not accessible for public, it is not included in sitemap. 

ACP > System > Support > Pick the radio button that says "Something isn't working correctly" (unless you've translated this phrase to "It's them, not you.") > Press the button to submit.

Thanks guys.  Stuart, it was another timeout issue like you said.  I got it finished by increasing the timeout to 3000.  
Appreciate all the support.

Typically this can happen when GD runs out of memory processing an image -- It doesn't have to be a huge image, but it might be a complex one. You can (if available) switch to ImageMagick for image processing or temporarily increase your PHP memory limit.

Hello again @borangeatx
I should add, to be mindful, that when performing a database backup and restore, using the terminal will always be your best option.  While you can technically perform a small backup and restore through a web interface control panel, such as Cpanel, Plesk, or DirectAdmin, to name a few. It will always be safer and more secure to do so via your terminal controls.
mysqldump --default-character-set=utf8mb4 -h [host] -u [username] -p [database_name] --set-gtid-purged=OFF --port=3306 --protocol=tcp --skip-triggers -r dump.sql Since you are at the stage where you are now importing multiple sites into your target community, it is safe to assume you are well beyond the scope of using your web browser to perform this action. Time out is something you do not wish to experience.  If you do not have access to your terminal, you should contact your web hosting service provider for assistance.
If you continue to need help, I would suggest you inquire with Community Support. There a seasoned system administrator may be able to further assist you. https://invisioncommunity.com/forums/forum/406-community-support/
 

First, I hope you have a backup of both databases—Especially your target database.  I have seen this before.  It was a good indication my database was corrupt.  Since the import did not complete, that is likely what caused the corruption.  If your importing fails, you cannot and should not proceed as if all is well.
I would suggest you restore your target database before you attempted the import.  I would then make sure to rule out the source is not corrupted and attempt a basic import on a test site. One that you have not already tried to port into previously (a clean install). If that fails, we know the issue is the source database (your WordPress).  If it completes, you could attempt to try to re-import.

Thanks guys.  Stuart, it was another timeout issue like you said.  I got it finished by increasing the timeout to 3000.  
Appreciate all the support.

Sure Ryan.  Thanks
Got it all moved over successfully.  The issue was with my .htaccess file having superfluous settings for memory limits, etc.
Thanks to all!

Sure Ryan.  Thanks
Sure Ryan, thanks

Thanks!  I’ll give it a shot!