<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>News from Planet eZ publish</title>
    <link>http://planetezpublish.org</link>
    <description></description>
    <language></language>
    <item>
      <pubDate>Fri, 29 Aug 2008 19:58:00 GMT</pubDate>
      <author>Derick Rethans</author>
      <title>Scotland Holiday</title>
      <link>http://derickrethans.nl/scotland_holiday.php</link>
      <description>
&lt;p&gt;
Edinburgh, August 9th and 10th, 2008
		&lt;/p&gt;

&lt;p&gt;
I had a good flight through Amsterdam to Edinburgh, the real nerves
started when my luggage did not appear on the baggage belt. Apparently I
had missed it and it had fallen off in the back, out of sight. After
being reunited with my bags slightly later and getting the car I made
the arduous trip to the &quot;hotel&quot;.  The &quot;hotel&quot; was
the Heriot-Watt campus, which was neither sign-posted or easy to find.
After making a few circles through the neighbourhood, I managed to find
it. However, finding the campus wasn&apos;t the only issue -- 30 minutes
later I finally had found the reception in a pitch black night. Sleep
commenced very soon after that.
		&lt;/p&gt;

&lt;p&gt;
I got up early in the morning for a light breakfast and unhappily
discovered that it was raining. Not something you should be surprised
about in Scotland. I took the bus into town to meet up with Lorna and
after a cup of tea Scott as well. Without any real plan we wandered
around the city and taking in the views. This quickly turned into
looking for food. While having some drinks over lunch we chatted a bit
more, and more walking occurred in the afternoon. We got tired, had some
more drinks and by that time Lorna had to leave for home again.
		&lt;/p&gt;

&lt;p&gt;
Scott and I dropped of our gear at his room and went looking for a
comedy show to go to. The Edinburgh Fringe festival was happening, so
the biggest problem was to which of the 640 shows we wanted to go. We
settled for &quot;Des Clarke - Desire&quot; at the Pleasance Courtyard.
After a cup of tea in a café full of loonies, we left for the show. We
had a great time, although his accent was sometimes a bit hard to
understand for me. A cab brought me back to the &quot;hotel&quot;.
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/edinburgh.jpg&apos; align=&apos;right&apos; alt=&apos;&apos;/&gt;After
sleeping in a little bit, I took the bus again to downtown Edinburgh. I
took a quick bite to give me strength to visit the Edinburgh castle. I
took the long route through Princess Gardens up the hill. The queue for
tickets took a little over hand an hour. The tour at the castle itself,
was interrupted by the occasional shower, but the weather had improved a
lot since the previous day.  The castle is a must see. I liked the
&quot;prison of war&quot; exhibitions best, and the crown jewels where
the anti-climax.
		&lt;/p&gt;

&lt;p&gt;
After visiting the castle I was quite hungry and went to have a lunch of
stir fried scallops at the Mussels hut. With the new found energy I
climbed Caston hill. The last hours in Edinburgh I spend at the various
street theaters of the fringe. After a light dinner at &quot;bar
One&quot;, consisting of swordfish and an apple/carrot salad I left back
by bus to the Heriot-Watt campus.
		&lt;/p&gt;

&lt;p&gt;
Edinburgh to the Isle of Arran, August 11th, 2008
		&lt;/p&gt;

&lt;p&gt;
I started the day with a simple though hearty breakfast at the newly
opened Mensa. From the hotel I travelled first slightly south to visit
Roslyn&apos;s chapel. Unfortunately the chapel is mostly hidden by a roof to
protect it from the rain. Inside photography was not allowed, so I
didn&apos;t manage to take any pictures. In the church I listened to a guide
explaining all the interesting art from the chapel. From pagan green
men, the apprentice pillar and the Hollywood circle, the church appeared
to house much more than I expected. From the church I left for Falkirk,
home of the Falkirk Wheel.
		&lt;/p&gt;

&lt;p&gt;
The wheel replaces many locks between the Union and Forth and Clyde
canals, and is quite an engineering feat. For some time there was even
some blue sky which made watching the wheel turn more pleasant. I
continued my journey after a quick lunch towards Glasgow and to
Ardrossan where I would take the ferry to the Isle of Arran. I was a bit
early and wandered about the really windy harbour. They also tried to
fool me that my ferry would be two hours later, but that I didn&apos;t go
for. The trip of the Firth of Clyde was windy, bumpy and slight sunny.
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/falkirk.jpg&apos; align=&apos;left&apos; alt=&apos;&apos;/&gt;When I
got the Brodrick on the other side, I shopped for essential energy
suppliers for the upcoming walks around the island. I was staying at the
Catacol Bay hotel on the northern point of the island, where I had
breaded haddock for lunch. The wine that came with it &quot;forced&quot;
me to walk around a bit along the windy coast. The heavy rain that had
plummeted down when I arrived was gone. Before I went to bed I prepared
a bit for the hikes of the following day.
		&lt;/p&gt;

&lt;p&gt;
Isle of Arran, August 12th, 2008
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/machrie.jpg&apos; align=&apos;right&apos; alt=&apos;&apos;/&gt;Hiking
on an empty stomach doesn&apos;t work, but a full Scottish breakfast might be
a bit too close to suicide. Way too much artery clogging goodness for
me. Of course, the rain had returned but that was not going to stop me
from a little hike around the &quot;Cock of Arran&quot;. From my
&quot;parking place&quot; I spotted a few seals, but they were obviously
not sun-bathing. I didn&apos;t walk the whole planned tour as there was
simply too much rain. In the end I was happy that I didn&apos;t continue, as
I would have missed some many other things during my really short stay
on Arran.
		&lt;/p&gt;

&lt;p&gt;
The next stop on my tour around Arran was a short walk to the standing
stones and stone circles of Machrie Moor. During the two mile hike it
was of course raining still. The last hike of the day was to the King&apos;s
caves. I was silly and went the wrong way for nearly half an hour, but
it finally stopped raining.  After some dry period I finally ended up at
the caves. There was even some sunshine. The rest of the day I merely
drove around the rest of the island thinking I had no water with me.
Back at the hotel I found six bottles in the trunk. I had dinner in the
hotel&apos;s bar and the Hitchhikers Guide to the Galaxy brought and end to
the day.
		&lt;/p&gt;

&lt;p&gt;
Isle of Arran to Isle of Skye, August 13th, 2008.
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/stalker.jpg&apos; align=&apos;right&apos; alt=&apos;&apos;/&gt;A heavy
Scottish breakfast started the day. I left quite early to catch the
ferry at Brodrick back to the mainland. The day consisted of a lot of
driving over narrowish roads. I stopped for a late lunch at a café
overlooking Monty Python&apos;s castle Stalker. The weather was getting
better the close I got to Skye. After the Skye bridge beautiful scenery
appeared but I stopped only briefly to take some pictures as it was
getting late too quickly. I didn&apos;t really settle in at the lovely
B&amp;B &quot;Roskhill House&quot; until after dinner at Hotel
Dunvegan&apos;s bar.
		&lt;/p&gt;

&lt;p&gt;
Isle of Skye, August 14th and 15th, 2008
		&lt;/p&gt;

