Subscribe for updates on posts
Be the first to read the latest news

Drupal Commerce for ePayment module

November 27th, 2011 by Ioan Cocan in Drupal

Inspired by Drupal philosophy of contributing code and modules for the community, we have released a module that provides ePayment support in Drupal Commerce. Available here.

Just install the module, configure standard ePayment parameters and you’re ready to process payments. You can also set a debug mode for the IPN confirmations and switch between production and test mode from the Drupal admin, very handy for a Drupal live site.

Feel free to extend it and contribute some more for the Drupal community.


Taxonomy additions Drupal module

February 1st, 2011 by Ioan Cocan in Drupal

Our first Drupal module: http://drupal.org/project/taxonomy_additions ads various additions to the core Taxonomy module. Meet Andrei (amateescu at tremend.ro) in Brussels at Drupal Developer Days 2011, 4-6 February.[QR]


How to move Drupal to a subdirectory and keep the links

October 20th, 2009 by Bogdan Nitulescu in Drupal

The usual way for Drupal is to have it live in the root of your web site. It’s all nice if the only thing on your site is Drupal, but it gets very cluttered when you have other top-level directories.

One customer had his corporate site at, say, “www.example.com“, and his customer support pages at “www.example.com/support“.  We wanted to keep the application in the “support” directory, move all the drupal directories under “corporate“. And keep the old links working.

First we had to let Drupal know that, even if it’s been relocated to “corporate”, the URL still remains the same. Do it in “corporate/sites/default/settings.php“:

$base_url = 'http://www.example.com';

Then tell Apache that Drupal has moved. Put these rewrite rules in .htaccess in the root of your web site.

  RewriteEngine on
 
  # Rewrite www.example.com to the Drupal home page: www.example.com/corporate/index.php
  RewriteRule ^$ corporate/index.php [L]
  # Let Drupal process paths like www.example.com/corporate/about
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule ^corporate/(.*)$ corporate/index.php?q=$1 [L,QSA]
 
  # Search for real Drupal files that moved, 
  #  (e.g. www.example.com/flash/intro.swf to www.example.com/corporate/flash/intro.swf)
  RewriteCond %{DOCUMENT_ROOT}/corporate/$1 -f
  RewriteRule ^(.*)$ corporate/$1 [L]
 
  # Let Drupal process all paths that are not real files and directories, like www.example.com/about
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !=/favicon.ico
  RewriteRule ^(.*)$ corporate/index.php?q=$1 [L,QSA]
 
  # What's left are real non-Drupal pages and directories, like www.example.com/support

Xaraya to Drupal Migration Script

September 11th, 2009 by Julia Biro in Drupal

Using some functionalities from this script I managed to port
a Xaraya 1.4 installation to Drupal 6.13.

The script performs the following tasks:

  • imports users
  • imports articles and comments
  • imports forums and comments
  • imports content types
  • imports vocabularies and terms
  • imports files

The first thing I’ve done was to eliminate the sequences table, which is deprecated starting from Drupal version 4.

Next, when managing categories, I’ve used the xaraya categories with parent id equal to 0 as Content Types and Vocabularies and inserted all the other as terms associated with the vocabulary.

The term hierachy is created by running a script on the term_hierarchy table setting parent_id 0 for the first child and the original parent_id for the next ones.

With regard to files and images, Inserting them into the ‘files’ table is not enough – the FileField
and ImageField Drupal modules are mandatory in order to associate a field with a node. (this is still work in progress)

One last note: in order to maintain database integrity, the original id-s must be used in all tables.

Click here to download the script