New answers tagged

0

Seems like this is due to a conflict between the SiteGround staging process and the database storage process of a plugin we use, TagDiv Composer, that's part of a theme we use from the same developers. It all boils down to the plugin's custom HTML blocks storing all those URLs in an encoded format along with everything else, and the rewrite rules used by ...


0

You should be using relative links (/path/here) instead of absolute URI's including the schema, this way it decreases the probability of you having insecure asset issues. Then, all you'll need to have set is the home and siteurl options in wp_options table to the correct URLs. If they're hardcoded into the posts/pages, you could use wp-cli or better search ...


0

Did you check the two URLs in the wp_options table? That's where WP gets the base URL for a site. If you moved the site database from staging to live, you may have forgotten to change those values in the wp_options table.


0

If you have a multisite network, and two sites share the same theme, then any changes to that theme will be made to both. Along with users, sites on a multisite network also share themes and plugins. It's one of the primary features of a multisite network. So if you need to make a template change for only one site, you'll need to check in the template which ...


0

I've figured how to hide the editor only when the product type is selected because if i remove the support: 1) The product type is the hidden and then change the product type to another the editor doesn't appear back 2) The product type is not the hidden and then change the product type to hidden the editor dont dissappear function admin_footer() { if ...


Top 50 recent answers are included