WordPress Staging and Testing of Plugins Best Practices

I don’t think there is the one correct answer. We use Git to manage versions. We have the master branch, that syncs with an online staging server, that has it’s own database. (Using the live database is kinda too hot for my taste.) Then there is the stable branch, that syncs with the live server. … Read more

Push from staging to live site?

Administrative capabilities are the essential part of the WordPress core, and while you may be able to block access to wp-admin directory and through this to the administrative UI, there are other ways to administer a WordPress site, namely XML-RPC and at some point the JSON API. The easiest approach assuming all of your plugins … Read more

production site routes to staging site after cloning

Check your production site’s wp-config.php file for one or both of these lines: define( ‘WP_HOME’, ‘https://example.com’ ); define( ‘WP_SITEURL’, ‘https://example.com’ ); …and set them as appropriate if they exist. These constants will override the settings in the database if they’re present. See Editing wp-config.php for details.

What are some tools for password protecting a staging site?

WordPress has an option to protect each page’s content using a password. That is done using the right panel just below/under the publish button. However if you want to hide the entire site and make it visible only to users who are logged-in, then you should consider using a “maintenance plugin” or a “construction plugin”, … Read more

Staging Sites: What to push through?

Siteground should be able to tell you if your sites share a DB (or it should be evident from whatever control panel they provide). That said, it’s generally not advisable to mess with the DB of a live site. Make your changes and configure your plugins on stage, then when you’re happy, replicate that work … Read more

Redirect to another page using contact form 7? [closed]

Redirect to another page using contact form 7? [closed]

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)