jb317

update: I think I resolved this. Under settings, appearance, I set the width from auto to a fixed width.

The site it testing better now.

Excellent. Thank you.

Same here. Following for updates.

@jreeve0805 Perfect! Thanks for this. I also use Brave. Just tried Chrome and it worked. Months later and mailchimp was still not able to figure this out.

Thank you for the reply.

That setting was ON.

I checked the same setting in my Async JavaScript plugin. That was set to include JQuery. I turned it off, and it seems to have resolved.

Thank you again.

@sunnyoz Did you ever get this resolved? I am facing the exact same issue.

I already had uploaded the backup database file the other day.

What I did today was to change the prefix of the staging database manually to a new one, then updated the wp config. I also updated the options and user meta tables to reflect the new prefix.

All seems to be working.

How can I prevent this from happening again?

Thank you for the reply.

This sounds very risky to me (though, it may not be).

What happens if I just leave the site as it is now? Will it continue to work and function as normal? Is there long term harm to operating this way?

The prefix in the config was wp_. However, in order to get me back online with an incredibly broken site, my host had to change some pre-fixes in the database and also make the prefix in the config to wpstg0_ .

Once that was done, I was able to access admin again. My site was wrecked!!!!!!! Thankfully, THANK GOD, I was able to uses the plugin to restore from the next previous backup. This fixed my site.

I cannot tell you what a disaster yesterday was because of this. I lost an entire day of my life because of this, trying to get it fixed, along with lost revenue from the day.

So, right now, I see tables in my DB with prefix wp_ and tables with wpstg0_ . The config file is still set to wpstg0_ . I have no idea how to fix the entire DB to be the proper wp_, nor if doing so will break everything again. At this point, I am terrified to change anything.

I am not sure which log file you want at this point. I just want to know why my database prefix was changed to wpstg0_ (which are clone or staging files, from my googling). How can I get back to everything being wp_, without breaking anything, and preventing this from ever happening to me or anybody else ever again.

I figured out the issue, but don’t know how it happened or how to fix it. Some of the database table prefix after restore are: wpstg0_ instead of wp_ .

And yes, the backups were made by Updraft. Here is another guy with the same issue last year: https://updraftplus.com/forums/topic/database-restore-sql-syntax-error/

Please advise.

• This reply was modified 5 years, 3 months ago by jb317.

Thanks for the reply. I’m sure it is something similar to the other problem that you mentioned.

It would be super if somebody from W3 would actually reply, however. Does anybody from the team monitor these forums?

I just noticed the very same issue. No data saved, but consent shown when the email is searched.

I’m following along for a solution.

Thank you.

Yes, that was helpful. Thank you!

Same problem for me. Colored squares with no icons.

I’m having same issue as others. As was stated, adding an email address to the from field fixed it.

I had only mail tags in the from:

[your-name] [your-email]

This worked fine until today. So, I had to add an email address. Now my from field looks like this:

[your-name] [your-email] <[email protected]>

Obviously, “mysite” is the url of my site.