Drupal Blogs, Pictures, and more on WordPress

Welcome To My Blog

Ovvero come insegnare ad un computer a leggere opere di narrativa. E a farci dire a quale genere letterario appartiene. I’m sorry, Dave. I’m afraid I can’t read this: it’s another boring Gothic Novel.

Parto dall’articolo “Style versus expression in literary narratives” di Ozlem Uzuner e Boris Katz. Lo potete trovare in CiteSeer, la Scientific Literature Digital Library.

Qui vengono date due definizioni:

Stile: le scelte linguistiche che un autore fa lungo tutta la sua opera, indipendentemente dal contenuto.
Espressione: le scelte linguistiche che un autore fa per veicolare un particolare contenuto (nello specifico, per una particolare opera).

Stile ed espressione si differenziano quindi da un punto di vista qualitativo (uno fa riferimento al contesto, l’altro no), ma loro propongono un esperimento interessante: per identificare lo stile analizzano le diverse traduzioni fatte di una stessa opera. In questo modo si concentrano sullo stile (indipendente dal contenuto) dei traduttori, confidando nel fatto che le differenze di contenuto siano nulle o poco più (ogni traduttore lavora sulla stessa opera).

In questo modo la loro ricerca evidenzia come sia possibile riconoscere lo stile mediante l’identificazione di parole funzionali e l’espressione mediante l’analisi della sintassi.

Per fare questo tipo di analisi, quindi, non è necessario identificare parole specifiche, prese dal contesto. Non importa sapere se l’autore ha usato o meno la parola “pianeta”, perché il suo stile e la sua forma espressiva non dipendono dal contesto di cui sta parlando.

Quando si pensa al genere letterario, invece, si presume che “pianeta” aiuti, eccome: fa subito venire in mente la fantascienza, i viaggi nello spazio. Com’è possibile immaginare il genere gotico senza almeno un castello, o il romanzo rosa senza un fremito al cuore?

Eppure pare che i più recenti tentativi di determinare/attribuire in automatico i generi letterari di un testo possano funzionare anche senza cercare parole note a priori, ovvero senza crearsi un elenco di tutte quelle parole specifiche che la macchina deve individuare, contare e dunque valutare per decidere di che genere sia l’opera in analisi.