&lt;p&gt;
A nice breakfast at the B&amp;B started the day. It was beautiful
weather and excellent for my plan to hike to the Quiraing. A quick drive
later over surprisingly good roads--although the last part was a
one-file road--brought me to the parking place at the start of the hike.
From there I walked for ca. 2.5 hours over the maintain range. Very
strange rock formations and beautiful vistas. From there I drove on to
walk to the Cave of Gold but was met by some bulls in a field that I had
to cross. I gave up in fear of my life, and instead drove to Neist&apos;s
point and enjoyed the view there in the setting sun.
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/quiraing.jpg&apos; align=&apos;&apos; alt=&apos;&apos;/&gt;
		&lt;/p&gt;

&lt;p&gt;
I had dinner at &quot;Old School&quot; restaurant. Actually, I had
dinner twice. For some reason my starter--duck--was misunderstood as
another main course by the totally cute, but clumsy waitress (it could
have been my accent of course as well). Both dinners were
excellent; if you want to eat here as well, make sure you book on time,
one, if not two days before hand.
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/storr.jpg&apos; align=&apos;left&apos; alt=&apos;&apos;/&gt;The second
day I was woken up by a little rain shower, but luckily the rain was
gone before I was out of the shower. As the weather on the east coast of
the island was supposedly going to be a bit better, I opted for climbing
up to the &quot;Old Man of Storr&quot;. A really nice walk with
excellent views -- which got even better when the sun broke through.
From the Storr I traveled up the coast and stopped a few times to enjoy
the views and take some pictures. I ended up doing a walk to a lock,
which was boring. With threatening rain I aborted the walk -- I got back
to the car just before the shower would have soaked me. I had dinner at
the Dunvegan hotel as my first choice, the &quot;Loch Bay Seafood
Restaurant&quot; had no space for me.
		&lt;/p&gt;

&lt;p&gt;
Isle of Skye to Edzell, August 16th, 2008
		&lt;/p&gt;

&lt;p&gt;
Lots of driving again this day. I started off after brekkie for
Scotland&apos;s east coast. I took a few compulsory pictures at Eilean Dohan
castle and then drove along the shore of Loch Ness towards Invernness. I
made a quick stop at Urquhart and but not manage to spot Nessie. I
continued my way south from there through beautiful Aberdeenshire where
all the heaths were blossoming. I was staying in a small village, Edzell
at the Kelvingrove B&amp;B. I had dinner at the Panmure Arms Hotel,
which has an interesting setting. The food however was excellent.
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/eilean_donan.jpg&apos; align=&apos;&apos; alt=&apos;&apos;/&gt;
		&lt;/p&gt;

&lt;p&gt;
Angus, August 17th, 2008
		&lt;/p&gt;

&lt;p&gt;
Breakfast was early at the B&amp;B which meant that I had some time to
kill before all the attractions opened -- it was a Sunday after all. So
I decided to drive into Glen Clova, the supposedly nicest of the Angus
glens. Unfortunately there was not much too see in the mist. I then
proceeded to Glamis castle, said to have been the set for Shakespeare&apos;s
MacBeth. It is very nice, with gardens all around. I found it a bit too
commercial. From there on I visited the Pictavia museum in Brechin
followed by a quick visit to Aberlemno to see a few of those Pictish
stones. It was a bit of a bummer and lame. As last activity of the day I
wanted to walk a little bit along the coast. But at the moment I started
to walk, the rain started to pour down as well. So I aborted and went
back to the B&amp;B to eat, pack and watch a movie. The following day I
was going home again.
		&lt;/p&gt;

&lt;p&gt;
&lt;img src=&apos;http://derickrethans.nl/images/content/glamis.jpg&apos; align=&apos;&apos; alt=&apos;&apos;/&gt;
		&lt;/p&gt;

&lt;p&gt;
Final notes
		&lt;/p&gt;

&lt;p&gt;
I should definitely have spend more time on Arran and Skye - both
beautiful places of which I&apos;ve not even seen half.
		&lt;/p&gt;

&lt;p&gt;
The food is mostly great in Scotland, as long as you stay away from
Haggis.
		&lt;/p&gt;

&lt;p&gt;
My best accommodation was &lt;a href=&quot;http://www.roskhillhouse.co.uk/&quot;&gt;Roskhill House&lt;/a&gt;, there were
also lots of other hikers there, which added to the atmosphere.
		&lt;/p&gt;

&lt;p&gt;
I had the least amount of fun in the last day in Angus.
		&lt;/p&gt;

&lt;p&gt;
It always rains in Scotland, so bring waterproof gear.
		&lt;/p&gt;

&lt;p&gt;
My pictures from the trip are on &lt;a href=&quot;http://flickr.com/photos/derickrethans/sets/72157606886274251/&quot;&gt;flickr&lt;/a&gt;.
		&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Tue, 26 Aug 2008 20:34:57 GMT</pubDate>
      <author>Damien Pobel</author>
      <title>Sécuriser un site eZ Publish</title>
      <link>http://pwet.fr/blog/securiser_un_site_ez_publish</link>
      <description>&lt;p&gt;&lt;a href=&quot;http://www.clochix.net&quot;&gt;Clochix&lt;/a&gt;
 a publié cette semaine deux articles à propos de sécurité; &lt;a href=&quot;http://www.clochix.net/post/2008/08/13/Et-si-on-s-interressait-a-la-securite-des-CMS&quot;&gt;le premier sur les &lt;acronym title=&quot;Content Management System&quot;&gt;CMS&lt;/acronym&gt;
 en général&lt;/a&gt;
 et &lt;a href=&quot;http://www.clochix.net/post/2008/08/20/Astuce-pour-securiser-l-affichage-d-un-site-eZ-Publish&quot;&gt;le second plus spécifiquement sur eZ Publish&lt;/a&gt;
. Le problème pointé est l&apos;affichage par défaut de tous les objets dans &lt;a href=&quot;http://pwet.fr/tags/keywords/weblog/ez_publish&quot;&gt;eZ Publish&lt;/a&gt;
 par les &lt;i&gt;templates&lt;/i&gt; par défaut même lorsque cela ne devrait pas arriver. La solution (simple) proposée est de faire des surcharges s&apos;appliquant en dernier et n&apos;affichant rien pour éviter d&apos;afficher tout ce qui n&apos;a pas été prévu. Évidemment il est toujours mieux de restreindre les droits, mais c&apos;est un bon dernier rempart à la divulgation d&apos;informations...&lt;/p&gt;&lt;p&gt;Il y a évidemment d&apos;autres éléments à considérer et j&apos;en oublie probablement d&apos;ailleurs mais voici ceux qui me viennent à l&apos;esprit.&lt;/p&gt;&lt;p&gt;Au niveau &lt;i&gt;template&lt;/i&gt;, il faut toujours penser à utiliser &lt;a href=&quot;http://ez.no/doc/ez_publish/technical_manual/4_0/reference/template_operators/strings/wash&quot;&gt;l&apos;opérateur wash()&lt;/a&gt;
