Contacts in Android not Saving or Syncing Properly

I recently had difficulty syncronizing my contacts between Google and my Android tablet. The symptoms were actually pretty strange. I could change contacts, I could add them in Google and they would show up on my tablet. But, contacts created on the tablet would not only never make it to Google, but they wouldn’t even save on the tablet.

After some work and searching around, I found the solution was to reset the Android contact database.


After backing up your contacts to a removable storage device, follow this procedure:

From your main Android apps screen, click your menu button and select “settings”.

Click on “Accounts & sync” and uncheck “background sync”.

Return to your “settings” page (click the back key) and click “Applications”.

Select “Manage Applications” then choose “ALL”.

Find the “Contacts Storage” application and open it.

Click the “clear data” button.

Return to the main Android apps screen, click “menu” then select “settings” again.

Click on “Accounts & sync” and recheck “background sync”.

Then reload contacts from backup and select Google to syncronize with.

This resolved my issues, hopefully it may help someone else as well! Comments or questions? List them below!

MOD_FCGID ignores directives in VirtualHost block

Hopefully the following will help some people from wasting a lot of time chasing their tail.

There are many “How-To” documents describing how to use mod_fcgid in Apache with PHP and almost all of them are absolutely WRONG!

If you run across a document which directs you to place process limiting directives for mod_fcgid in the <VirtualHost> block, don’t listen to it. Although the documentation for mod_fcgid says you can place these directives there (up until version 2.3.2), you need to be aware that they will be ignored!

Here’s a note from the latest and greatest readme:

Some directives which could be placed inside <VirtualHost> but were
ignored before now result in configuration errors. As before, these
directives must be set at global scope to have the desired effect.
(emphasis added)

If you are attempting to use any of these directives, you MUST use them in a global scope (which means they can NOT be set per virtual host even though the documentation says they are allowable in that context).

The following is a list of previously ignored – now causing an error if placed in VirtualHost – directives for mod_fcgid:

FcgidBusyScanInterval, FcgidBusyTimeout, FcgidMaxProcessesPerClass, FcgidDefaultMinProcessCount, FcgidErrorScanInterval, FcgidIdleScanInterval, FcgidIdleTimeout, FcgidMaxProcesses, FcgidFixPathinfo, FcgidProcessLifetime, FcgidProcessTableFile, FcgidIPCDir, FcgidSpawnScore, FcgidSpawnScoreUpLimit, FcgidTerminationScore, FcgidTimeScore, and FcgidZombieScanInterval

If you are having trouble with your MaxProcesses, ProcessLifetime, MaxProcessesPerClass or MinProcessCount being ignored, try moving them to the global context.

Google Blacklisting WordPress Websites over Old Vulnerability

Keeping your software updated is part of keeping your website secure. Most sites are hacked using old vulnerabilities that simply haven’t been fixed yet.

The recent spike in malware (bad software) infecting thousands of WordPress websites is a case in point.

The fix has been out for some time, but many website owners have not made the required changes.

If your site has been blocked – or if your site has not YET been blocked and you would like to keep it that way, email us. We offer affordable rates for WordPress Support to deal with your WordPress problems.

Sites who have not been compromised can be innoculated for as little as $50! That’s a small price to pay for a little peace of mind. If your WordPress site uses TimThumb, email us or call us at (586)779-3242 about making sure it is up to date so you don’t find your site blacklisted by Google!