Trying to migrate to html with a big site

Beta
#1

Hi Charlie,

i uploaded the beta to staging site (big wpml site) and tried to migrate to html as the docs say.

when i turn on the store content as HTML and then piush the button Migrate, i immediately see this message:

{“readyState”:4,“responseText”:“

Es gab einen kritischen Fehler auf deiner Website.

<a href=“https://wordpress.org/documentation/article/faq-troubleshooting/”>Erfahre mehr über die Problembehandlung in WordPress.

”,“status”:500,“statusText”:“error”}

anything i can try?
Thanks in advance

#2

When you turn on WP_DEBUG what message do you receive? It will also show the error in the browser dev tools.

#3

Hi Charlie,
sorry for the delay. I attached the logfile in secure note. Just click the blue button on top right to download the file.
If you need access to staging let me know.

thank you

#4

hi charlie,
i found the issue. I had enabled the maintenance mode serve side. so only my ip was able to access the site.
Now i diosabled the maintenance mode and it started migrating and the migration was sucessfull.
(Why is that, when maintenance mode is on i cant migrate?)

After the Migration the frontend changed => i then opened the homesite in cornerstone => in cornerstone all looked good => resaved the frontpage and now it also looked good again in frontend.

It is a really Big site in 5 languages with a lot of pages. it would take a lot of time to resave every page. Is that a bug or the normal behaviour?

thanks again

#5

When I’ve seen sites in maintenance mode I’m usually not even able to access the dashboard. Was that some hosting maintenance mode or some setting you had in your dashboard?

It’s probably a bug. It should migrate and work the same as when in shortcodes. Without needing to save manually. Do you have any caching plugins on that site?

#6

It was a hosting maintanance mode => only my ip was able to access the site.
I disabled the hosting maintanance mode and enabled Under construction Plugin from theme.co and it worked.

No caching on that site, and also no caching server side for the staging site.

I will test further tomorrow if i find anything else.

#7

I found out that the problem with styling is when i used element css.
i hope that helps.

#8

Does clearing the Cornerstone cache help? Have a great weekend.