, il permet de s&apos;assurer que tous les caractères spéciaux sont échappés pour produire du code XHTML valide mais aussi pour éviter &lt;a href=&quot;http://fr.wikipedia.org/wiki/Cross_site_scripting&quot;&gt;des attaques de type &lt;acronym title=&quot;Cross Site Scripting&quot;&gt;XSS&lt;/acronym&gt;
&lt;/a&gt;
 si surtout votre site propose aux internautes de contribuer.&lt;/p&gt;&lt;p&gt;Au niveau système pour un site en production, seul le répertoire &lt;tt&gt;var&lt;/tt&gt;
 devrait être permettre l&apos;écriture au serveur web. On peut aussi restreindre &lt;a href=&quot;http://pwet.fr/blog/droits_necessaires_dans_mysql_pour_ez_publish&quot;&gt;les droits de l&apos;utilisateur MySQL utilisé par eZ Publish&lt;/a&gt;
 pour limiter la portée d&apos;une éventuelle mauvaise utilisation de ce compte.&lt;/p&gt;&lt;p&gt;On peut aussi penser à désactiver les modules et/ou les vues inutiles pour un &lt;i&gt;siteaccess&lt;/i&gt; donné. Par exemple, pour ce site, le fichier site.ini.append.php de mon siteaccess correspondant au &lt;i&gt;front&lt;/i&gt; comporte la configuration suivante :&lt;/p&gt;	&lt;pre class=&quot;ini&quot;&gt;&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;SiteAccessRules&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;access&lt;/span&gt;&lt;span style=&quot;color: #666666; font-style: italic;&quot;&gt;;enable&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;moduleall&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;access&lt;/span&gt;&lt;span style=&quot;color: #666666; font-style: italic;&quot;&gt;;disable&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;module&lt;/span&gt;&lt;span style=&quot;color: #666666; font-style: italic;&quot;&gt;;user/register&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;module&lt;/span&gt;&lt;span style=&quot;color: #666666; font-style: italic;&quot;&gt;;user/forgotpassword&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;module&lt;/span&gt;&lt;span style=&quot;color: #666666; font-style: italic;&quot;&gt;;user/activate&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;module&lt;/span&gt;&lt;span style=&quot;color: #666666; font-style: italic;&quot;&gt;;user/success&lt;/span&gt;
Rules&lt;span style=&quot;color: #000066; font-weight:bold;&quot;&gt;&lt;span style=&quot;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;&quot;&gt;]&lt;/span&gt;&lt;/span&gt;=&lt;span style=&quot;color: #660066;&quot;&gt;module&lt;/span&gt;&lt;span style=&quot;color: #666666; font-style: italic;&quot;&gt;;ezinfo &lt;/span&gt;
 &lt;/pre&gt;&lt;p&gt;Ces quelques lignes désactivent quelques vues du module &lt;tt&gt;user&lt;/tt&gt;
 ainsi que le module &lt;tt&gt;ezinfo&lt;/tt&gt;
 qui sont accessibles aux utilisateurs anonymes alors qu&apos;ils ne me sont pas nécessaires. La vue &lt;tt&gt;ezinfo/about&lt;/tt&gt;
 en particulier donne des informations sur les extensions activées et surtout sur la version d&apos;eZ Publish ce qui permet de savoir à quoi est potentiellement vulnérable le site. Dans tous les cas, &lt;a href=&quot;http://pwet.fr/blog/upgrade_to_ez_publish_4_0_1&quot;&gt;il vaut mieux être à jour&lt;/a&gt;
, les versions 4.0.0, 3.10.0 et 3.9.4 sont &lt;a href=&quot;http://ez.no/developer/security/security_advisories&quot;&gt;vulnérables à quelques failles connues&lt;/a&gt;
.&lt;/p&gt;&lt;p&gt;Il faut aussi penser à nommer les fichiers de configuration en .ini.append.php et à encadrer le contenu par des commentaires HTML ce qui évite toute possibilité de lecture via un accès direct par le serveur web. À ce niveau, avoir &lt;a href=&quot;http://ez.no/doc/ez_publish/technical_manual/4_0/installation/virtual_host_setup&quot;&gt;un site eZ Publish en mode Virtual Host&lt;/a&gt;
 devrait aussi apporter un gain en cachant presque complètement l&apos;arborescence &quot;physique&quot; du site.&lt;/p&gt;&lt;p&gt;Enfin au niveau des extensions il faut évidemment penser à échapper toutes les données inconnues avant de l&apos;utiliser dans une requête SQL (ça n&apos;est pas spécifique à eZ Publish !), &lt;a href=&quot;http://pubsvn.ez.no/doxygen/4.0/html/classeZDBInterface.html#743e3da0d8f956262e551b3da9fb3591&quot;&gt;la méthode escapeString() de la classe eZDBInterface&lt;/a&gt;
 est faite pour ça.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Tue, 26 Aug 2008 09:50:56 GMT</pubDate>
      <author>eZ Projects</author>
      <title>Uploaded code to download section and added code to subversion repository</title>
      <link>http://projects.ez.no/enhancedezbinaryfile/news/uploaded_code_to_download_section_and_added_code_to_subversion_repository</link>
      <description>
&lt;p&gt;
The 1.0 code for the enhancedezbinaryfile type has been released.
&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Mon, 25 Aug 2008 16:27:28 GMT</pubDate>
      <author>Hans Melis</author>
      <title>MOSS 2007: laugh or cry?</title>
      <link>http://blog.hansmelis.be/2008/08/25/moss-2007-laugh-or-cry/</link>
      <description>When Microsoft released Microsoft Office Sharepoint Server (MOSS) 2007, it was touted as The Next Big Thing™ for enterprises. And that&amp;#8217;s where the good news ends&amp;#8230;
This piece of software has so many issues I don&amp;#8217;t even know where to start. My first encounter with it was when I had to evaluate the web content management [...]</description>
    </item>
    <item>
      <pubDate>Sun, 24 Aug 2008 14:55:58 GMT</pubDate>
      <author>Damien Pobel</author>
      <title>Upgrade to eZ Publish 4.0.1</title>
      <link>http://pwet.fr/blog/upgrade_to_ez_publish_4_0_1</link>
      <description>
&lt;div class=&quot;object-center&quot;&gt;&lt;div class=&quot;content-view-embeddedmedia&quot;&gt;
&lt;div class=&quot;class-image&quot;&gt;

&lt;div class=&quot;attribute-image&quot;&gt;
&lt;p&gt;    
    
        
    
            &lt;a href=&quot;http://pwet.fr/media/images/nouveau_logo_ez_publish_4_0_1&quot;&gt;&lt;img src=&quot;http://pwet.fr/var/plain/storage/images/media/images/nouveau_logo_ez_publish_4_0_1/215974-1-fre-FR/nouveau_logo_ez_publish_4_0_1_largeurBlog.png&quot; width=&quot;524&quot; height=&quot;126&quot;  alt=&quot;&quot; /&gt;&lt;/a&gt;    
    
    
    &lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;&lt;p&gt;&lt;a href=&quot;http://ez.no/developer/news/ez_publish_4_0_1_3_10_1_and_3_9_5_released&quot;&gt;eZ Publish 4.0.1 has been released this week&lt;/a&gt;
, I upgraded this afternoon because of &lt;a href=&quot;http://ez.no/developer/security/security_advisories&quot;&gt;security advisories on eZ Publish 4.0&lt;/a&gt;
. In fact, there&apos;s nothing to say, &lt;a href=&quot;http://ez.no/doc/ez_publish/upgrading/upgrading_to_4_0/from_4_0_x_to_4_0_y&quot;&gt;the upgrade runs smoothly&lt;/a&gt;
 without any major problem for me, even &lt;a href=&quot;http://pwet.fr/blog/upgrading_a_large_site_from_ez_publish_3_9_2_to_ez_publish_3_10&quot;&gt;on migrating more than 60 000 URL aliases&lt;/a&gt;
 on &lt;a href=&quot;http://pwet.fr/blog/ez_publish_sur_dedibox&quot;&gt;a small server&lt;/a&gt;
