Pro 6.6 Beta 1 - HTML Storage - Message for which storage engine we are using

Not sure I missed something.

I went to the settings, turned on the HTML storage and clicked migrate. This seems to take a while so I moved on with something else on another site.

The notes say clicking migrate is basically a toggle.

As there was no message when I returned to the site I’m using to test the beta, I have no clue if it was successful or not or which engine I’m using.

My question, how do we know if we are using the HTML storage or the shortcodes? Is it possible you can add something to indicate clearly which storage engine we are on?

3 Likes

I agreed a success message would be very helpful

2 Likes

And preferably a message to tell us which engine we are using.

Or just a note on the button. So the button says Migrate to HTML or Migrate to Shortcodes depending on which storage type is active

1 Like

Yeah, right now you’re left guessing.

Great ideas on making it clear what migration is going to take place. And we can certainly add a success message. If you didn’t receive any message currently, it means it was successful for clarification.

Would it be more clear if the toggle said “Storing as HTML” and “Storing as Shortcodes” conversely?

1 Like

Just something that states which engine is active. Those words sound perfect.

When trying to migrate a website (three attempts) I invariably get the message (also see screenshot):

{"readyState":4,"responseText":"<html><head><title>500 Internal Server Error</title><style>@media (prefers-color-scheme:dark){body{background-color:#000!important}}</style></head><body>\n<h2>Request Timeout</h2>\n<p>This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase 'Connection Timeout'.\n</p>\n</body></html>\n","status":500,"statusText":"error"}

The Migrate button says “Loading” until the error appears. On this particular site, the process to error takes about 8-10 minutes.

Afterwards, the screenshot shows the Migrate button back to default.

Thanks,
Christopher

It’s unfortunately going to timeout on sites with a large set of content. It’s something I’ll fix by beta3.

@whitemedia I’m not sure what you mean by layout broke though, could you start a new thread with some screenshots or a site to look at? Was that after the migration?

Thanks for testing. Have a great weekend.

Thanks Charlie.

Unfortunately, with this site, despite being on beta, as it was from last Spring, this one is getting close to going live (but I wanted to try and use the amazing masonry row settings) and I was with the client this morning. The whole layout broke, which they pointed out to me. The main issues were top and bottom margins were almost eliminated between sections. In this case, most sections are actually Parameter-based Components. There were also “shadow” buttons below one section where there were no buttons. Unfortunately I did not manage to get any screen-grabs, due to time-sensitivity.

I am not sure if the beta caused the problem in itself, or if the HTML migration attempt was the issue.

In the meanwhile, I restored the website to an All-In-One WP Migration backup, as attempting to reinstall the current live Pro version over the beta caused even more layout issues!

I will create a new staging site for this staging site and see if we can replicate this. When done, I will start a new post.

Thanks,
Christopher

1 Like

In beta2 I’m going to change the migration a bit. It really shouldn’t change any post meta in the update and hopefully that will prevent any issue you experienced. Apologies for the issue in the demo.