Earlier when upgrading a WordPress site that is running on a CentOS Linux server I needed to quickly backup the entire site to then perform an upgrade of the core WordPress installation. There are multiple directories located beneath the primary site folder that I didn’t need to backup including some caching directories as well as a database backup directory since all of those directories are not required to restore the site in case of an issue during the WP upgrade. Use the information below to create a tar archive while excluding multiple sub directories.
Last night I was creating some manual backups from a server including an entire web sites data files as well as the databases associated with that same web site. I decided to use the tar archiving utility to pack all of the files from the web site into a single file so it could be downloaded and stored easily. Use the information below to exclude a sub directory when creating a tar archive.
Installing a bunch of packages on a CentOS server today I ran into an issue where the CentOS Base mirror I was using was incredibly slow. First I checked to make sure that the yum-fastestmirror plugin was installed which it was. Next I attempted to clear the fastest mirror plugin cache by running “yum clean plugins” but I ended up with the same exact CentOS Base mirror yet again. Follow the directions below to disable a specific mirror from yum.
A WordPress site I recently helped develop had an issue related to the header navigation. From a previous request certain pages had been excluded from the header navigation which can be completed in the Mandigo Theme Options section. In Mandigo you can simply check any page to exclude it from the header navigation. Typically if you want to simply add it back to the navigation you remove the check and the page will show in the header navigation in the order in which you have configured it to display using the Order Attribute. In this particular case when I attempted to remove the check and then click the Mandigo Update Options button it appeared to be successful but then the check would still exist in check box I had just removed it from. Below I describe the issue, how I realized what the conflict was, and how to resolve the problem.
If you are using Google Analytics for web analytics it can be beneficial to exclude certain addresses to provide a more accurate view of traffic to the site. There are numerous reasons that excluding IP’s from the analytics statistics such as if it is a personal site that doesn’t do a lot of traffic and you are working on all the time from home the analytics results might not provide a real world view of what other visitors view the most. Another example might be if it’s a corporate web site that numerous developers, QA personal, and others employees are visiting from the same address space it could skew the analytics results because of such a high concentration of traffic from one IP address or subnet. One of the great reasons for reviewing the web analytics data provided by Google Analytics is to see what pages customers view or what region your customers are from. This type of data can help prioritize the areas of the site that should be worked on the most or what content provides the best return on investment and if the data includes your own traffic it might not provide accurate data for you to review.