. Great job eZ guys !&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Sat, 23 Aug 2008 16:45:12 GMT</pubDate>
      <author>Damien Pobel</author>
      <title>Install eZWebin Toolbar into an existing site</title>
      <link>http://pwet.fr/blog/install_ezwebin_toolbar_into_an_existing_site</link>
      <description>&lt;p&gt;&lt;a href=&quot;http://ez.no/doc/extensions/website_interface&quot;&gt;eZWebin&lt;/a&gt;
 is an extension providing a toolbar that lets you manage your content directly in the front-end of an &lt;a href=&quot;http://pwet.fr/tags/keywords/weblog/ez_publish&quot;&gt;eZ Publish&lt;/a&gt;
 site. When &lt;a href=&quot;http://pwet.fr/blog/pwet_2_0&quot;&gt;refreshing the design of this site&lt;/a&gt;
, integrating the toolbar was one of my goals. &lt;a href=&quot;http://serwatka.net/&quot;&gt;Łukasz Serwatka&lt;/a&gt;
 had already published &lt;a href=&quot;http://serwatka.net/blog/how_to_create_and_use_an_ez_publish_website_toolbar_extension&quot;&gt;a nice article on how to create your own toolbar extension&lt;/a&gt;
 by copying files from the ezwebin extension. I don&apos;t like this solution because you have to copy again those files when the extension is upgraded (I&apos;m lazy as all developers !). That&apos;s why I use the following steps on my blog.&lt;/p&gt;&lt;a name=&quot;eztoc215940_1&quot; id=&quot;eztoc215940_1&quot;&gt;&lt;/a&gt;&lt;h2&gt;Install and configure the ezwebin extension&lt;/h2&gt;&lt;p&gt;If you don&apos;t have the ezwebin extension installed, you have to download and install it. Retrieve &lt;a href=&quot;http://packages.ez.no/ezpublish/4.0/4.0.0/ezwebin_extension.ezpkg&quot;&gt;the ezwebin extension as a package&lt;/a&gt;
 on &lt;a href=&quot;http://ez.no/download/ez_publish/ez_publish_4_stable_releases/4_0/packages/4_0_0&quot;&gt;the eZ Publish 4.0 packages page&lt;/a&gt;
 (it should work with eZ Publish 4.0.1 to) and &lt;a href=&quot;http://ez.no/doc/ez_publish/technical_manual/4_0/features/packages/installing_packages&quot;&gt;install it through the admin interface&lt;/a&gt;
 and finally activate it. As I have my own design, I don&apos;t need the others ezwebin_* packages.&lt;/p&gt;&lt;a name=&quot;eztoc215940_2&quot; id=&quot;eztoc215940_2&quot;&gt;&lt;/a&gt;&lt;h2&gt;Template modification&lt;/h2&gt;&lt;p&gt;This step depends on your site. With most designs, you just need to add those lines of code in &lt;a href=&quot;http://ez.no/doc/ez_publish/technical_manual/4_0/templates/the_pagelayout#eztoc86799_4_1&quot;&gt;the pagelayout template before the &lt;tt&gt;{$module_result.content}&lt;/tt&gt;
&lt;/a&gt;
 :&lt;/p&gt;	&lt;pre class=&quot;smarty&quot;&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;def $current_node_id = first_set&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $module_result.&lt;span style=&quot;color: #006600;&quot;&gt;node_id&lt;/span&gt;, &lt;span style=&quot;color: #cc66cc;&quot;&gt;0&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;
     $content_info = cond&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; is_set&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $module_result.&lt;span style=&quot;color: #006600;&quot;&gt;content_info&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;, $module_result.&lt;span style=&quot;color: #006600;&quot;&gt;content_info&lt;/span&gt;, hash&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;
&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;&lt;span style=&quot;color: #0600FF;&quot;&gt;if&lt;/span&gt; and&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $current_node_id,
         $current_user.&lt;span style=&quot;color: #006600;&quot;&gt;is_logged_in&lt;/span&gt;,
         and&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; is_set&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $content_info.&lt;span style=&quot;color: #006600;&quot;&gt;viewmode&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;, &lt;span style=&quot;color: #D36900;&quot;&gt;ne&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $content_info.&lt;span style=&quot;color: #006600;&quot;&gt;viewmode&lt;/span&gt;, &lt;span style=&quot;color: #ff0000;&quot;&gt;&apos;sitemap&apos;&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;,
         and&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; is_set&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $content_info.&lt;span style=&quot;color: #006600;&quot;&gt;viewmode&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;, &lt;span style=&quot;color: #D36900;&quot;&gt;ne&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $content_info.&lt;span style=&quot;color: #006600;&quot;&gt;viewmode&lt;/span&gt;, &lt;span style=&quot;color: #ff0000;&quot;&gt;&apos;tagcloud&apos;&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;
