arturmarques.com iLog Welcome Guest | Login or Register

Descobri uma extensão do Firefox, que integra uma ferramenta de blog no browser.
Comecei a escrever este post, NÃO a partir do meu habitual BlogJet , mas a partir dessa extensão, que se chama ScribeFire.

As únicas perguntas de configuração do blog são as credenciais (login/password) e a “server API URL”.

Assim as possibilidades de configuração são extremamente limitadas, como (1) não poder escolher-se o porto de comunicações e (2) não poder indicar-se o destino de binários.
As hiperligações também não são automáticas, sendo estes últimos pontos desvantagens, relativamente ao software que tenho utilizado.

Uma VANTAGEM é a inclusão de imagens, por simples copy/paste… mas é uma vantagem com restrições: acontece que a imagem copiada para o clipboard é despejada para uma directoria temporária (c:\temp, no meu caso) e depois uploaded para o blog system, sem qualquer alteração da sua origem; isto quer dizer, que o HTML vai referir um endereço do estilo “file://c:/temp/file.jpg”, que não tem validade futura, nem a partir de qualquer localização externa ao sistema de ficheiros local…

Carregando o post produzido pelo ScribeFire via BlogJet, este último trata de corrigi-lo e fazer o upload para a localização configurada para binários, pelo que acontece simbiose: sozinho, o BlogJet não permite o copy/paste directo de imagens, para posts, obrigando ao passo extra de as guardar explicitamente em ficheiro.

Por exemplo, eis a imagem de satélite de accuweather.com, para Portugal, para hoje (era dia 20070808), colhida de uma página aberta num dos tabs, no momento em que escrevia.

Instalar ScribeFire (ou fazer right-click, guardar o ficheiro .xpi no sistema de ficheiros local, depois fazer file/open a partir do Firefox).

Upgrading Wordpress on IIS 5 is very easy: all the user has to do, is to unpack the contents of the latest official Wordpress distribution file to the folder/directory where Wordpress is already installed, choosing to OVERWRITE all files in the way.
Despite the fear that a total overwrite might cause, it is a safe operation, because there is only one critical file (wp-config.php), that could cause problems, if lost, but is distributed with a different name (wp-config-sample.php), to be renamed only on first time installs.

With IIS 6, things aren’t so easy.

The system running IIS6 should have “simple file sharing” disabled. Such option allows the “security” and the “web sharing” tabs to appear, on the dialog box that shows, when selecting “folder properties”.

Knowing this, after OVERWRITING all Wordpress files, as if upgrading Wordpress on IIS 5, to upgrade Wordpress on IIS 6, just follow the next six steps.

Step #1 – Locate the Wordpress folder on the local file system (for example, c:\webs\site\wordpress);
Step #2 – Choose properties (ALT+ENTER) for that folder.
Step #3 – On the security tab, select the “Internet Guest Account”, then click the button “advanced”.

Wordpress upgrade on IIS 6 – Picture 1 of 5 – select the “Internet Guest Account”, then click the “Advanced” button.

Wordpress upgrade on IIS 6 – Picture 2 of 5 – Check both the checkboxes, then press ok.

Step #4 – As shown on the picture above, select both check boxes, to (1) allow inheritable permissions from the parent folder, and (2) to replace the previous permissions, everywhere down the tree. Then, press OK.

Wordpress upgrade on IIS 6 – Picture 3 of 5

Step #5 – Point the Internet browser to the site’s Wordpress URL (for example, http://arturmarques.com/wordpress) and follow the instructions on screen.
As the image above shows, you’ll first have to choose to upgrade the database.

Wordpress upgrade on IIS 6 – Picture 4 of 5 – Upgrade goes on

After upgrading the database, some files will also be updated.

Wordpress upgrade on IIS 6 – Picture 5 of 5 – The conclusion

Step #6 (final) – After a few seconds, the upgrade is done. Just visit your Wordpress site to confirm.

I hope this guidance can help someone who gets stuck on something so simple, yet with the potential to cause a major headache.

UPDATE: some Wordpress upgrades change the database structure. If so, it will be needed to upgrade the database, by visiting http://server/path/wordpress/wp-admin/upgrade.php
where server and path should be replaced by proper values, specific to each installation.

For example, here at home, the upgrade can be invoked the following way:
http://localhost/cgi-bin/wordpress/wp-admin/upgrade.php

I found that the “group posting” (Blog -> Group Posting) feature in BlogJet has one problem: if the post includes images and you are posting from your localhost PC to both a localhost blog and to a public Internet blog, then the public Internet blog might NOT display the pictures, because their URLs - their src tag - might point to the localhost machine!

For example, I was “group posting” to arturmarques.com and to a http server on my Intranet (named “X”).
The <img src=”something”> HTML would always mention X, no matter the server.

I had to edit the many posts who had wrong URLs for the images. This huge error was hard to spot, because I did most browsing tests from the X machine, meaning that the images were still showing, because they were available from the Intranet. Only when testing from outside the Intranet, I realized my mistake.

When fixing the mistake, I found another BlogJet annoyance: each closing bracket was being forward’slashed.
For example <tag bla bla> was being transformed in <tag bla bla />. This caused no HTML parsing errors, but did not correspond to the post’s original HTML, so I also edited the affected posts, only to discover that the HTML that gets posted by BlogJet is NOT exactly what the user types - again, the slash phenomenon happens, although it doesn’t break the pages.

Because of multiple edits, I had posts with several slashes like “<tag bla bla bla / / />” – this one corresponds to a twice edited post (one slash on creation; one extra slash per edit).

Doing the text find/replace operation to transform, for example, “/ / / />” in “>” was NOT easy!
My default text editor (NoteTab Light 4.95) didn’t detect the right character set, so when doing a simple copy paste from BlogJet’s HTML view, the Portuguese characters got all messed up.

Because of this, I started using EditPad Light. This free editor allows to easily change the document’s character set.
I found that BlogJet’s HTML is UTF-8. So, setting EditPad to UTF-8, allows direct copy/paste from BlogJet even for non english characters.

Quite a ride. I am sorry if you visited the website and found (only) the “ALT” description for pictures… It is fixed – I hope.

I’ve been playing with WebCeo and I am very much impressed with its flexibility and power. Even the free version will give the user a solid understanding of search engine optimization techniques, plus related tools.

Now, all you need is time to use all the tools, for a more search engine effective website

I found good and concise answers, about what Windows Vista will bring, here.