schmecktes

Hi,

my fault. Found it and it works fine!

Great & Thanks

Cool!!!

Hi @corylamleorg,

tried it. Can′t find a legacy check on step 2 and not on step 1-4 at the installer routine…?

Thanks for your help,

Sven

YEAH!!! That′s it!

To comment out this code lines was definive necessary! Before in google search console there was a 503 error.

After changing the code in the wp-maintenance-mode.php and new manual indexing with google it succeed a few minutes later.

Thank you very much!

PS. Maybe you include this knowledge in your plugin for other customers, that do the same with maintance mode as a temporary construction site…

One more question please. I′ve done it like you wrote but the google index doesn′t work. I have wait for 2-3 weeks now.

With this preferences it would work? The maintance page would be included in the search enginge? Are there maybe other preferences, that causes index issues? WordPress …

Thanks

Ah ok! That was the mistake. I′ll try it. Thanks

Hi Cory,

Thanks for your input. At the moment, the website is running. (Website files are installed at the hosting package and the database comes from another provider with 5.6)

Sorry, I can′t comprehend your suggested solution because I can′t find the legacy check. I have a german version and searched all the options and preferences.

On step 2 (Scan) I have Server setups, archive options and a database overview. Is this a pro feature?

Thanks Sven

PS. I′ve read that maybe it is possible to downgrade per mysqldump. On localhost the info is red and not available:

Mysqldump was not found at its default location or the location provided. Please enter a custom path to a valid location where mysqldump can run. If the problem persist contact your host or server administrator…

Thanks with 5 *****

Hi George,

thanks for your fast reply. I think I understand the facts. To let the robots scrawl only the maintance page with infos on it and not the rest of the website:

1. index, follow & 2. Bypass für Such-Bots: no

3. Using the maintance site as a coming soon page is not the best practice, but it works probably for one month.

Correct? Thanks

PS. I saw it here in a german webdesign blog. Using a migrate plugin for that issue as the best of all possibilities.

He suggests quite the same as the last link and in the end he highly recommends the changing of the database using a migrate plugin (duplicator or migrate DB) that can retype the server paths. Steps of Die WordPress-Adresse über die Datenbank ?ndern:
1) Find out the absolute path
2) Find and replace
3) ZIP
4) import it in PHPmyadmin

So I use duplicator for migration. Can I solve it with that? Do you see now my problem and maybe it′s possible with duplicator? Do you have experience with that issue?

Thanks!

Hi Cory,

Thanks for the links. Yes it goes more in that issue. But we have no staging site and no entry to the hoster backend. We work together with another agency, that hosts the domain in this case. They switch from the installation webspace to the target domain. After that we have the problem. It is more like this: URL changing
So I thought, maybe I can solve it before with the preferences or help of duplicator. Thanks

Hi Cory,

thanks for your answer. I think it’s more the second paragraf. Maybe I describe this confusing thing in short steps.
– upload of the duplicator package to the installion webspace.
– Website works on this address
– the domain is switched from the old website (webspace) to the new of the same hoster.
– by typing of the URL the visitor gets the new website but the installation webspace in the browser URL. Not the wished domain

My question is, if I can solve it during the installation with the preferences of duplicator. I guess not?! And afterwords propably not too?
Thanks!

Old site: domain.com

Where is it possible to send some details / credentials in a private mode?

Thanks