I have added a tutorial on how to add a search engine to AWStats using Bing as an example.
How to add a search engine to AWStats
Doug
I have added a tutorial on how to add a search engine to AWStats using Bing as an example.
How to add a search engine to AWStats
Doug
AWStats v6.9 has been out since end of December, 2008. I like to wait a while before upgrading because sometimes there are quick fixes that come out shortly after. It has been three months and no quick fixes so it was time to upgrade. Upgrading was easy: all I did was overwrite the old files with the new ones by copying the entire directory on top of the old one (after making a backup). A few tools had to be copied to the wwwroot/cgi-bin directory but other than that the upgrade went well.
I ran the weekly update and all went well. The geoip country and city plug-ins work better than 6.8.
For several weeks Windows update has been trying to install a security update for Visual Studio 2005. And for several weeks, failing. I tried to repair .net 2.0, which went fine, and VS 2005 which did not. The error was that vs_setup.msi could not be run. Finally found some clues searching the internet:
1. go to HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts C7F704DE975BCC419DF58C55E80E468
2. In Patches subkey clear the entry for Patches which is type REG_MULTI_SZ.
Now the repair of Visual Studio 2005 went fine and the update was successfully installed.
Doug
We finally got Expression Web 2 installed and working (that is another story). One of the biggest reasons in switching to EW 2 is the ability to handle PHP (though we still do ASP.NET). Installing PHP directions is found in EW 2 help under PHP.
In setting up PHP preview, a few problems surfaced:
As I find other PHP-related problems and observations, I will post them here.
Doug
I went to install Expression Web but found out it would not install over the beta version. But the beta version would not uninstall – it was corrupt. Searching the web only found other people with the same dilemma…so I thought I’d try a fix myself.
Note that I did -not- have Office 2007 or Office 2007 beta installed – just Expression Web beta 1 – so I’m not sure how this fix will work if you have Office 2007 or its beta installed.
I had Expression Web Beta 1 but I believe the fix will be similar to the CPT 1 release.
*** Make sure to back up your registry before doing this! ***
1. In the %temp% directory (start > run > open then type in %temp%) search for the latest log SetupExe(..).log. Near the end is this:
Catalyst beta product conflict check failed. Office Beta product conflict is detected on the computer, productcode={30120000-0026-0000-0000-0000000FF1CE}
2. Search for the productcode in the registry and delete all the occurrences but when you find the occurrence in a subkey of:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/ CurrentVersion/Installer/UserData/
S-1-5-18/Products
you need to delete the entire subkey. In my case their were 4 of them that started with 000021 and contained the productcode in question.
For example:
In …/Products there were 4 keys starting with 000021…. Each key had the productcode mentioned above in the InstallProperties subkey. Delete the entire key starting with 000021… not just the InstallProperties subkey.
There were two places that had these 4 keys to be deleted.
Then delete all occurrences of the productcode in the registry…most were in the Uninstall key.
What this whole exercise does is to delete references to Expression Web beta and Office 2007 beta.
Hopefully these instructions make sense. I did not record every place that I deleted the productcode…I wasn’t sure it would work…but it did.
Doug