Submitted by Karthik on 1 January, 2007 - 04:28
My default Kubuntu install needed some tweaking to get Clean URLs working (in Drupal 5, Apache 2). This is a quick guide to getting this sorted for other users out there:
First off, the mod_rewrite module isn't enabled by default. To enable it, type
sudo a2enmod
and add rewrite as the module you would like enabled. (You can also enable the expires module which is also used by Drupal, but do it later).
Restart apache:
sudo /etc/init.d/apache2 force-reload
Check if the clean URLs test (in ?q=admin/settings/clean-urls) works. If not, jump to the /etc/apache2/sites-enabled directory and check what your setup is like. By default, you should just see the 000-default link here. (Backup first and) Edit the file:
Submitted by Karthik on 23 May, 2006 - 21:18
Submitted by Karthik on 1 May, 2006 - 20:30
[quote]After more than a year of development we are ready to release Drupal 4.7.0 to the world. More than five years, 13 major releases, 30+ servicing firms employing 100+ Drupal professionals, 300+ third party modules, and over 55,000+ Drupal powered sites later, Drupal 4.7.0 is finally here and it rocks![/quote]
Woohoo!
More here.
Expect to see some updates here soon!
-K
Submitted by Karthik on 23 April, 2006 - 18:26
Another patch that didn't get into 4.7 was a simple (yet important) one that created an index for the locale database. The locale module can suck you dry in terms of DB calls, so this can provide a huge boost for a site using it. The index is added on a BLOB field named 'source' with a length of 30-40 (AFAIK, this number was just picked at random).
-K
Submitted by Karthik on 23 April, 2006 - 13:18
Due to a session fixation patch, a usability bug has been introduced when a user tries to access multiple installations of Drupal on the same box (not necessarily multi-site installations). The user can only stay logged into one site at any point in time as the session ID and the related cookie is regenerated upon login.
Submitted by Karthik on 4 February, 2006 - 21:36
Why the dearth of new stories in the last couple of weeks? Too much work and too little time. I have however, spent some time in the last week developing some new stuff for when Drupal 4.7 comes out. I will very likely upgrade quillem.com as soon as it hits RC status :)
-K
Submitted by Karthik on 23 November, 2005 - 12:10
Added in a few updates to the site a couple of days ago:
- Added the global broadband comparison table.. *phew* this was a lot of work..
- Updated Hathway pages with the plans from their plan pages. Also amended my review to put them in a little more positive light as speeds have been much better off late.
- Removed Net4India from the broadband page and move it to the Other ISPs page. The responsiveness of their customer service divisions is just positively .. bovine :/
This is a work (very much) in progress. The following is the MySQL DB layout for the 4.7 HEAD..
If you notice any errors, please post a message to let me know. Here goes..
access
Holds a list of access rules added via admin/access/rules
| Field |
Type |
Null |
Default |
Comment |
|---|
| aid |
tinyint(10) |
|
|
Unique sequence ID for each access rule. |
| mask |
varchar(255) |
|
|
A string to match the rule against. |
| type |
varchar(255) |
|
|
Denotes what field to match the rule against. Example values include user/email/host which match against the user name/email address/host address respectively. |
| status |
tinyint(2) |
|
0 |
Indicates whether this is an "allow"[1] or "deny"[0] rule. |
accesslog
Holds a list of page accesses and associated user details.
Submitted by Karthik on 10 November, 2005 - 09:14
[ramble]
I've been working on a couple of Drupal modules, and just wanted to pen down some of the stuff that either doesn't make any sense to me or has just plain annoyed me for a while now..
- auto_increments: With Drupal supposedly ANSI SQL compliant, I don't know why half the tables have auto_incremented fields, even though the actual code relies on the sequences table to manually take care of increments.
- Forums table: Drupal's basic premise is that *everything is a node*. But yet, it has a Forums table that does what the node_term table does, virtually identically. In 4.6.3, both tables have the same fields - nid, tid. However the current HEAD version adds the vid to the forum table, for reasons as yet unfathomed.
So, while it would have been excellent to treat all data as nodes, making their management so much more easier, I now have to treat all forum data as special nodes :/
Submitted by Karthik on 12 October, 2005 - 14:55
Site Update: Added the google sitemap module yesterday - looks pretty nifty, except I'm not too sure that it's handling node type priorities very well - not sure yet.
I'm also working on my first Drupal module, and intend to perhaps write a walk-through-or-two that outlines the basics of module writing. The online docs are (as is the norm with Drupal) just plain shoddy.
-K
Pages
|
Recent comments