Ogre's blog

I had significant problems with commiting changes to svn repository for my Tangra Framework. Repository was at sourceforge.net. For ages I am using one and the same configuration and just recently I've started to have problems with commits.

Configuration:

Linux server with Debian/GNU linux + Apache + Samba (3.2.0.31-2) + PHP, etc.

Windows XP with Zend Studio, Dreamweaver, TortoiseSVN, etc.

Working copy of the framework is shared as Samba share. Yes, I know that this is not recommended but it is most convenient way -- I am able to edit files directly from my windows PC. 

After upgrade to TortoiseSVN 1.5.* all commits that added new files was showing error like:

"Commit succeeded but…"

"Error: "Error bumping revisions post-commit (details follow):"

"Error: "Can't move" (some files from .svn/props/ to .svn/prob-base/).

After above error I was unable to commit anymore -- svn was stating that I have to execute Clean Up, but when trying to do so -- clean up was failing. I had to delete whole dir that was failing, then to update parent dir in order to obtain clean working copy. That was working solution when just one dir was messed up but when I had multiple dirs with same problem -- I hade to checkout the entire trunk which tooked about 1hour (because sourcefourge svn is slow, project itself is not vary big.)

Solution:

(more…)

Ето и накратко първите впечатления от Google Chrome:

Инсталация

Бърза и лесна, няма въпроси с повишена трудност. Лошото е, че автоматично разпознава настройките на Windows-а и превключва на езика, който намери в Regional Settings.

При инсталацията импортва отметките от FF. Интересното е, че поне при мен не импортна нищо от IE, а все пак уж този Chrome е с цел да смаже IE-то.

Интерфейс

Максимално опростен, няма дори Home и Стоп бутони. Баща ми, който е на 69 години ще го хареса.

Настройки (more…)

Не мога да разбера точната причина, но днес поне 4 човека ме питаха откъде съм си свалил Google Chrome. За тяхно разочарование им отговорих, че не съм. За всички, които чак пък с такова нетърпение очакват новия броузер -- сайта му ще е наличен на: http://www.google.com/chrome след 20 часа българско време днес (02.09.2008).

Аз лично, този броузер го очаквам със смесени чувства, най-вече, защото (more…)

Днес отново имах диспут с отнесен от вихъра web дизайнер, който се опитваше да ме убеди да съм му оставел 158 килобайтовия full page background, защото иначе се развалял целия дизайн. Опитах се да му обясня най-човешки, че такова животно като full page background е единствено подходящо за неговия личен сайт, където си представя дизайнерските умения. Опитах се и да му покажа, че ако сайта получи повече content ще се появи скролбар и няма абсолютно никакъв начин неговия bg да изглежда нормално в такъв случай. Наивно очаквах, че след експеримента със скролбара пича ще се усети, че е напаравил гаф и ще измисли нещо ново, но за съжаление, както ми се е случвало и преди с други такива като него, ми излезе със следните идиотски идеи: (more…)

If you ended up here you are probably wondering how to remove annoyng "Blog archive" text from your blog post titles.

There are good news and bad news.

The bad news is that if you have blog registered at wordpress (i.e. username.wordpress.com) I can't help you.

The good news is that if you have installed wordpress package on your server or some hosting space -- removing "Blog archive" is quite easy.

FTP (or whatever method you use to upload files) to your server and go to directory wp-content/themes. Here you will fine directories for available themes. Enter the directory of your theme (probably "default/"). Here you will find a bunch of files. Open header.php for editing.

Find the line that is enclosed by <title></title> tags. On default theme that is line 7.

It looks like:

<title><?php bloginfo('name'); ?> <?php if ( is_single() ) { ?> » Blog Archive <?php } ?> <?php wp_title(); ?></title>

All you have to do is to remove "» Blog Archive" (without quotes).

Save your file. That's it.

Today, during testing of a site for a client of mine I found that for some reason $_SERVER['PATH_INFO'] is not populated although there is path_info parameters in the requested URL. Initially I suspected that fault is in my Tangra Framework for PHP but after a quick phpinfo() I found that the problem is with the PHP itselft. Examples that describe the situation:

• With requested URI http://test.myhost/index.php/_lang-en/ everything works as expected, i.e. $_SERVER['PATH_INFO'] contains /_lang-en/.
• With requested URI http://test.myhost/index.php?someparam=1/_lang-en/ $_SERVER['PATH_INFO'] is not set at all. The problem is that when you have GET parameter(s) in your URI, PATH_INFO for some reason is not populated.

The solution: (more…)