Staging with Woocommerce and Siteground - wordpress

I have a problem. I need to do some updates for a client and the website use Woocommerce, the hosting platform is Siteground. Someone told me that I need to use stages for updates/ development. But I don't know how to manage the situation because I have an example..
I'm making the stage using the Siteground tools, and now I have a copy of the entire shop. I'm working on updates for 5 days for example. After this 5 days, everything looks great and I want to do "Push to live" but surprise, in this time the production got another 50 orders. What can I do to not override this orders, new users, etc.
I know that I can use the the Advanced Push and to check the tables that I want to update, but we all know how wordpress works, that all the things are actually stored in wp_posts. How to deal with that?
A strange thing is that I've made the stage and right after I've checked if are some updates to do using Advanced Push and got to do update for this tables
wp_termmeta
wp_redirection_logs
wp_posts
wp_redirection_404
wp_term_relationships
wp_terms
wp_commentmeta
wp_options
wp_comments
wp_users
wp_redirection_items
wp_term_taxonomy
wp_usermeta
wpk_postmeta

The approach to take will purely depend on what updates were made to the site. If purely plugins/themes were updated you can copy over the files from the staging site to the live site.
However if a more in-depth change was made to the site such as content, structure, etc then an approach, using a plugin, similar to in the link below can be taken:
https://wp-staging.com/migrate-wordpress-staging-site-to-production-site/

Related

I have a backup of the Wordpress folder but not the SQL database, is it possible for me to recover the website for local use?

I have a backup of the entire Wordpress folder of one of my old websites but, unfortunately, I forgot to also make a backup of the database for it. It's been years since the website expired so there's no way I can get the SQL file that way, and both Wayback Machine and Google don't seem to have any caches left of it (a tutorial I saw mentioned trying that way).
Is it still possible for me to get the website working for local use?
Yes and no, depending on what you are willing to do.
Is it still possible for me to get the website working for local use? No
If you have no database you will not have access to the Posts, Pages, Users, Options and all of the meta.
Is it still possible for me to get the website working for local use? Yes
If you create all of the database entries again to your satisfaction. You will still have all of the images you can re-upload to recreate the database entries for images. Then just re-create all of the pages and users as needed. Plugins may need to be disabled/reactivated/reinstalled and configured as well as your theme settings.
Try https://web.archive.org/ , you might be in luck there. Without sqldump its not much to do. If you had a cache plugin active, check if you have any snapshots.

Using same database for multiple wordpress websites

I want to use the same database for multiple WordPress sites. The products should be same in both sites but front end differs.
Is there any way i can accomplish this? So that i can save fhe database of products and just use to create another site without wasting time to upload products.
I don't think it is possible to use One Database for Multiple Wordpress setup on different Domains because Wordpress Database stores SITE URL in wp_options and wp_posts frequently.
And there is no option to switch SITE URL dynamically.
One option I can think of is running a script that executed daily in CRON, script clones everything from one database to another AND also update URLs in the database dynamically.
That should copy all the content you add in one database to another.
Let me know if you have more concerns. Thanks.
This wouldn't be possible unless you were to change the prefix of the tables for one WP install, but then you still wouldn't have the same content on both sites.
Maybe try out WordPress Multisites, I think this might help you in this instance.

Downloaded sql file/db as backup, found gibberish that can't be found in wordpress pages or posts. What to do?

I made a couple of wordpress database backups before making some adjustments on a site. Found some new problems, so I checked my work to see if a new problem was something I'd done, or if it wasn't correctly handled on the original site...I did this by opening up the original backup sql file and searching for a word, and saw a whole bunch of inappropriate verbiage in the file. Stuff that has nothing to do with the content of the website. Possibly inflammatory sentences involving politics which I know the site owners would never have put there (they are a retail site).
I ran some checks to see whether or not the site had MalWare, and the software didn't see any warnings.
I checked the pages, posts, and comments on the site, and do not see anything from the sql files on the site itself. The site owners had mentioned in passing that they'd had a site break-in previously. I assumed it had been cleaned up.
Does the stuff that I found in their sql file prove that it hasn't been cleaned up?
What are the best steps to remove that material without breaking the site?
And does this material being in the db negatively impacted their SEO?
Your thoughts and advice much appreciated.
1) Does the stuff that I found in their sql file prove that it hasn't been cleaned up?
Not necessarily. The owners may have overwritten posts or restored previous revisions and the bad content you are seeing may actually be in post revisions - which would not be visible.
To verify this: Login to your hosting account, open phpmyadmin, select the database for this website, click the SQL tab and run this query:
SELECT `ID`, `post_content` FROM `wp_posts` WHERE `post_type` = "revision"
If you see the bad content in the results then what you saw in the SQL file was likely from the revisions.
2) What are the best steps to remove that material without breaking the site?
There are plugins to delete old revisions. See here: https://wordpress.org/plugins/search/delete+revisions/ or (if you are comfortable with doing this) you can directly delete them from the database. Just make sure you backup first!
3) And does this material being in the db negatively impacted their SEO?
Old revisions should not be crawled by search engines and should have no impact on SEO.

How to create database and use it in wordpress dashboard

i am newbie to wordpress.I just created a free blog in Wordpress.I want to know how to create Database in it and use it. Any links to good tutorial will be great.Thanks in advance.
WordPress itself uses a MySQL database to store (among other things) post content and meta, users, info about plugins, etc.
In terms of creating a separate database from the one that's in WordPress itself, the question you're asking itself makes me very hesitant to think that you should. You'd be dealing with passwords, permissions, and a whole range of very easy to screw up settings that probably aren't worth playing with if you're new to WordPress.
If you wanted to use the database in WordPress itself and have the ability to write queries or create tables, you could look at any number of SQL plugins (eg http://wordpress.org/plugins/sql-executioner/ or https://wordpress.org/plugins/elisqlreports/) that would allow you to query tables in the WordPress database.... I don't recall if the existing plugins would allow you to create/modify tables, but phpMyAdmin or terminal would be just fine for that if not.
Since you're new, let me ***strongly*** encourage you not to modify/delete the default tables in WordPress, especially not on a live site.
Best of luck

How to delete all plugin references in database?

How does one completely remove a plugin from WordPress?
I have deleted the plugin via WordPress admin and then reinstalled, problem persists.
I see 8 records in cmsoptions table referencing the offending plugin. Since WP Admin drags to a grinding crawl with the plugin active, and for weeks the plugin was working just fine, I have to conclude that the problem exists due to the plugin references in the DB.
If anyone has the inside word on completely obliterating a plugin from WP, please do share.
The the options API (http://codex.wordpress.org/Options_API) is open to the plugin to store whatever data it wishes (under whatever name it wishes). You'd have to search the plugin code to see what it is storing (and how) in order to get rid of the offending data.
The issue isn't with WordPress, it's with the plugin. WordPress is a framework and can't take responsibility for whatever gets built on top of it (ie plugins). It's like blaming a hammer for a poorly built house.

Resources