Secondo l’articolo “Machine-Classifying Novels and Plays by Genre” (https://www.stanford.edu/~mjockers/cgi-bin/drupal/node/27) il gotico, la fantascienza e il romanzo rosa (e tutti gli altri generi letterari, ovviamente) sono riconoscibili

• per il loro uso della punteggiatura,
• per la costruzione delle frasi tramite congiunzioni e subordinate,
• per l’utilizzo di aggettivi pronominali (interrogativi, numerali, indefiniti, possessivi…)
• per l’utilizzo dei pronomi personali.

Elencando insieme punteggiatura, congiunzioni, subordinate, interrogativi, numerali eccetera di un’opera siamo in grado di fare calcoli statistici su quanto spesso (e in che posizione) questi elementi ricorrono, così da associare tra di loro opere di narrativa (che la macchina ci restituisce raggruppate in insiemi). E questi insiemi corrispondono a quelli che noi intendiamo essere generi letterari.

Strumenti che si possono utilizzare per analizzare la narrativa:
Docuscope: http://betterwriting.net/projects/fed01/dsc_fed01.html
R: http://www.r-project.org/
Eseguire R in PHP: https://www.stanford.edu/~mjockers/cgi-bin/drupal/node/25

డిసెంబర్ రెండవ ఆదివారం తెలుగు బ్లాగుల దినోత్సవం. మీ ఊళ్ళో ఏం చేస్తున్నారీసారి? ఇంకో నెల ఉందనుకోండి.

The first book to reveal the vulnerabilities and security issues that exist in the sites that have b

In this article I wind up Packt Open Source CMS award week with the final winning announcements: Wor

The first book to reveal the vulnerabilities and security issues that exist in the sites that have been built with Drupaland how to prevent them from continuing Drupal is an open source framework and content management system that allows users to create and organize content, customize presentation, automate tasks, and manage site visitors and contributors. Authored by a Drupal expert, this is the first book to reveal the vulnerabilities and security issues that exist in the sites that have been built with Drupaland how to prevent them from continuing. The main goal of this guide is to explain how to write code that avoids an attack in the Drupal environment, while also addressing how to proceed if vulnerability has been spotted and then regain control of security.

# Paperback: 240 pages
# Publisher: Wiley (May 11, 2009)
# Language: English
# ISBN-10: 0470429038
# ISBN-13: 978-0470429037

Click Here to Download File

President Obama promised us change, and change we get.  The White House official website, whitehouse.gov, has changed its CMS (Content Management System) to the open source platform Drupal.

Drupal is, quite frankly, a pain in the butt if you don’t know any php, and aren’t comfortable learning the architecture of a site.  For most individuals who just want to blog, or have a small business website, I still think WordPress is king.  It’s easy as hell to understand and it’s quite flexible.  Nearly every site I’ve ever created I did with WordPress. I’m a mathematician, not a web developer.

But, for large websites needing lots of features or, in this case, for a large government, Drupal is well worth the learning curve.  It can do pretty well anything you want it to do.  It’s more secure than most CMS’s. And, it’s got a large community of developers backing it up.

WhiteHouse.gov’s switch is part of an effort on the part of the Obama Administration to make the white house a more interactive and “Web 2.0″ friendly place.  He is the first President to be addicted to his Blackberry after all.

If you are looking at different CMSs to set up your own website then this article might be of help.

Also read the comments and you’ll find even more CMS suggestions from the readers.

Highly reccommend this article:

http://www.goodwebpractices.com/other/wordpress-vs-joomla-vs-drupal.html

 In Feiten en Fillet op Radio 1 hoorde ik Dries Buytaert, de uitvinder van Drupal, tekst en uitleg geven (te herbeluisteren) over zijn geesteskind. Dat gebeurde n.a.v. de lancering morgen 15 november 2009 van de hernieuwde website van de koning, op de Dag van de Dynastie. De website van de Belgische monarchie zal vanaf dan op Drupal draaien. Nu, ik ben geen geek. Ik heb goed proberen te luisteren naar Dries Buytaert en (ook blogger) Koen Fillet.

Op Dries Buytaerts persoonlijke site lees ik over hem en Drupal:

  He is the original creator and project lead of Drupal, an open source social publishing system. He is co-founder and chief technology officer of Acquia, a venture-backed software company that offers products and services for Drupal. Dries is also working on Mollom, a service that helps you identify content quality and that stops website spam. People often laugh at his hair but he is cool with that.

Op Twitter werd het ‘koninklijke nieuws’ door Drupal architect Dieter Beheydt de wereld ingestuurd.

Zoals de overheid en vele anderen, grote en kleinere beroemdheden, krijgt dus ook koning Albert II een open source website. … Bij Flip Kowlier ziet Drupal er zo uit, en de world’s hardest Drupal band, de Kitten Killers, doen het zo. ‘t Is maar dat we het weten. ‘Grote’ voorbeelden trekken.

Wir haben und für ein Layout entschieden, fein, mit dem Drupal-Theming begonnen…

Derweil haben unsere Fach-Autoren Nachtschichten eingelegt, um hochwertige Inhalte in Bezug auf Krankheiten, deren Ursachen, Symptome und Behandlung zu verfassen. An dieser Stelle schonmal ein herzliches dankeschön dafür.

So wie es aussieht, gestaltet sich die Entwicklung unseres Systems an der einen und anderen Stelle doch schwieriger als gedacht, insbesondere weil wir teilweise eigene Module für Drupal entwickelt haben, die einige Unzulänglichkeiten des Systems in unserem Sinne verbessern müssen.

Wie dem auch sei – alles dauert länger, aber wird sicher gut. Gesundheitkompakt – der Ratgeber für Gesundheit. We will keep you informed about the progress.

In this article, I discuss the Packt first inaugural Open Source CMS Hall of Fame award, who won thi

This is my simple implementation of a multistep preview for any node type. It is basically a ‘

Ever seen this when in Drupal’s administration pages?

Fatal error: Cannot redeclare getnodecount() (previously declared in /var/www/sites/site.org/htdocs/includes/common.inc(1685) : eval()'d code:3) in /var/www/sites/site.org/htdocs/includes/common.inc(1685) : eval()'d code on line 9

There are a few causes for this, as mentioned on drupal.org, but the one in which you might be interested (because your error message looks more similar to mine, above, than to the drupal.org documentation) is when PHP is actually contained in a block or node body. That’s something you should suspect if you see the above error message referring to PHP’s eval() function.

To fix this, do something in MySQL like

SELECT nid
FROM node_revisions
WHERE body LIKE '%getnodecount%';


And edit the offending nodes in Drupal with a URL such as
http://example.com/node/123/edit

Está em fase de finalização o novo Portal Consignum. Através deste portal o usuário poderá participar ativamente de nossos conteúdos. Veja as funcionalidades:

• Comentar em nossas publicações;
• Fazer downloads das legislações vigentes;
• Assistir vídeos sobre a consignação;
• Ter notícias atualizadas sobre o sistema;
• Todo conteúdo em RSS.

Todos os ocnvênios poderão utilizar nossas novas funcionalidades.

Aguarde…

AWstats和Google Analytics目前都不支持用Title显示URL信息，以Drupal网站为例，经常看到一堆node/1, term/32之类没有意义的东西出现的排行榜，或是出口、入口地址，非要点击过去才能知道是什么。

所以最好利用Path Auto模块自动生成URL Alias，把Title自动映射为URL，便于在日志统计分析中一目了然。

可是，结果出现的确是以%B4%A3这样的Plain Text。

为此研究了一下awstats.pl的源代码，修改一下ShowURLInfo函数：

前几行改为

my $nompage;
if ($PluginsLoaded{‘DecodeURL’}{‘decodeutfurl’}) {
$nompage = CleanXSS(
DecodeURL_decodeutfurl($url, $PageCode || ‘gb2312′));
}
else {
$nompage = CleanXSS($url);
}

然后修改Awstats的配置文件，加入

LoadPlugin=”decodeutfurl.pm”

并且把这个decodeutfurl.pm文件放到/plugin目录下，就应该OK了。

刷新一下看看，enjoy。

现在AWStats除了无法显示单个用户访问明细，其他的效果还是不错的

What Exists

Currently, the commenting system on the Economist.com is limited and straightforward.  Registered users are able to comment on articles and blogs when they are signed in.  Usernames appear as a link in every post.  When clicked, this link leads to a separate page which tallies the user’s history of posts.

Comments appear flat on the page, either in chronological or reverse chronological order.  Users can also select a 3rd option of “Readers’ most recommended” viewing order.  Posts appear 20 at a time per page, regardless of length.

Users cannot reply directly to each other within the thread.  They cannot upload video or media within a post.  Hyperlinks posted by users will navigate away from The Economist’s page in the browser.

No commenting is available on The Economist’s videos.

What We Recommend

1. Enable voting on comments

• Drupal’s fivestar voting module

2. Enable embedding of video/images in comments

• Drupal Video module (allows users to submit videos)
• Drupal Riffly module (allows users to video or audio record their comments)

3. Allow users to share content through social networking sites

• Drupal Share module

4. Users receive e-mails when someone comments on their post

• Drupal Comment Notify module

5. Create user profiles

• Drupal Profile module

What Exists

Currently, the commenting system on the Economist.com is limited and straightforward.  Registered users are able to comment on articles and blogs when they are signed in.  Usernames appear as a link in every post.  When clicked, this link leads to a separate page which tallies the user’s history of posts.

Comments appear flat on the page, either in chronological or reverse chronological order.  Users can also select a 3rd option of “Readers’ most recommended” viewing order.  Comments can be flagged for abuse.  Posts appear 20 at a time per page, regardless of length.

Users cannot reply directly to each other within the thread.  They cannot upload video or media within a post.  Hyperlinks posted by users will navigate away from The Economist’s page in the browser.

No commenting is available on The Economist’s videos.

What Should Be Changed

Several of our recommended changes are already being implemented as the Economist.com moves to Drupal.  Among those are (1) featured comments, (2) threaded-style layout, (3) comments tagging, (4) a ratings system, and (5) an e-mailed response to commenters when someone replies to them.

We will elaborate on these improvements only where we have a specific suggestion.

We believe users should have the ability to reply to one another, in addition to the articles.  Commenters are already directing posts at each other without a conducive layout.  Threaded comments should solve most of this problem.

Users should be given the opportunity to identify themselves, in a way that fosters online community.

They should also be able to intuitively post text, audio, photo, video, and hyperlinks, and share content they like with social networking and bookmarting sites.

Examples Of Other Sites’ Systems and Drupal Modules

1. Commenters reply directly to each other in threaded layout

• Gawker uses the Twitter “@” reply method, and replies are organized within the comment they are referring to

• NY Times health care conversations: replies become an entirely new thread of their own

2. User identification within comments

• Drupal Profile module allows a users to share personal info using a number of different fields (single line, drop-down menu, list).
• This could include information such as name, age, location, political preference, etc.

3. Voting on comments

• Many sites already allow this in different  formats, including voting comments “up” or “down”, or a ranking system.
• The Huffington Post allows users to become “fans” of each other, as well as marking comments as “favorites”

• Drupal Fivestar Voting module could be used to enable users to vote on a comment through a rating system.

4. Word limits

• Consider introducing word limits for each comment (300 words), then enabling the continuation of more in depth discussions in separate spaces.
• e.g. Gawker Open Forums: by using Twitter style hashtags (#tips) in a comment, a new url is generated with that tag (www.gawker.com/tag/tips), for people to continue their conversation

5. Embedding of video/images in comments

• Gizmodo allows users to embed images or  YouTube videos in their comments.

• Drupal Video module allows users to submit their own videos, not just those hosted on YouTube
• Drupal Riffly module allows users to video or audio record their responses directly into the comments box

6. Comments on same page as article, for easy interaction

• By extension, allow users to directly quote from the article, or others’ comments.
• Drupal Quote module has this feature, so a quote is clearly marked within a user’s response

7. Users sharing content through social networking sites

• Drupal Share module allows users to share content through social networking and bookmarking sites, i.e. Twitter, Facebook, Digg, etc.

What We Recommend

We recommend the following:

(1) A threaded comments layout that allows users to reply directly to each other in addition to Economist content

(2) Provide incentives for online users by featuring comments not only on “Channel” pages but also in the print edition

(3) Introduce a “fivestar” rating system that ranks comments according to user voting.  Consider having a separate “Economist-ranked” option.

(4)  Allow users to identify themselves in posts.  This would take the form of an optional user profile to be completed upon registration.  This could include:

• Location (or Hometown)
• Occupation
• Political Affiliation
• Personal Website
• Photo or Avatar

Each field should be optional.  Users should be able to post selected personal info alongside comments, or have their username link back to a separate profile page.

(5) Impose a visible word-limit on posts (i.e. only 300 words will appear in the display page), encouraging commenters to be thoughtful and concise.  Invite users to participate in related debates or events, either in the article and with an invite after they post a comment.

(6) Keep comments thread on the same page as the article.  Make sure hyperlinks open up a separate tab/window in user’s browser rather than navigate away from the Economist page.

(7) Allow users to embed video and other media easily into posts.

(8) Allow users to share content with links to social networking and bookmarking sites.

(9) Enable commenting on Economist video and multimedia content.

There are numerous ways to integrate Magento with Drupal. Here I will share my experiences while working on that with very smart people at Optaros. I don’t take credit for all the points in this post, because they are the product of the whole team.

The motivation for this kind of integration is the innovative look into where e-commerce is moving. To get a grasp of it look at OCentric. To keep it short, content is free advertisement for products. It allows customers to get more input about products and provides the meat for search engines to index.

Briefly, there are several main approaches to integrate Drupal and Magento:

1. let Magento be the main component, while leaving Drupal just as a subcomponent
2. let Drupal be the main component, and have Magento as an e-commerce  module
3. let  both Magento and Drupal be main components

These are general approaches and each of them have different pros and cons. They will be further detailed by usecases, complexity, technicalities, etc. in the following sections.

Moreover, we will release much of the code as open source, so it’s not only a theoretical discussion here:)

Magento as the Main Component

This is probably the most acceptable approach in terms of implementation complexity. Moreover you can choose different level of complexity to implement.

The straightforward solution is to integrate on the service layer. Meaning that whenever we are on the e-shop product page we have to call a Drupal service to bring related content, for instance blog posts. The same holds for category pages. How to do that:

• Create a Drupal module that allows you assigning categories and products  to a content node in Drupal
• Implement XML-RPC client on Magento side and use it to talk to services on Drupal in order to pull the content (e.g. using view.get or node.get funuctions)
• Rewrite the category and product controllers on Magento to take the content from Drupal into account

There are some challenges in taking this way. They are mainly for those who want to implement features in a generic way. Specifically, whenever you add a CCK field or a feature like rating to a content type, you have some work to do on the Magento side. Namely, you need to modify layout and write templates to handle this additional data coming from Drupal. Hence it’s pretty cumbersome to use Drupal community contributed modules as you need to do some coding on Magento side for every new Drupal feature. This is quite easy when the content from Drupal is read-only, but as soon as you want commenting, rating, flagging, etc. it becomes an issue, because you need to not only redo rendering on Magento but also map the functionality.

A more complex path to take  is to integrate the whole Drupal rendering engine into Magento, however, this means a very tightly coupled architecture… Still, if you plan to use many many many of the Drupal features it may make sense. This will require writing a Drupal module for Magento that will adapt every Drupal core function to Magento. Could end up as a very complicated solution.

We chose the XML-RPC because of the given time frame and specific requirements. Normally a product or a category will be associated with a very specific set of content types, and therefore the fully generic solution may not pay off.

By the way there is already a CMS module for Magento as part of the core. And the question is why would one want to struggle integrating Drupal instead of using that CMS module? Moreover, with enterprise 1.6 version of Magento the module offers quite cool features. Some things from the top of my head to consider:

• Drupal has a solid community, and it is more stable and feature-rich than the Magento CMS module will ever be (of course it’s good as soon as you make the Drupal-Magento integration reasonably flexible)
• There is the CCK module that allows to very quickly add additional fields to a content type and make it available to the content producing team
• Content versioning, workflow, etc. is easy in Drupal
• …more ?

Drupal as the Main Component

This approach has been already taken by others and you can start digging for it here. We’ve tried out the available modules but didn’t stick with them… Basically there the implementation is based on the notion of synchronizing Magento products, categories, orders, etc.  into Drupal using a cron job.

In general, although Drupal-as-the-main-component approach in the end may give a lot of  flexibility, it may be too complex to implement. Imagine that the whole Magento frontend functionality needs to be rewritten for Drupal. Magento would then only be an e-commerce backend (the admin part) accessible via Web services. Of course you’d be able to use plenty of Drupal modules as well as flexible templating without any hassle, have better performance, and many other goodies but it just looks too expensive to implement.

Still, bringing only a part of Magento into Drupal makes a lot of sense (as in that module that synchronizes products and orders into Drupal using cron job). In this case it’s a decision to make whether the site is more about content or about commerce. When it’s about content, then you don’t really care about SEO for products, fancy business logic, etc.

Both Mangento and Drupal as the main Components

This is reasonable when the content will be displayed on the Drupal site and e-shop on the Magento site. Meaning that no proxying for content happens behind the scenes. So if a product has a blog post attached, then on the product page you’ll have a link (maybe even the post itself loaded using Ajax call) and clicking it will open a Drupal page with that blog post.

One of the challenges here is to maintain two different themes in order not to harm user experience. So that when the customer clicks on the blog link inside the product page the blog is displayed with the same look and feel as the shop. For that you can’t avoid coding on two different frameworks. Apart from theming SEO will have to be also maintained on both components.

Another challenge would be the ability to mix content with product information on the same page. Some kind of communication on the service layer will be necessary for that, which means that it’s not really reasonable to use this dual approach with such a usecase present.

It may make sense, however, to take this path when there are only some of the things to be shared between both components, e.g. users, and everything else is completely separate. For example, when a company has an e-commerce site, a customer community site, and a corporate site.

Additional Points for Integration

The end user display is only one part of the story. When you integrate this kind of monster systems to work seamlessly you get trapped with other things besides templating.

One of them is single sign on. A good thing to do here is to use CAS. Drupal already has the CAS module. Magento, however, needs one (we’ve been writing one). The good news that all the low level protocol implementation is available for PHP as open source.

Another thing is search. Independently of the integration approach chosen eventually you want to search for products and content in the same search box. This may become pretty challenging but it’s not impossible. We’ve got a proof of concept for the store front in Magento, where we leverage Solr search. It performs really well for our suggest box functionality.

There are numerous ways to integrate Magento with Drupal. And here I will share my experiences while working on that with very smart people at Optaros. asdfa sfd

asdf adsfasdf asdfasdf

In this article, I look into the major changes to Drupal coming with the release of Drupal 7. This v

A Paróquia da Santíssima Trindade recebe há três meses a assessoria do Web Master Marc Storms para a construção do site  www.trindade.org . A Igreja da Santíssima Trindade está localizada na região central de São Paulo, da maior cidade da América do Sul. Nesse sentido buscávamos um site que mostrasse um diferencial dentre os demais sites de igrejas já existentes. O site deveria não só servir aos paroquianos mas também às pessoas comuns, não muito “entendidas” sobre o mundo das igrejas. Nesse sentido o trabalho profissional de Marc Storms nos ajudou a concretizar nossos objetivos.

Tínhamos a concepção de que o site da Paróquia deveria espelhar o máximo da vida ou do jeito de ser das pessoas que freqüentam a nossa igreja. Queríamos compartilhar o que tínhamos de melhor com às pessoas que estão fora do ambiente da igreja. Queríamos algo que complementasse os textos, com sons, com imagens, movimento… Um site que fosse também dirigido conjuntamente por uma equipe responsável da liderança paroquial. O site deveria ser tão bom e tão gostoso de se visitar  que chegaria ao ponto de estimular o desejo dos visitantes internautas de querer conhecer pessoalmente nossa Paróquia.

Nossa igreja é muito dinâmica, com  muitas atividades,  e sempre precisamos colocar no ar as notícias no tempo certo e com boa qualidade.  O Marc criou formas bastante práticas e rápidas para que nossa equipe pudesse contribuir com matérias para o site, se mantendo sempre atualizado.

Nessas três semanas no ar tivemos um bom número de visitantes   e esperamos manter a qualidade e o profissionalismo na proposta do novo site.

Arthur Cavalcante+, Reitor da Paróquia da Santíssima Trindade

arthur@trindade.org