Tim Codex

You can try to go to Settings / Permalink to check link structure and you have to click Save button at least one time (YOU HAVE TO) and WordPress will generate access file on the server to fix the problem. That happened to me, hope it will be same for you.

You can export and import the content from the current domain to the new one and you will have the same all comments + posts.

You should better keep the current domain working for a while so you can redirect all readers from current domain to new domain using JavaScript or plugin so your readers from current sites can aware the new domain.

Remember add canonical meta tags to all your posts on current domain target to new domain so crawlers from search engine will index the posts on new domain instead.

GA will not be affected if your GA account is a hosted account.

You will have no problem with JetPack.

Many hosting provider automatic installer will add security plugin which is cause the error. Just follow the plugin requires to log into dashboard first, after that, you can disable one by one plugin to double check.

In case you are not familiar with this, you can request support from your hosting provider.

Seem you have no any posts in 2017/10 and also no post in category id 60. Also need to check your permalink settings to make sure your link structure is right.

You can use JavaScript or plugins to redirect your readers from .com to .org.

Please double check if you are not installing on an already installed WordPress folder. Also please make sure your database information is right.

Did you purchase a hosting plan? Most of hosting providers now have automatic application to install WordPress for you.

You install using auto application or manually?

You should set this ticket as resolved so people will not waste the time to read the comment again and again. Thank you.

Yes. You need to change theme version in style.css and add release notes to readme.txt then submitting it again at: https://www.ads-software.com/themes/getting-started/

Actually, the readme.txt will not affect reviewers but that’s standard, when you release new things, you must have release notes for it.

Aha. After reading your comment, I switched back to the plugin detail and realize the same thing as you.

I think they should better have a bold border for the preview image.

Excellent idea Andrew. It’s better if the core can also remember the last time editor which users used so it will also show that editor for them when creating new posts. I also suggest integrate a fast way to switch between editors in case that Classic Editor workflow is faster.

Can you provide more detail? It’s also better if you have screenshot or example URL.

As I understand, you need a fast way to switch between editors (example press CTRL+SHIFT+E to switch), right?

I also hope they can integrate that feature into Classic Editor plugin, or better including in core. That will save us a lot of time.

If disable Classic Editor not help so it’s not in the plugin support scope. Can you provide more detail like Screenshots?