Instead of rendering the home page, it displays:
“504 Gateway Time-out”
“nginx”
In Settings > General of both WordPress https sites this has happened to me,
the site URLs are the same to the real URLs, including https.
After migration of WordPress to another server, SiteOrigin CSS breaks
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi manos
Thanks for reaching out.
I don’t think a mismatched URL’s would lead to a gateway time-out, thanks for checking that though. There isn’t a specific action I can recommend to resolve this issue, there is however a list of troubleshooting steps you can try to resolve. Please, see the steps outlined in the following post https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-504-gateway-timeout-error-in-wordpress/.
Perhaps it is not understandable. SIteOrigin CSS did function well in both sites I have been handling. After migrating, it broke, meaning that the WYSIWYG editor does not respond. Nothing has changed in my local pc and logging in from another does not solve any issue. The two examples are more than half a year distant in between and while the one site was broken, the other did function well with SiteOrigin CSS. There seems to be a database signature bug in SiteOrigin CSS.
Hi manos
Thanks for the update, I understand the question. At the moment, I’m not aware of a specific SiteOrigin CSS issue that would arise after a server migration. Without further information, my advice is to troubleshoot the 504 error, that’ll hopefully lead you to the cause. Have you tried any of the steps in the article I sent? For example, the 6th step in the article is to optimize the database via phpMyAdmin or a plugin like WP-Sweep.
It sounds like you’ve worked through some of the steps. If you could please, let me know if you completed step 6 and also step 7. In this case, step 7 would be to temporarily deactivate all plugins except for SiteOrigin CSS and then check to see if the issue persists. The test should only take a minute or two.
Disabling plugins does not help at all.
Changing theme does. All css code is gone by changing theme.
Turning back to productive theme restores the problem (and css code re-appears).
May I remind that the theme(s) had worked well with SiteOrigin CSS before migration.
How did you migrate sites? What method was used?
WP-Sweep for cleanup did not help
Understood. How was the migration done?
The first site was migrated by the provider. We have no control on it, we have to send email for every change on hosting. They did change server.
The second site is in the public school network. They let us use a temporary page, having added an “”-new”” in the domain. SiteOrigin CSS worked well there. As soon as we noticed them that the site was ready, they removed the “-new” = the initial domain was assigned to the new site and SiteOrigin CSS stopped functioning.
Are the original sites and databases still available?
We’re attempting to offer advice from a position with very little information but it would appear that the manner in which the migration was done isn’t suitable. I haven’t personally encountered this with SiteOrigin CSS but we have seen Page Builder sites being migrated via methods that don’t support serialization which breaks Page Builder. That’s just an example.
A solution might be to make a clone of the theme with different naming in order to fool the DB and make it work.
I would prefer to remove the memory of SiteOrigin CSS from the DB and re-install it.
Hi Manos,
I’ve read over your posts and Andrew is correct; this issue you’re facing is caused by the migration attempt which has failed.
Unfortunately, there are a number of reasons why a migration can fail, and all of them are really tricky to fix. I personally recommend not debugging the migration attempt and instead recommend asking your hosting provider to attempt migration again. If they refuse, or that second migration attempt also fails, I recommend manually doing one using a plugin like All-in-One WP Migration.
I know this isn’t ideal, but migrations can be very tricky and prone to errors. These sorts of errors aren’t something we’re able to directly fix so you’ll need to work closely with your hosting provider to proceed.
Kind regards,
Alex
Thank you. In fact All-in-One WP Migration from our side has been already used in the first site as the migration from the provider resulted to a half broken site. If you cannot tell where in the DB are the SiteOrigin CSS settings to remove, the most promising solution seems to be the cloning of the theme under a different name, as any theme change restores the functionality. I think I ‘ll give it a try.
Hi Manos,
SiteOrigin CSS stores its CSS in the database in the wp_options (WP may be different if you’re using a non-standard prefix) table under siteorigin_custom_css[theme-slug]. Replace theme-slug with the slug of your theme. The slug is the directory the theme is stored in so for example, Vantage, is stored in the vantage directory and SiteOrigin North is stored in the siteorigin-north directory.