Check out More comic strips http://15xcomic.blogspot.com

Happy Nanowrimo! Follow my progress at http://www.nanowrimo.org/eng/user/246963

I thought I’d thoroughly read this article, but upon reading it again today, I noticed a key point I’d missed. If you can’t upgrade your SVN client, do a fresh checkout with the older client. I’m going to have to try this now…

This client is too old to work with working copy ‘XXX’

The full error message is:
This client is too old to work with working copy ‘.’; please get a newer Subversion client.

You will get this error message once you have used a Subversion client linked with a higher Subversion version, and then try to execute a command with a Subversion client linked with an older version, e.g., you used an 1.4.x client on your working copy, and now you try an svn 1.3.x client on the same working copy.

The reason for this is that Subversion 1.4 and 1.5 upgrade the working copies transparently on every command. But once the working copy format is upgraded, older clients can’t access the working copy anymore because they don’t know the new format.

The only solution to ‘fix’ this is to upgrade whatever clien

via This client is too old to work with working copy ‘XXX’ | TortoiseSVN

Attention: I know that there are bugs, with my fix based on the configuration of your menu system. Since I can not replicate these issues myself, I can not fix them on my own. I would like to complete the fix for those people who may want to use joomla with dynamic caching. If you are interested please email me at joomlafixd@yahoo.com.

It’s no secret that there are serious performance problems with Joomla 1.5x. Especially if you’re not using caching. Right out of the box, most sites see memory and CPU usage go through the roof with each request. This problem is well documented, and even Joomla’s own website has pages dedicated to helping users come up with fixes and work-arounds.

After much frustration on a recent project, I decided to investigate the problem. Below is what I discovered.

First: By turning off the Main Menu in the Module Manager, there is vast improvement in performance to be found. This is where most of the resources are greedily consumed.

Next: To recreate the functionality of the menu system, I created a hack that caches the HTML for all of Joomla’s menus. I’ve made this available to the public, below.

Note: The project I worked on has a fairly large menu, about five levels deep. But this hack should work for any size menu.

Here are the results.

Before
Profile Information
Application afterLoad: 0.002 seconds, 0.43 MB
Application afterInitialise: 0.214 seconds, 2.28 MB
Application afterRoute: 0.341 seconds, 3.78 MB
Application afterDispatch: 0.482 seconds, 4.33 MB
Application afterRender: 5.377 seconds, 6.02 MB
Memory Usage
6346872
45 queries logged

After
Profile Information
Application afterLoad: 0.002 seconds, 0.43 MB
Application afterInitialise: 0.191 seconds, 2.28 MB
Application afterRoute: 0.308 seconds, 3.78 MB
Application afterDispatch: 0.446 seconds, 4.33 MB
Application afterRender: 0.708 seconds, 5.16 MB
Memory Usage
5455480
45 queries logged

Notice the afterRender where the Top Menu module executes. Significant time and memory has been shaved off.

While the performance improvements are most noticeable when you’re not using caching (either free or purchased), this hack will work alongside all the caching plug-ins available.

Also, I have not come up with an elegant way to make a plug-in, so you’ll have to replace some files to get it to start working. (If you have suggestions on how best to make this a plug-in, let me know.)

Instructions

1. Make a back-up copy of these files in case it does not work properly for your install. Then copy helper.php under your docs/modules/mod_mainmenu
item.php and list.php under /docs/administrator/components/com_menus/models.

2. Replace those files with these, under the same directory: helper.php, item.php, and list.php.

3. Make sure that the docs/cache folder is write-able, you should start seeing .html files appear with in your cache directory. The html files are all the menu files cached so that Joomla does not have to execute or build the data structure to write them out. The source files that go in the administrator component will take care of menu changes by deleting the specific cache.

Update on joomlacode:

There are two patches mines and this one. My patch should be a greater performance boost, but as I said this is more a work around or hack. I do not know if joomla is addressing this in any other fashion.

Also if you are experiencing bugs, please email me at joomlafixd@yahoo.com, so maybe I can work out a universal solution in case joomla does not come up with an actual fix.

E’ stato scoperto recentemente un Bug nel Cms joomla (Core 1.5x – 1.5.5)

Molti siti sono stati defacciati grazie a questo bug che permette di reimpostare la password dell’admin, non linko l’exploit altrimenti contribuirei a diffondere il morbo lamer.

Gli sviluppatori si sono subito messi a lavoro su come fixare il bug ed ora è disponibile un nuovo core patchato: Link-> http://download.joomla.it/index.php?option=com_docman&task=cat_view&Itemid=2&gid=201&orderby=dmdate_published

Se non volete cambiare tutto il core potete pensare a patcharlo voi stessi modificando il file residente nella path /components/com_user/models/ chiamato reset.php

Vediamo come patcharlo:

1. Aprite il file reset.php
2. Andate nella riga 113 aggiungete queste linee di codice:

3. if(strlen($token) != 32) {
   	$this->setError(JText::_('INVALID_TOKEN'));
   	return false;
   }

4. Salvate e chiudete
5. Il vostro sito è protetto dalla vulnerabilità Remote Admin Password Change.

Quì potete trovare la spiegazione ufficiale.

Invito TUTTI i webmaster che hanno questa versione di core e non hanno ancora patchato il sito di effettuare l’upgrade o di patcharlo immediatamente.

nel caso avete un sito/blog/forum etc. CONTROLLATELO

Utilizzando le Dork di google è molto semplice trovare i siti vulnerabili, quindi state allerta.

Torna alla HomePage

]]> http://raquelsaraiva.wordpress.com/2008/07/24/photographer/ Thu, 24 Jul 2008 22:33:28 +0000 raquelsaraiva http://raquelsaraiva.wordpress.com/2008/07/24/photographer/

Eu e a minha pretinha. ^^

Essa câmera digital incorpora uma maravilhosa tecnologia, e o melhor de tudo é que a H50 possui além de tudo um design super compacto.

Entre as suas principais características encontramos: zoom óptico de 15x aumentos, sensor de 9.1 megapixels efetivo, amplo display LCD de 3 polegadas, sistema de reconhecimento de faces e sensibilidade ISO 3200.

Fonte: Sony.com