&lt;style type=&quot;text/css&quot;&gt;
@import url(&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;&lt;span style=&quot;color: #ff0000;&quot;&gt;&quot;stylesheets/websitetoolbar.css&quot;&lt;/span&gt;|ezdesign&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt;no&lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;);
&lt;/style&gt;
&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;&lt;span style=&quot;color: #0600FF;&quot;&gt;include&lt;/span&gt; uri=&lt;span style=&quot;color: #ff0000;&quot;&gt;&apos;design:parts/website_toolbar.tpl&apos;&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;
&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;&lt;span style=&quot;color: #0600FF;&quot;&gt;elseif&lt;/span&gt; or&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; $uri_string|begins_with&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; &lt;span style=&quot;color: #ff0000;&quot;&gt;&apos;content/versionview&apos;&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;,
            $uri_string|begins_with&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt; &lt;span style=&quot;color: #ff0000;&quot;&gt;&apos;content/edit&apos;&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt; &lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;
&lt;style type=&quot;text/css&quot;&gt;
@import url(&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;&lt;span style=&quot;color: #ff0000;&quot;&gt;&quot;stylesheets/websitetoolbar.css&quot;&lt;/span&gt;|ezdesign&lt;span style=&quot;color: #D36900;&quot;&gt;(&lt;/span&gt;no&lt;span style=&quot;color: #D36900;&quot;&gt;)&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;);
&lt;/style&gt;
&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;/&lt;span style=&quot;color: #0600FF;&quot;&gt;if&lt;/span&gt;&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;
&lt;span style=&quot;color: #D36900;&quot;&gt;{&lt;/span&gt;undef $current_node_id $content_info&lt;span style=&quot;color: #D36900;&quot;&gt;}&lt;/span&gt;&lt;/pre&gt;&lt;p&gt;If you have several pagelayout templates, you can put this code in a template file and include it. It only adds the toolbar and/or a stylesheet if you are identified or if you edit or preview a content. The toolbar seems to be flexible enough to be included without major layout problem.&lt;/p&gt;&lt;a name=&quot;eztoc215940_3&quot; id=&quot;eztoc215940_3&quot;&gt;&lt;/a&gt;&lt;h2&gt;And then ?&lt;/h2&gt;&lt;p&gt;These steps bring an easy to use interface to manage your content. You probably need to adjust your stylesheet(s) to have a nice edit form.&lt;/p&gt;
&lt;table class=&quot;table-centre&quot;  border=&quot;0&quot; cellpadding=&quot;2&quot; cellspacing=&quot;0&quot; &gt;
&lt;tr&gt;
&lt;td valign=&quot;top&quot;&gt;  
&lt;div class=&quot;object-center&quot;&gt;&lt;div class=&quot;content-view-embeddedmedia&quot;&gt;
&lt;div class=&quot;class-image&quot;&gt;

&lt;div class=&quot;attribute-image&quot;&gt;
&lt;p&gt;    
    
        
    
            &lt;a href=&quot;http://pwet.fr/media/images/ezwebin_toolbar&quot;&gt;&lt;img src=&quot;/var/plain/storage/images/media/images/ezwebin_toolbar/215962-1-fre-FR/ezwebin_toolbar_DemiLargeurBlog.png&quot; width=&quot;250&quot; height=&quot;171&quot;  alt=&quot;&quot; /&gt;&lt;/a&gt;    
    
    
    &lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;

  &lt;/td&gt;

&lt;td valign=&quot;top&quot;&gt;  
&lt;div class=&quot;object-center&quot;&gt;&lt;div class=&quot;content-view-embeddedmedia&quot;&gt;
&lt;div class=&quot;class-image&quot;&gt;

&lt;div class=&quot;attribute-image&quot;&gt;
&lt;p&gt;    
    
        
    
            &lt;a href=&quot;http://pwet.fr/media/images/front_end_interface&quot;&gt;&lt;img src=&quot;/var/plain/storage/images/media/images/front_end_interface/215965-1-fre-FR/front_end_interface_DemiLargeurBlog.png&quot; width=&quot;250&quot; height=&quot;171&quot;  alt=&quot;&quot; /&gt;&lt;/a&gt;    
    
    
    &lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;

  &lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;
&lt;p&gt;I also have two small problems :&lt;/p&gt;
&lt;ol&gt;

&lt;li&gt;It&apos;s not possible to make &lt;a href=&quot;http://ez.no/doc/ez_publish/technical_manual/4_0/reference/template_override_conditions&quot;&gt;an override condition&lt;/a&gt;
 to use a special pagelayout for edit mode. Depending on your layout, you may need to add some conditions to have only one column (or enough space) in edit mode. For instance, the toolbar of &lt;a href=&quot;http://pwet.fr/blog/the_new_online_editor_for_ez_publish_beta&quot;&gt;the new Online Editor&lt;/a&gt;
 needs 750px to be displayed on a single line (even if it works well when the toobar is displayed on many lines)&lt;/li&gt;

&lt;li&gt;&lt;a href=&quot;http://issues.ez.no/13529&quot;&gt;content/versionview has a bug&lt;/a&gt;
 when it is used from the ezwebin toolbar. It doesn&apos;t use the right pagelayout if you have some override rules on it. I propose a patch in the bug report which works well for me. &lt;/li&gt;

&lt;/ol&gt;
&lt;p&gt;Nevertheless, it works well and it&apos;s very convenient for a blog.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Thu, 21 Aug 2008 19:15:39 GMT</pubDate>
      <author>eZ Systems North America</author>
      <title>Importing external contacts into eZ Publish: eZ Web Contacts extension</title>
      <link>http://feeds.feedburner.com/~r/ezna/~3/375553722/ez_web_contacts</link>
      <description>&lt;p&gt;eZ Web Contacts is an API encapsulated in its own eZ Publish extension. The extension provides a set of eZ Functions that enables an API user to query external service providers, such as Google and Yahoo, for web contacts.&lt;/p&gt;&lt;img src=&quot;http://feeds.feedburner.com/~r/ezna/~4/375553722&quot; height=&quot;1&quot; width=&quot;1&quot;/&gt;</description>
    </item>
    <item>
      <pubDate>Wed, 20 Aug 2008 13:29:15 GMT</pubDate>
      <author>Community news (ez.no)</author>
      <title>eZ Publish 4.0.1, 3.10.1, and 3.9.5 released</title>
      <link>http://ez.no/developer/news/ez_publish_4_0_1_3_10_1_and_3_9_5_released</link>
      <description>
&lt;p&gt;
We are happy to announce the stable releases of eZ Publish 4.0.1, 3.10.1, and 3.9.5. These releases carry a huge number of fixes (about 310 for 4.0.1) and upgrading is highly recommended. eZ Publish 4.0.1 should be used for all new installations.
&lt;/p&gt;

&lt;p&gt;
Included in these new releases is a dedicated extension to migrate custom URL aliases and URL history elements for existing 4.0.0 and 3.10.0 sites.
&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Wed, 20 Aug 2008 08:17:52 GMT</pubDate>
      <author>Felix Laate</author>
      <title>Carpe diem in Paris</title>
      <link>http://felix.laate.no/?p=8</link>
      <description>The first official eZ Media User Group  meeting will be held in Paris on September 4th from 9.00 to 16.00. I&amp;#8217;m realy looking forward to it, as I believe that when using open source technology one has to seize the opportunity to shape the techonology. Ask not what open source can do for you, [...]</description>
    </item>
    <item>
      <pubDate>Mon, 18 Aug 2008 14:24:20 GMT</pubDate>
      <author>eZ Projects</author>
      <title>eZSiteAccessOperator Version 1.0.0 released</title>
      <link>http://projects.ez.no/ezsiteaccessoperator/news/ezsiteaccessoperator_version_1_0_0_released</link>
      <description>
&lt;p&gt;
Today I released the first version of the siteaccess() operator
&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Mon, 18 Aug 2008 12:44:46 GMT</pubDate>
      <author>Maxime Thomas</author>
      <title>Firefox 3 - eZDebug extension</title>
      <link>http://www.wascou.org/Blogs/Maxime-THOMAS/Firefox-3-eZDebug-extension</link>
      <description>&lt;p&gt;And I finally finished it, the new version is better, smaller, faster, stronger ?&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;/wascou/Media/Images/eZDebug-1.0&quot; target=&quot;_blank&quot;&gt;Here&lt;/a&gt; are some screenshot of what it can do.&lt;/p&gt;&lt;p&gt;Some informations :&lt;/p&gt;
&lt;ul&gt;

&lt;li&gt;Click on the link to install the extension&lt;/li&gt;

&lt;li&gt;To use it, you can click on the small icon on the bottom right corner, make CTRL+SHIFT+E combination or open the related sidebar in Firefox. Then just press Scan when you are on a page with debug inside.&lt;/li&gt;

&lt;li&gt;Due to the differences between Firefox 2 and 3, it won&apos;t be updated fore Firefox 2. (And also because I&apos;m lazy).&lt;/li&gt;

&lt;li&gt;If there&apos;s no debug on the page, nothing happens.&lt;/li&gt;

&lt;li&gt;If you got some trouble, you can mail me or just leave a message here.&lt;/li&gt;

&lt;/ul&gt;
&lt;p&gt;You can download it on the official extension page on &lt;a href=&quot;https://addons.mozilla.org/fr/firefox/addon/8534&quot; target=&quot;_blank&quot;&gt;addons.mozilla.org&lt;/a&gt;. Please for this extension and leave a comment so it can be supported by the Mozilla Foundation.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Sun, 17 Aug 2008 13:06:10 GMT</pubDate>
      <author>Damien Pobel</author>
      <title>eZ Publish et l&apos;accessibilité</title>
      <link>http://pwet.fr/blog/ez_publish_et_l_accessibilite</link>
      <description>&lt;p&gt;Plusieurs études ont été réalisées cet été sur l&apos;accessibilité du &lt;acronym title=&quot;Content Management System&quot;&gt;CMS&lt;/acronym&gt;
 &lt;a href=&quot;http://pwet.fr/tags/keywords/weblog/ez_publish&quot;&gt;eZ Publish&lt;/a&gt;
 :&lt;/p&gt;
&lt;ul&gt;

&lt;li&gt;&lt;a href=&quot;http://blog.temesis.com/2008/07/10/331-rmll-cms-accessibilite-suite&quot;&gt;Comparatif de l&apos;accessibilité des CMS par Temesis&lt;/a&gt;
 accessible via &lt;a href=&quot;http://mon.opquast.com/&quot;&gt;un compte Opquast&lt;/a&gt;
&lt;/li&gt;

&lt;li&gt;&lt;a href=&quot;http://freemi.fr/ez_publish/backoffice_accessibilite.html&quot;&gt;Audit d&apos;accessibilité de l&apos;interface d&apos;administration du CMS eZ Publish 4.0&lt;/a&gt;
&lt;/li&gt;

&lt;li&gt;&lt;a href=&quot;http://freemi.fr/ez_publish/wysiwyg_accessibilite_ez.html&quot;&gt;Étude sur l&apos;accessibilité des contenus générés par les éditeurs WYSIWYG du CMS eZ publish 4.0&lt;/a&gt;
&lt;/li&gt;

&lt;/ul&gt;
&lt;p&gt;Je passe rapidement sur le premier qui pour moi a une valeur toute relative quand on parle d&apos;eZ Publish (et même de la plupart des autres CMS d&apos;ailleurs) puisque l&apos;étude se penche sur les &lt;i&gt;templates&lt;/i&gt; par défaut. Mais qui utilise les &lt;i&gt;templates&lt;/i&gt; par défaut d&apos;eZ Publish ?&lt;/p&gt;&lt;p&gt;Les deux suivantes ont été réalisées par &lt;a href=&quot;http://freemi.fr/&quot;&gt;Rémi Farrot&lt;/a&gt;
 et sont déjà nettement plus intéressantes. La première au sujet de l&apos;accessibilité du &lt;i&gt;backoffice&lt;/i&gt; montre que celui ci n&apos;est pas si mal de ce point de vue même si quelques points sont améliorables. Le plus gros problème dans le &lt;i&gt;backoffice&lt;/i&gt; est semble t il posé par les menus contextuels sur les icônes (fonctionnalité ultra pratique cela dit). Parmi les autres points faibles relevés, on trouve aussi l&apos;absence de l&apos;attribut &quot;for&quot; sur les balises label, je viens de créer &lt;a href=&quot;http://issues.ez.no/13503&quot;&gt;un rapport de bug sur ce point&lt;/a&gt;
, c&apos;est tellement pratique de cliquer sur les labels pour avoir le focus sur le champs associé !&lt;/p&gt;&lt;p&gt;La seconde étude de Rémi Farrot porte sur le code produit par les éditeurs &lt;acronym title=&quot;What You See Is What You Get&quot;&gt;WYSIWYG&lt;/acronym&gt;
 disponibles avec eZ Publish. La situation est nettement moins bonne dans ce registre, &lt;a href=&quot;http://ez.no/doc/extensions/online_editor/4_x&quot;&gt;Online Editor 4.x&lt;/a&gt;
 comme &lt;a href=&quot;http://pwet.fr/blog/the_new_online_editor_for_ez_publish_beta&quot;&gt;le nouvel éditeur basé sur TinyMCE&lt;/a&gt;
 sont plutôt mauvais. Malgré tout, beaucoup de points peuvent être corrigés avec une configuration adéquate et encore plus avec le nouvel éditeur. Ce sera peut être l&apos;objet d&apos;un prochain billet...&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Tue, 12 Aug 2008 18:55:00 GMT</pubDate>
      <author>Damien Pobel</author>
      <title>Putting a site under maintenance</title>
      <link>http://pwet.fr/blog/putting_a_site_under_maintenance</link>
      <description>&lt;p&gt;Pascal Specht asks &lt;a href=&quot;http://ez.no/developer/forum/general/under_maintenance&quot;&gt;a good question in the eZ Publish forums&lt;/a&gt;
 : &lt;i&gt;how to put a site under maintenance without breaking bookmarks and external links&lt;/i&gt; ?&lt;/p&gt;&lt;p&gt;The easiest way (the only ?) is probably to use &lt;a href=&quot;http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html&quot;&gt;mod_rewrite&lt;/a&gt;
 of &lt;a href=&quot;http://pwet.fr/man/linux/administration_systeme/apache2&quot;&gt;Apache&lt;/a&gt;
 to distribute a maintenance page instead of the normal page. This can be done with those few lines in a .htaccess file :&lt;/p&gt;	&lt;pre class=&quot;apache&quot;&gt;&lt;span style=&quot;color: #00007f;&quot;&gt;RewriteEngine&lt;/span&gt; &lt;span style=&quot;color: #0000ff;&quot;&gt;on&lt;/span&gt;
&lt;span style=&quot;color: #adadad; font-style: italic;&quot;&gt;#  RewriteCond  %{REMOTE_ADDR}         !^82.225.188.34$&lt;/span&gt;
&lt;span style=&quot;color: #00007f;&quot;&gt;RewriteRule&lt;/span&gt;  &lt;span style=&quot;color: #66cc66;&quot;&gt;(&lt;/span&gt;.*&lt;span style=&quot;color: #66cc66;&quot;&gt;)&lt;/span&gt; /path/to/your/maintenance/file/index.htm &lt;span style=&quot;color: #66cc66;&quot;&gt;[&lt;/span&gt;L&lt;span style=&quot;color: #66cc66;&quot;&gt;]&lt;/span&gt;&lt;/pre&gt;&lt;p&gt;With this setting, Apache distributes the index.htm file for all request. You can also put your own IP address on the second line and uncomment it so that you can view the normal site for example to generate some caches in &lt;a href=&quot;http://pwet.fr/tags/keywords/weblog/ez_publish&quot;&gt;eZ Publish&lt;/a&gt;
 before putting your site online again.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Mon, 11 Aug 2008 15:37:25 GMT</pubDate>
      <author>Maxime Thomas</author>
      <title>Ciao 3.x</title>
      <link>http://www.wascou.org/Blogs/Maxime-THOMAS/Ciao-3.x</link>
      <description>&lt;a name=&quot;eztoc1446_0_1&quot; id=&quot;eztoc1446_0_1&quot;&gt;&lt;/a&gt;&lt;h3&gt;It&apos;s done. We loved it, they stop it. Bye bye &lt;a href=&quot;http://ez.no/developer/news/ez_publish_4_0_1rc2_3_10_1rc2_released&quot; target=&quot;_blank&quot;&gt;eZPublish 3.x series&lt;/a&gt;...&lt;/h3&gt;&lt;p&gt;Yes, a bit sad but how good for developpers ! There were some features that eZSystems improved in the 3.x and which made this great software a more evolutive and scalable software for everyone. Here are the features I remember the most :&lt;/p&gt;&lt;a name=&quot;eztoc1446_0_1_1&quot; id=&quot;eztoc1446_0_1_1&quot;&gt;&lt;/a&gt;&lt;h4&gt;3.6&lt;/h4&gt;
&lt;ul&gt;

&lt;li&gt;LDAP handler : connect eZPublish on a LDAP directory and to automatically create users in the eZ subtree.&lt;/li&gt;

&lt;li&gt;Reverse features : get the objects which are relating the current object.&lt;/li&gt;

&lt;li&gt;Remove subtree : useful to delete entire subtree.&lt;/li&gt;

&lt;/ul&gt;
&lt;a name=&quot;eztoc1446_0_1_2&quot; id=&quot;eztoc1446_0_1_2&quot;&gt;&lt;/a&gt;&lt;h4&gt;3.7&lt;/h4&gt;
&lt;ul&gt;

&lt;li&gt;Siteaccess settings in the extensions : you can put siteaccess settings in the extension. It allows you to design reusable extensions, overriding standards.&lt;/li&gt;

&lt;li&gt;Developpement Mode : in dev mode it&apos;s not necessary to clear cache at each time...&lt;/li&gt;

&lt;/ul&gt;
&lt;a name=&quot;eztoc1446_0_1_3&quot; id=&quot;eztoc1446_0_1_3&quot;&gt;&lt;/a&gt;&lt;h4&gt;3.8&lt;/h4&gt;
&lt;ul&gt;

&lt;li&gt;Internationalisation : it is possible to translate any content in any language without having a content reference translated in a given language.&lt;/li&gt;

&lt;li&gt;Clustering : you can put several instance of eZ on several hosts to share the load.&lt;/li&gt;

&lt;li&gt;Group approval for workflows.&lt;/li&gt;

&lt;li&gt;Serialization for all datatypes.&lt;/li&gt;

&lt;li&gt;eZInfo() function for extensions.&lt;/li&gt;

&lt;/ul&gt;
&lt;a name=&quot;eztoc1446_0_1_4&quot; id=&quot;eztoc1446_0_1_4&quot;&gt;&lt;/a&gt;&lt;h4&gt;3.9&lt;/h4&gt;
&lt;ul&gt;

&lt;li&gt;Auto upload for files in Online Editor.&lt;/li&gt;

&lt;li&gt;Diff.&lt;/li&gt;

&lt;/ul&gt;
&lt;a name=&quot;eztoc1446_0_1&quot; id=&quot;eztoc1446_0_1&quot;&gt;&lt;/a&gt;&lt;h3&gt;And now ?&lt;/h3&gt;&lt;p&gt;Some upcoming goodies for us ! Version 3.10.1 and 4.0.1 will be updated and 4.1 is announced for Q3. It seems that eZ gets behind...&lt;/p&gt;&lt;p&gt;No ?&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Thu, 07 Aug 2008 18:40:00 GMT</pubDate>
      <author>Derick Rethans</author>
      <title>RIP PHP 4</title>
      <link>http://derickrethans.nl/rip_php_4.php</link>
      <description>
&lt;p&gt;
PHP 4 has been with us (as &quot;stable&quot; release) since May 22nd,
2000. In the past 8 years it brought us lots of joy, but in the later
years lots of pain. A better PHP, PHP 5, as been a better alternative
for close to 3 years now so it&apos;s time to get rid of the old stuff that
PHP 4 really is.
		&lt;/p&gt;

&lt;p&gt;
PHP 4 had quite some changes over the past years though. The main
changes came with new mini releases:
		&lt;/p&gt;

&lt;p&gt;
4.1.0 (10 Dec 2001): The introduction of the super globals.
		&lt;/p&gt;

&lt;p&gt;
4.2.0 (22 Apr 2002): Register globals was turned off by default. The
release announcement shouts &quot;External variables (from the
environment, the HTTP request, cookies or the web server) are no longer
registered as global variables&quot;.
		&lt;/p&gt;

&lt;p&gt;
4.3.0 (27 Dec 2002): Introduces &quot;CLI&quot;, PHP&apos;s Command Line
Interface and streams.
		&lt;/p&gt;

&lt;p&gt;
4.4.0 (11 Jul 2005): Addresses the &quot;&lt;a href=&quot;http://derickrethans.nl/php_440_release_candidate_1.php&quot;&gt;reference issue&lt;/a&gt;&quot;.
		&lt;/p&gt;

&lt;p&gt;
Now, more than 3 years after the last major PHP 4 release, it is time to
die down. With hardly any support for OO, sub-standard XML support and
generally lots of other suckyness as well, it&apos;s time to focus on the
future: PHP 6. So please die PHP 4 - and quickly. Today, August 7th,
2008 is the last release of PHP 4 - PHP 4.4.9. After today there will be
no more PHP 4 releases, regardless of whether there are security issues
found in PHP 4. It&apos;s time to upgrade now.
		&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Thu, 07 Aug 2008 10:14:50 GMT</pubDate>
      <author>Felix Laate</author>
      <title>On the coming of new versions</title>
      <link>http://felix.laate.no/?p=7</link>
      <description>Back in the old days (when eZ Publish was so difficult to install, that it took all my fridge-cold beer to get through it) there was no release-schedule at all. We all hung around the local astronomer to get some hints about the coming of long-awaited upgrades. But then things changed, a road-map appeared and [...]</description>
    </item>
    <item>
      <pubDate>Wed, 06 Aug 2008 19:46:00 GMT</pubDate>
      <author>Damien Pobel</author>
      <title>En attendant eZ Publish 4.0.1 (ou 4.1)</title>
      <link>http://pwet.fr/blog/en_attendant_ez_publish_4_0_1_ou_4_1</link>
      <description>&lt;p&gt;&lt;a href=&quot;http://pwet.fr/blog/ez_publish_4&quot;&gt;eZ Publish 4.0 est sorti en décembre 2007&lt;/a&gt;
 et depuis rien, aucune version stable. 8 mois c&apos;est vraiment très très très long, il y a donc forcément des bugs gênants dans &lt;a href=&quot;http://pwet.fr/tags/keywords/weblog/ez_publish&quot;&gt;eZ Publish&lt;/a&gt;
 4.0 d&apos;autant plus que cette version est un portage vers PHP5 de la version 3.10 ce qui occasionne encore quelques bugs supplémentaires. &lt;a href=&quot;http://issues.ez.no/RoadMap.php?Id=732&amp;ProjectId=3&quot;&gt;La roadmap du bugtracker&lt;/a&gt;
 liste les problèmes résolus et non résolus mais il n&apos;est pas toujours simple de faire le lien entre un comportement suspect et un bug dans cette liste.&lt;/p&gt;&lt;p&gt;Par exemple en développant la nouvelle version de ce site, je me suis trouvé face à plusieurs problèmes qui ont nécessité l&apos;inclusion de patchs issus du &lt;a href=&quot;http://pubsvn.ez.no/websvn2/listing.php?repname=nextgen&amp;path=/&amp;sc=1&quot;&gt;SVN&lt;/a&gt;
.&lt;/p&gt;&lt;a name=&quot;eztoc214894_1&quot; id=&quot;eztoc214894_1&quot;&gt;&lt;/a&gt;&lt;h2&gt;Les cache-block qui n&apos;expirent pas&lt;/h2&gt;&lt;p&gt;Il s&apos;agit du &lt;a href=&quot;http://issues.ez.no/12175&quot;&gt;bug #12175&lt;/a&gt;
 qui empêche l&apos;utilisation &lt;a href=&quot;http://ez.no/doc/ez_publish/technical_manual/4_0/reference/template_functions/miscellaneous/cache_block&quot;&gt;des cache-block expirant avec une sous-arborescence&lt;/a&gt;
. Pour règler ce problème sans passer à la version 4.0.1rc1 il faut appliquer 3 patchs successifs sur l&apos;arborescence d&apos;eZ Publish 4.&lt;/p&gt;	&lt;pre class=&quot;bash&quot;&gt;$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/cd&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;cd&lt;/span&gt;&lt;/a&gt; /tmp
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/wget&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;wget&lt;/span&gt;&lt;/a&gt; http://pwet.fr/content/download/&lt;span style=&quot;color: #cc66cc;&quot;&gt;71716&lt;/span&gt;/&lt;span style=&quot;color: #cc66cc;&quot;&gt;214901&lt;/span&gt;/file/patch_cache_block_&lt;span style=&quot;color: #cc66cc;&quot;&gt;12175&lt;/span&gt;.&lt;a href=&quot;http://pwet.fr/man/linux/commandes/tar&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;tar&lt;/span&gt;&lt;/a&gt;.gz
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/tar&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;tar&lt;/span&gt;&lt;/a&gt; -zxvf patch_cache_block_&lt;span style=&quot;color: #cc66cc;&quot;&gt;12175&lt;/span&gt;.&lt;a href=&quot;http://pwet.fr/man/linux/commandes/tar&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;tar&lt;/span&gt;&lt;/a&gt;.gz
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/cd&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;cd&lt;/span&gt;&lt;/a&gt; /path/to/ez/publish/
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt; -p0 &lt; /tmp/&lt;span style=&quot;color: #cc66cc;&quot;&gt;01&lt;/span&gt;_cache-block.&lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt;
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt; -p0 &lt; /tmp/&lt;span style=&quot;color: #cc66cc;&quot;&gt;02&lt;/span&gt;_cache-block.&lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt;
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt; -p0 &lt; /tmp/&lt;span style=&quot;color: #cc66cc;&quot;&gt;03&lt;/span&gt;_cache-block.&lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt;&lt;/pre&gt;&lt;p&gt;Les erreurs sur l&apos;application du &lt;a href=&quot;http://pwet.fr/man/linux/commandes/posix/patch&quot;&gt;patch&lt;/a&gt;
 sur le change log peuvent être tranquillement ignorées.&lt;/p&gt;&lt;a name=&quot;eztoc214894_2&quot; id=&quot;eztoc214894_2&quot;&gt;&lt;/a&gt;&lt;h2&gt;Les variations des images re-dimensionnées en permanence&lt;/h2&gt;&lt;p&gt;Celui la, c&apos;est &lt;a href=&quot;http://issues.ez.no/12386&quot;&gt;un bug vicieux&lt;/a&gt;
, on s&apos;en rend compte lors de la mise en production quand la machine est à plat par tous les &lt;a href=&quot;http://pwet.fr/man/linux/commandes/convert&quot;&gt;convert&lt;/a&gt;
 (ou apache si on utilise GD) en train de générer &lt;a href=&quot;http://ez.no/doc/ez_publish/technical_manual/4_0/reference/datatypes/image&quot;&gt;les différentes variations&lt;/a&gt;
 encore et encore. 80 de &lt;a href=&quot;http://pwet.fr/blog/load_average_ou_charge_d_une_machine_unix_linux&quot;&gt;load average&lt;/a&gt;
 sur ma pauvre Dedibox, elle a du avoir chaud ;-)&lt;/p&gt;&lt;p&gt;Là un seul patch est nécessaire et c&apos;est immédiat et magique sur la charge de la machine&lt;/p&gt;	&lt;pre class=&quot;bash&quot;&gt;$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/cd&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;cd&lt;/span&gt;&lt;/a&gt; /tmp
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/wget&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;wget&lt;/span&gt;&lt;/a&gt; http://pwet.fr/content/download/&lt;span style=&quot;color: #cc66cc;&quot;&gt;71717&lt;/span&gt;/&lt;span style=&quot;color: #cc66cc;&quot;&gt;214904&lt;/span&gt;/file/image_variations.&lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt;
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/cd&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;cd&lt;/span&gt;&lt;/a&gt; /path/to/ez/publish
$ &lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt; -p0 &lt; /tmp/image_variations.&lt;a href=&quot;http://pwet.fr/man/linux/commandes/patch&quot;&gt;&lt;span style=&quot;color: #000066;&quot;&gt;patch&lt;/span&gt;&lt;/a&gt;&lt;/pre&gt;&lt;p&gt;J&apos;ai pas eu d&apos;autres bugs bloquants (enfin je les ai pas encore remarqué :)), j&apos;en ai d&apos;ailleurs découvert un sur &lt;a href=&quot;http://issues.ez.no/13449&quot;&gt;le SmartCacheClear avec les keywords&lt;/a&gt;
, la correction est dans &lt;a href=&quot;http://issues.ez.no/13449&quot;&gt;le rapport&lt;/a&gt;
 et tient sur une unique ligne.&lt;/p&gt;</description>
    </item>
    <item>
      <pubDate>Wed, 06 Aug 2008 12:37:28 GMT</pubDate>
      <author>Community news (ez.no)</author>
      <title>eZ Publish 4.0.1rc2 &amp; 3.10.1rc2 released</title>
      <link>http://ez.no/developer/news/ez_publish_4_0_1rc2_3_10_1rc2_released</link>
      <description>
&lt;p&gt;
We are happy to announce the release candidates of eZ Publish 4.0.1 and 3.10.1. These releases carry fixes for about 290 (!) different issues since their initial version.
&lt;/p&gt;

&lt;p&gt;
Included in these new releases is a dedicated extension to migrate custom URL aliases and as much as possible of the URL history elements for existing 4.0.0 and 3.10.0 sites.
&lt;/p&gt;
</description>
    </item>
    <item>
      <pubDate>Wed, 06 Aug 2008 09:58:11 GMT</pubDate>
      <author>Kristof Coomans</author>
      <title>eZpedia DNS problems</title>
      <link>http://blog.coomanskristof.be/2008/08/06/ezpedia-dns-problems/</link>
      <description>There seems to be some problems with the DNS for the eZpedia community wiki at ezpedia.org. We&amp;#8217;re trying to get it up and running again as soon as possible. In the meantime, you can add ezpedia.org with IP 85.19.74.82 to your HOSTS file so you can still reach it.
</description>
    </item>
    <item>
      <pubDate>Tue, 05 Aug 2008 19:48:30 GMT</pubDate>
      <author>Damien Pobel</author>
      <title>pwet 2.0</title>
      <link>http://pwet.fr/blog/pwet_2_0</link>
      <description>&lt;p&gt;Nouveau design, nouvelles couleurs, nouveaux templates, nouveaux bugs peut-être mais toujours &lt;a href=&quot;http://pwet.fr/tags/keywords/weblog/ez_publish&quot;&gt;eZ Publish&lt;/a&gt;
 ! ça me démangeait depuis un moment, je repoussais toujours en attendant l&apos;intégration &lt;a href=&quot;http://ezcomponents.org/docs/tutorials/Template&quot;&gt;du composant Template d&apos;eZ Components&lt;/a&gt;
 bien plus performant mais vue &lt;a href=&quot;http://pwet.fr/blog/ez_conference_2008&quot;&gt;la nouvelle roadmap d&apos;eZ Publish et le projet V&lt;/a&gt;
, ce n&apos;est pas encore pour tout de suite !&lt;/p&gt;&lt;p&gt;J&apos;espère donc que c&apos;est plus clair et lisible, moins buggé sous Internet Explorer notamment (fini les &lt;a href=&quot;http://www.positioniseverything.net/explorer/peekaboo.html&quot;&gt;Peekaboo&lt;/a&gt;
 normalement) et surtout bien plus performant avec une gestion des caches plus fines (oui j&apos;ai appris quelques trucs depuis &lt;a href=&quot;http://pwet.fr/blog/ouverture&quot;&gt;Août 2006&lt;/a&gt;
).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>