Jeg ser ikke noe vits med å gjøre g.d.o/Norway om til en "link farm". Etter hvert har denne gruppen blitt en side hvor innlegg og kommentarer stort sett minner oss om søppelpost. Har bestemt meg for lenge siden og ikke ha e-post-oppdateringer fra denne gruppen, tror det er mange av oss som har gjort det samme og/eller flere vil gjøre det samme.
Grunnen til at vi er her, er fordi vi utvikler/administrerer et eller flere Drupal-nettsteder. Mange av oss blogger og formidler nyheter om Drupal i hver vår Drupalside. For og imøtekomme behovet for markedsføring av egne sider om Drupal, laget jeg i går kveld en ny tjeneste for Drupal-blogger i Norge, som etterligner "Drupal Planet".
Ved og vise ønsket vårt om og samle ressurser, er enda en mulighet rett foran oss. Har lagt til de nettstedene som er listet på GDOs forside og technorati (tag:Drupal). Dere som skriver om Drupal, vær vennlig og gjør oss oppmerksom på ditt nettsted. Skriv gjerne et innlegg på denne siden hvis du vil at ditt nettsted inkluderes.
Er jo litt ironisk å skrive linken her etter og ha "mumlet om link farm"! Her er hverfall linken til Norges versjon av "Drupal Planet ". Forslag? si i fra :-)
NorwayDisse sidene blogger og formidler nyheter om Drupal: (i alfabetisk rekkefølge)
Lenkene over vises på forsida til g.d.o/norway. Rediger blokka for å legge inn flere ressurser. (La kommentaren med !--break-- stå, den sørger for at dette avsnittet ikke vises på forsida.)
Norwaythe first beta of the site is online now
http://drupalcamp.dk/
go register post sessions etc etc etc :)
Ser at vi er fjerne fra blokken "Bidra til det norske Drupal-miljøet".
Kunne jeg fått en forklaring på hvorfor?
Oppdaterte bokmål språkfiler, som vi alle har jobbet for, skal etter planen sendes inn til CVS den 7.okt. Disse språkfilene har vi tenkt å gi ut som Norsk Bokmål 6.x-1.0 (mao. ikke en dev-versjon lenger).
Håper dere tar dere tid til og besøke lokaliseringstjeneren før 7. okt og bidra, så håper vi at nb 6.x-1.0 blir en 100% oversettelse av Drupal 6.x. Les mer
Odd-inge
Drupal Norge
Det offisielle norske nettstedet for Drupal
Ok. Drupal 6 is probably the best thing since bread came sliced. Views 2, the new and improved CCK, and the updater—it’s like updating your anti virus—has made life so much easier. Updating Web application frameworks has never been easier.
This updater alone is incentive enough to upgrade your Drupal 4.x and 5.x installations to Drupal 6.x. Unfortunate it is then that this moat to be crossed is filled with non-upgraded module crocodiles and inexplicable PHP error sharks.
There are two approaches to converting a Drupal 5.x site to 6.x:
1. Upgrading: For this, all contrib. modules installed in your 5.x better be ported to 6.x, and also pray that Watchdog has encountered no life-threatening PHP errors. That periodic cron runs, database updates, & zilch-modification of core modules were a must go without saying.
2. Migration: Setup a crisp, clean Drupal 6.x site, and painstakingly port all data from your 5.x behemoth to your 6.x kiddo. Migration can be performed either manually (pray, lord, pray if your site has more than 500 nodes) or through scripts.
Although approach 1, if it works without spewing any errors, is enough to incite a hallelujah from even the most ardent of the non-believers, we all know how rare it is. And the pre-requisites to it are just too many and too hard to fulfill.
The only solution in cases where an upgrade is not possible, then, is the use of automated migration scripts. Currently, there is no such unified migration script available. I have broken down the script I used to migrate my 5.x site to 6.x for the migration of users, simple-content-type posts, comments, taxonomy, & forum posts. Migrating the theme itself (blocks, nodes, templates, etc.) would require one to get their hands dirty with PHP.
Before we begin, we need our PHP migration script to set certain variables:
< ?php
set_time_limit(0);
//MySQL globals
$mysql_server = "localhost";//change this server for your Drupal installations
$mysql_user = "root";//Ideally, should be root
$mysql_pass = "pass";//Corresponding password
$conn = mysql_connect($mysql_server,$mysql_user,$mysql_pass);//MySQL connection string
//If your 5.x and 6.x installations reside on different servers, you will need two sets of server names, usernames, and passwords.
?>
Also, in my scripts, tables prefixed “drupal.” and “timesnow.” belong to the 5.x and 6.x sites, respectively. Please change these accordingly for your databases.
Lastly, these scripts are not optimized with regard to execution. So do not expect unified inserts to insert multiple tuples.
User migration script:
This script, currently, only migrates users, e-mail addresses, uids, and passwords. It does not take care of the profile fields, which can be handled through other customized scripts as profile fields for each installation can differ. It does not import “usernode” content type either. This is coz’ usernodes are typically not required in 6.x, as user profile pages can be styled using tpl.php files themselves. Also, it is important that the uids from your orignal installtion be migrated to your current installation accurately coz' comments and nodes that we will migrate later on are linked to the users through these uids.
There are absolutely no differences between the Users table in 5.x and 6.x. Both of them have the same 18 fields. So you can go ahead and use the following script without even thinking:
< ?php
//first, we delete all users, if any, from the new table, except for the admin
$query = "delete from timesnow.users where uid not in (0,1)";
mysql_query($query);
print "User table cleared. <br />";
//now we start inserting users into the new table
$query = "select * from drupal.users where uid not in (0,1)";
$queryresult = mysql_query($query);
while ($row = mysql_fetch_row($queryresult)) {
$query = "insert into timesnow.users values('" . $row[0] . "','" . $row[1] . "','" . $row[2] . "','" . $row[3] . "','" . $row[4] . "','" . $row[5] . "','" . $row[6] . "','" . $row[7] . "','" . mysql_real_escape_string($row[8]) . "','" . $row[9] . "','" . $row[10] . "','" . $row[11] . "','" . $row[12] . "','" . $row[13] . "','" . $row[14] . "','" . $row[15] . "','" . $row[16] . "','" . $row[17] . "')";
if (!mysql_query($query)) {
print $query;
}
$ucnt += 1;
}
print $ucnt . " users inserted.";
?>
An easy one that was, wasn’t it. Now, for some taxonomy.
[Note: You can even take a backup of the old Users table using mysqldump and restore it into the new one. Just make sure that you delete the insertion statements for UIDs 0 and 1.]
Migrating taxonomy:
Now, this is the tricky part. Broken down, the minimal unit of taxonomy data in Drupal is a “term,” which has an associated “tid” (term id). Terms can be fixed taxonomies or free tags. Each node (if applicable) and forum post has an associated tid, which maps it to the term that the user has assigned to it. Therefore, it is imperative that this data is migrated accurately.
The migration script for taxonomy will migrate the hierarchies, term-node relations, vocabularies, etc.:
< ?php
$query = "truncate timesnow.vocabulary";
mysql_query($query);
print "Vocabulary table cleared. <br />";
$query = "truncate timesnow.vocabulary_node_types";
mysql_query($query);
print "Vocabulary_node_types table cleared. <br /><br />";
$query = "truncate timesnow.term_data";
mysql_query($query);
print "Term_data table cleared. <br />";
$query = "truncate timesnow.term_hierarchy";
mysql_query($query);
print "Term_hierarchy table cleared. <br />";
$query = "truncate timesnow.term_node";
mysql_query($query);
print "Term_node table cleared. <br />";
$query = "truncate timesnow.term_relation";
mysql_query($query);
print "Term_relation table cleared. <br />";
$query = "truncate timesnow.term_synonym";
mysql_query($query);
print "Term_synonym table cleared. <br />";
print "<br />";
$query = "select * from drupal.vocabulary";
$queryresult = mysql_query($query);
while ($row = mysql_fetch_row($queryresult)) {
$query = "insert into timesnow.vocabulary values('" . $row[0] . "','" . mysql_real_escape_string($row[1]) . "','" . mysql_real_escape_string($row[2]) . "','" . mysql_real_escape_string($row[3]) . "','" . $row[4] . "','" . $row[5] . "','" . $row[6] . "','" . $row[7] . "','" . $row[8] . "','" . $row[9] . "','" . $row[10] . "')";
if (!mysql_query($query)) {
print $query;
}
}
print "Vocabulary plugged in.<br />";
$query = "select * from drupal.vocabulary_node_types";
$queryresult = mysql_query($query);
while ($row = mysql_fetch_row($queryresult)) {
$query = "insert into timesnow.vocabulary_node_types values('" . $row[0] . "','" . $row[1] . "')";
if (!mysql_query($query)) {
print $query;
}
}
print "Vocabulary node types set.<br /><br />";
$query = "select * from drupal.term_data";
$queryresult = mysql_query($query);
while ($row = mysql_fetch_row($queryresult)) {
$query = "insert into timesnow.term_data values('" . $row[0] . "','" . $row[1] . "','" . mysql_real_escape_string($row[2]) . "','" . mysql_real_escape_string($row[3]) . "','" . $row[4] . "')";
if (!mysql_query($query)) {
print $query;
}
}
print "Term_data plugged in.<br />";
$query = "select * from drupal.term_hierarchy";
$queryresult = mysql_query($query);
while ($row = mysql_fetch_row($queryresult)) {
$query = "insert into timesnow.term_hierarchy values('" . $row[0] . "','" . $row[1] . "')";
if (!mysql_query($query)) {
print $query;
}
}
print "Term_hierarchy plugged in.<br />";
$query = "select * from drupal.term_node";
$queryresult = mysql_query($query);
while ($row = mysql_fetch_row($queryresult)) {
$nid = $row[0];
$tid = $row[1];
$query = "select vid from drupal.node where nid = " . $nid;
$qr2 = mysql_query($query);
$row2 = mysql_fetch_row($qr2);
$vid = $row2[0];
$query = "insert into timesnow.term_node values('" . $nid . "','" . $vid . "','" . $tid . "')";
if (!mysql_query($query)) {
print $query;
} else {
$tncnt += 1;
}
}
print "Term_node plugged in (" . $tncnt . " records entered).<br />";
?>
You must’ve noticed that I am clearing out all associated tables before each insert block. This is coz’ it is important that the tids, tid-vid pairings, and tid-nid pairings be unique and as they are in the old database. Otherwise it will cause either of the following two problems: (a) terms won’t get attached to your nodes accurately or (b) the insert statements will throw primary key and/or unique key errors.
This script is out-of-the-box too. With just the database name changes (from timesnow. to your database name), it can be run as it is.
And now for the big Kahuna—migrating forum posts.
Migrating forums:
Three parts to this script—forum topics have to be attached to their respective terms, forums posts have to go into the node table, and forum comments have to be migrated. The first part has already been taken care of in the previous script, so we are simply dealing with inserting comments and forum nodes. Again an out-of-box script, this one:
< ?php
$cnt = 0;
$commentcnt = 0;
$query = "select * from drupal.node where type = 'forum'";
$noders = mysql_query($query);
while ($row = mysql_fetch_row($noders)) {
$nid = $row[0];
$vid = $row[1];
$type = $row[2];
$title = mysql_real_escape_string($row[3]);
$uid = $row[4];
$status = $row [5];
$created = $row[6];
$changed = $row[7];
$comment = $row[8];
$promote = $row[9];
$moderate = $row[10];
$sticky = $row[11];
//Insertion into node
$query="insert into timesnow.node values('" . $nid . "','" . $vid . "','" . $type . "','','" . $title . "','" . $uid . "','" . $status . "','" . $created . "','" . $changed . "','" . $comment . "','" . $promote . "','" . $moderate . "','" . $sticky . "','0','0')";
if (!mysql_query($query)) {
print $query;
}
$query = "select * from drupal.node_revisions where nid = " . $nid;
$node_revisionrs = mysql_query($query);
$nrow = mysql_fetch_row($node_revisionrs);
$body = mysql_real_escape_string($nrow[4]);
$teaser = mysql_real_escape_string($nrow[5]);
$log = mysql_real_escape_string($nrow[6]);
$timestamp = $nrow[7];
$format = mysql_real_escape_string($nrow[8]);
//Insertion into node_revision
$query="insert into timesnow.node_revisions values('" . $nid . "','" . $vid . "','" . $uid . "','" . $title . "','" . $body . "','" . $teaser . "','" . $log . "','" . $timestamp . "','1')";
if (!mysql_query($query)) {
print $query;
}
$query = "select * from drupal.node_comment_statistics where nid = " . $nid;
$node_comment_statistics_rs = mysql_query($query);
$ncsrow = mysql_fetch_row($node_comment_statistics_rs);
$last_comment_timestamp = $ncsrow[1];
$last_comment_name = mysql_real_escape_string($ncsrow[2]);
$last_comment_uid = $ncsrow[3];
$comment_count = $ncsrow[4];
//Insertion into node_comment_statisitcs
$query = "insert into timesnow.node_comment_statistics values ('" . $nid . "','" . $last_comment_timestamp . "','" . $last_comment_name. "','" . $last_comment_uid . "','" . $comment_count. "')";
if (!mysql_query($query)) {
print $query;
}
$query = "select * from drupal.comments where nid = " . $nid;
$commentrs = mysql_query($query);
while ($row = mysql_fetch_row($commentrs)) {
$query = "insert into timesnow.comments values ('" . $row[0] . "','" . $row[1] . "','" . $row[2] . "','" . $row[3] . "','" . mysql_real_escape_string($row[4]) . "','" . mysql_real_escape_string($row[5]) . "','" . $row[6] . "','" . $row[7] . "','" . $row[9] . "','" . $row[10] . "','" . $row[11] . "','" . $row[13] . "','" . $row[14] . "','" . $row[15] . "')";
if (!mysql_query($query)) {
print $query;
}
$commentcnt += 1;
}
$cnt += 1;
}
print $cnt . " rows inserted.<br />";
print $commentcnt . " comments inserted.<br />";
//Inserting into forum
$query = "select * from drupal.forum";
$queryresult = mysql_query($query);
while ($row = mysql_fetch_row($queryresult)) {
$nid = $row[0];
$vid = $row[1];
$tid = $row[2];
$query = "insert into timesnow.forum values('" . $nid . "','" . $vid . "','" . $tid . "')";
if (!mysql_query($query)) {
print $query;
} else {
$forumcnt += 1;
}
}
print $forumcnt . " records updated into the forum table.<br />";
?>
Certain table structures have changed in 6.x. But these scripts handle those too.
Now, moving on into content migration. Due to CCK, content migration will have to take into account many different things. I am not going to post a generic content migration script, coz’ I don’t have one, and that is coz’, frankly, I did not need one. I just needed one for a simple content type with just a title and body and terms of all sorts associated with it, with comments.
My content type was called “multi_user_blog.” You may have to change that for your needs. But basically, what the following script does is inserts content title, body, and associates comments. It is like a building block for all your node migrations. A lot of things have changed in Drupal 6.x when it comes to nodes and associated comments and revisions. There have been translation fields added to the node table itself. Also, the vid (version id) in the node_revision table is set to auto increment in 6.x. This vid is also associated with different terms. Thus, each version can now have its own terms in 6.x.
Moving right along to the script, it is pretty straight forward:
< ?php
$query = "truncate timesnow.node";
mysql_query($query);
print "Node table cleared. <br />";
$query = "truncate timesnow.node_revisions";
mysql_query($query);
print "Node_revisions table cleared. <br />";
$query = "truncate timesnow.node_comment_statistics";
mysql_query($query);
print "Node_comment_statistics table cleared. <br />";
$query = "truncate timesnow.comments";
mysql_query($query);
print "Comments table cleared. <br />";
$query = "truncate timesnow.forum";
mysql_query($query);
print "Forum table cleared. <br />";
?>
<hr />
Inserting multi_user_blogs<br />
<?php
$query = "select * from drupal.node where type = 'multi_user_blog'";
$noders = mysql_query($query);
while ($row = mysql_fetch_row($noders)) {
$nid = $row[0];
$vid = $row[1];
$type = $row[2];
$title = mysql_real_escape_string($row[3]);
$uid = $row[4];
$status = $row [5];
$created = $row[6];
$changed = $row[7];
$comment = $row[8];
$promote = $row[9];
$moderate = $row[10];
$sticky = $row[11];
//Insertion into node
$query="insert into timesnow.node values('" . $nid . "','" . $vid . "','" . $type . "','','" . $title . "','" . $uid . "','" . $status . "','" . $created . "','" . $changed . "','" . $comment . "','" . $promote . "','" . $moderate . "','" . $sticky . "','0','0')";
if (!mysql_query($query)) {
print $query;
}
$query = "select * from drupal.node_revisions where nid = " . $nid;
$node_revisionrs = mysql_query($query);
$nrow = mysql_fetch_row($node_revisionrs);
$body = mysql_real_escape_string($nrow[4]);
$teaser = mysql_real_escape_string($nrow[5]);
$log = mysql_real_escape_string($nrow[6]);
$timestamp = $nrow[7];
$format = mysql_real_escape_string($nrow[8]);
//Insertion into node_revision
$query="insert into timesnow.node_revisions values('" . $nid . "','" . $vid . "','" . $uid . "','" . $title . "','" . $body . "','" . $teaser . "','" . $log . "','" . $timestamp . "','" . $format . "')";
if (!mysql_query($query)) {
print $query;
}
$query = "select * from drupal.node_comment_statistics where nid = " . $nid;
$node_comment_statistics_rs = mysql_query($query);
$ncsrow = mysql_fetch_row($node_comment_statistics_rs);
$last_comment_timestamp = $ncsrow[1];
$last_comment_name = mysql_real_escape_string($ncsrow[2]);
$last_comment_uid = $ncsrow[3];
$comment_count = $ncsrow[4];
//Insertion into node_comment_statisitcs
$query = "insert into timesnow.node_comment_statistics values ('" . $nid . "','" . $last_comment_timestamp . "','" . $last_comment_name. "','" . $last_comment_uid . "','" . $comment_count. "')";
if (!mysql_query($query)) {
print $query;
}
$query = "select * from drupal.comments where nid = " . $nid;
$commentrs = mysql_query($query);
while ($row = mysql_fetch_row($commentrs)) {
$query = "insert into timesnow.comments values ('" . $row[0] . "','" . $row[1] . "','" . $row[2] . "','" . $row[3] . "','" . mysql_real_escape_string($row[4]) . "','" . mysql_real_escape_string($row[5]) . "','" . $row[6] . "','" . $row[7] . "','" . $row[9] . "','" . $row[10] . "','" . $row[11] . "','" . $row[13] . "','" . $row[14] . "','" . $row[15] . "')";
if (!mysql_query($query)) {
print $query;
}
$commentcnt += 1;
}
$cnt += 1;
}
print $cnt . " rows inserted.<br />";
print $commentcnt . " comments inserted.<br />";
?>
Studying this script can you give you some clues/insights to migrating content on your own site.
I am working on an auto content migration script that will enable migration of all content types, associated tables, fields, etc.
Also in works is the profile migration script.
In the meanwhile, let me know if I can improve on these OR if you have some script to contribute (I will credit, promise). :-)
Also cross-posted at: http://sentimentalminions.wordpress.com/2008/09/14/php-script-for-the-migration-of-data-from-drupal-5x-to-6x/
MumbaiHi everyone.
I have been exploring Drupal for a month and I have found it impressive, amazing piece of work from the Drupal community. Maybe my questions will sound a bit naifs, I’ve been in project coordination for a while, so my coding skills are rusted.
I’ve been trying to use the “calendar” 6.x module applying a new content created with CCK, but I got stuck in creating its View with the View 2 module.
The test is quite simple.
The table {activity} consists in the following:
.- name (the table nodes name field)
.- description (the table nodes body’s field)
.- date (a date field created and customized with cck)
I tried to use the calendar module to show the dates that are store in the date field, but view 2 doesn’t show the fields from the table “content_type_activity” which contains the date field. I have found the tutorial for the View API, but I still don’t have the experience to follow those instructions.
Could someone give me a example with the hook_views_api(), hook_views_data(), hook_views_handlers(), hook_views_plugins() functions? Please.
I’m also trying to implement the functions hook_load() and hook_view() in a .module so I could create a view for this content type, but, since “activity” content type was created with the cck I’m wondering where to place those functions, in a .module file in the sites/all/modules/activity folder?
And after doing this How could I use the calendar with the fletched data? Any suggestions?
It’s a shame that the events related modules for 5.x aren’t ported for the drupal 6.
Thanks for your help.
Adan
Drupal DojoForleden installerte jeg oppdateringer av noen tilleggsmoduler, og satt plutselig med skjermen full av databasefeilmeldinger. Etter prøving og feiling, bannskap og mer enn en gjenoppretting fra sikkerhetskopiene hadde jeg funnet ut hvordan jeg kunne oppdatere uten at alt gikk til helsikes. Da kom dagens lille dilemma: Skulle jeg gidde å skrive en sak om problemet i saksporingskøen? Jeg hadde jo funnet en løsning som virka for meg, og jeg hadde flere nettsteder å oppdatere og en solfylt høstettermiddag å nyte hvis jeg klarte å kreke meg vekk fra PCen. Min bedre side vant, og jeg sendte avgårde en kort beskrivelse av problemet og løsninga jeg hadde funnet.
Da kom belønningen: Hun som vedlikeholdt modulen var på nett, og kom kjapt med en forklaring, og ikke minst: Et forlsag til løsning som ville være raskere og greiere! Jeg testa den, alt virka, KarenS kunne beskrive løsninga i dokumentasjonen for modulen, og når jeg oppgraderte neste nettsted, som brukte samme modul, gikk alt fort og smertefritt.
...og moralen er: Del løsningene du finner med andre! Ikke bare får du ære, berømmelse og god karma, rett som det er får du nytte av det sjøl også!
NorwayHello Everyone,
I have been working with the new Drupal 6 hook_menu, and have discovered that hook_menu in D6 no longer accepts $may_cache or !$may_cache as arguments. I have a menu which writes out some links information dynamically, and I can't figure out how to stop it from caching the menu.
I have searched for an answer and I found a very vague reference to the use of hook_init and hook_link_save, but there was no example of how to implement this. Does anyone know how to to it properly?
Thanks,
Drupal DojoJeg skriver her en oversikt over ting jeg mener er viktig for oss å diskutere for kontinuerlig utvikling av Drupal i Norge. Jeg skrev forskjellige innlegg om disse emner som jeg skal lenke til. Jeg skrev ikke separate emner her på gdo fordi etterfølgende innlegg ser ut som spam hehe. Jeg tror at det vil være lettere for oss å diskutere hvert emne separat og samtidig starte samlingen av ressurser.
Innleggets innhold:
Nettverksbygging:
En svært viktig faktor i utviklingen av Drupal i Norge er nettverksbygging. For å imøtekomme behovet til Drupal i Norge, ville det være fint hvis vi har to Drupalkataloger. Den første vil være en katalog over norske Drupalnettsteder. Jeg tror vi kan tilpasse det vi har nå for å liste bare norsk-laget nettsteder. Den andre katalogen er for norske Drupalbedrifter og frilansere. En liste (takk til Views) med lenker til en hel infoside av hver bedrift/frilanser er foreslått av Odd-inge. Blir det ikke fint hvis vi har en katalog over de som tilbyr Drupal i Norge med sin egen presentasjon? Det finnes besøkende til vårt nettsted som er på utkikk etter norske Drupalkonsulenter og utviklere. Det vil være enklere for fremtidige kunder å finne oss hvis det er en katalog dedikert til det.
Hvis du er enig, uenig, har noen forslag eller ønsker å være maintainer, kan du gå til: http://drupalnorge.no/innlegg/forum/innlegg-899
Drupalmeetups og DrupalCamp.
Under våre "drikkeøkter" med de danskene og svenskene to uker siden, informerte den danske brukergruppen (Drupal Danmark - http://drupaldenmark.dk) oss om deres plan om DrupalCamp i København. Vi deretter diskuterte muligheten for denne DrupalCampen å tilbys ikke bare for dansker, men for hele Skandinavia. Vårt mål er å holde et skandinavisk DrupalCamp hvert år. Stedet roterer fra en skandinavisk by til en annen.
Slik som de danskene, har vi også registrert et nytt domenenavn og satt opp et nytt Drupalnettsted for bare dette formål. Håper at vi kan få det til at den neste DrupalCamp-en blir i Norge. Jeg vil vente til Danmark for å kunngjøre deres domenenavn før vi kunngjør vårt eget. I mellomtiden, finnes diskusjonen om mulig skandinavisk DrupalCamp i Norge her: http://drupalnorge.no/innlegg/forum/innlegg-900 Hvis du vil være prosjektleder for denne, bare si fra!
Hvis det er DrupalCamp Copenhagen du vi diskutere, da kan du besøke: http://drupaldanmark.dk/artikler/2008/08/31/drupalcamp-i-koebenhavn-15-1...
Drupal 7-dokumentasjon
Vi fikk noen "inside"-oppdateringer fra dokumentasjonsteamet til drupal.org. Dokumentasjonsteamets mål for D7 er å kunne gi ut en brukermanual samtidig som Drupal 7 blir utgitt. Siden dette er et svært ambisiøst mål, bør de som er interessert i å hjelpe med den norske dokumentasjonen stå fram. Dessverre er det ikke aktuelt for tiden å ha flerspråklige håndbøker på drupal.org. Så hvis du ønsker å bidra med norsk dokumentasjon, har vi tre norske håndbøker som finnes på: http://drupalnorge.no/bok
Tidlig i år, oversatte stenjo pressemeldingen for Drupal 6 og zirvap kontrollerte den.
Hvis du vil ha redigeringsprivilegier til de norske håndbøker, bli medlem av norske dokumentasjonsteamet ved å skrive et innlegg på forumet: http://drupalnorge.no/innlegg/forum/innlegg-901
Hvis du vil ha redigeringspriviligier til de engelske håndbøker, bli medlem av de engelske dokumentasjonsteamet: http://drupal.org/node/23367
Maintainer-priviligier
Hvis du ønsker å starte en ny funksjonalitet eller hjelpe til med eksisterende funksjonaliteter på vårt nettsted, bare skriv et innlegg på forumet (http://drupalnorge.no/forum/utvikling/drupal-norge-framover) og spør om maintainer-privilegier.
Nytt design
Vårt community nettsted har fått nytt design. Hvis du ikke liker, liker, du ønsker å endre noe, eller du ønsker å være ansvarlig for det, er det bare å skrive en kommentar, slik at vi kan gjøre noe med det. Skriv din kommentar angående vår ny utseendemal her: http://drupalnorge.no/blogg/johnnoc/2008/09/14/innlegg-902
Takk og happy drupaling!
PS. Vi kan også diskutere disse temaene "realtime" i kveld på IRC, men skriv også på forumet, slik at folk som ikke kan bli med oss på IRC blir fortsatt være en del av utviklingsprosessen.
NorwayHey all!
I submitted a proposal to the Knight Drupal Initiative - http://groups.drupal.org/node/14760.
It's main purpose is to build a new site that is loosely like the dojo, with hopes to re-start the community.
Drupal DojoIt was so nice to meet Drupalistas from other Scandinavian countries at the DrupalCon two weeks ago. To keep the fire burning and continue building bridges, I am listing here the Drupal IRC channels of the Scandinavian countries. This also gives us the opportunity to chat in realtime with other people we have not met before.
I know we cannot order beer from Druplicon (bot), that just have to wait in the next meet-up/camp/con :-)
This list is taken from http://drupal.org/irc
I don't know if Drupal.fi have an irc channel. Do you guys have one?
Relevant links:
http://groups.drupal.org/node/2326 » Internet Relay Chat: an intro to Miranda IM (Windows) and Colloquy (Mac OS X)
http://drupal.org/irc » How to use IRC effectively
https://addons.mozilla.org/en-US/firefox/addon/16 » Chatzilla (firefox addon)
This is a very introductory look at Forms API in Drupal 6.
The focus is on basic and practical application, and should allow the newest Drupal programmer to be able to go create his or her own form, in Drupal 6.
Attached is the code for your perusal--It's the same as what's demonstrated in the video, with a bunch of comments. (I would have attached a tarball, but it was not an acceptable file format)
The 30-minute screencast is hosted at blip.tv.
NOTE: In the video, I fail to use check_plain() when outputting some user-generated content...For the sake of you and your web site, don't forget this step. The attached code example is i believe doing it right
Corrections, Questions, Comments, and Smart Remarks are always welcome. :-)
Drupal DojoAfter a week of delay due to DrupalCON related travel, it is time for our monthly open review meeting. We will meet for the next round of proposal reviews on Thursday, September 11th at 14:00 Eastern (US) (18:00 UTC).
The meeting will be held in IRC #drupal-dojo on irc.freenode.net. (See http://drupal.org/irc for information about using IRC.) We will meet for 1:30 with the following agenda:
1) Review current proposals that need decisions:
-- NewsCloud newsroom module is being reviewed for the second time and should be accepted or rejected at this meeting.
Participants are asked to review this proposal before the meeting.
The project sponsors are welcome to answer questions during this review. The possible outcomes of these reviews are:
* Submit the proposal to Knight for possible funding. * Reject the proposal, with reasons why. * Ask the proposal to be revised for the next round of review.2) Introduce the new proposals for review:
-- Expanding Context_UI, Spaces, Messaging and Notifications, FeedAPI and Maps and Open Sourcing 8trees and Managing News is a new application that needs review and consensus on how to move forward. The application has met the acceptance criteria, but there are outstanding issues regarding the format and scope of the application. See the discussion of the proposal for details.
-- drupaleo - talent growing and hiring for drupal is a new proposal for review.
-- Grant-Making System is a new proposal for review.
-- Documentation sprints for better docs and to grow the team is a new proposal for review.
The purpose here is to get eyes on the new proposal, and let the submitter answer questions.
3) Time permitting, work on publicizing the efforts of the KDI.
Marketing of DrupalHello Fellow Drupal Users....
My name is Dale and I'm very new (white belt) to Drupal, Over the last three years or so I converted to Dreamweaver using pure HTML and am now moving to Drupal because it is so powerful and flexible. I'm very new to the process and am reading everything I can get my hands on and watching allot of tutorials.
I own my own (very little) web development company and work primarily for small non-profit or small business owners and plan on expanding that a little as I learn more about this great program. This is not my day job :( but it soon may be as I've spent the last 25 years of my life serving and protecting the public as a Firefighter/Paramedic/Fire Inspector/Fire Investigator/ and currently serve as Fire Marshal in a medium sized Township Government in Ohio U.S.A.
So hello to all and I look forward to learning a lot of each other....
Dale
Drupal DojoBarCamp Nashville is an open-source gathering of technology enthusiasts who come together for one weekend to share what they know and learn what they don’t. It is an intense event with discussions, demos and interaction from attendees.
We are expecting this to be one of the largest BarCamp gatherings in the Nation! Don't Miss out!
Anyone with something to contribute or with the desire to learn is welcome and invited to join.
(Drupal will be well represented by many developers/designers/admins)
Virginia TechHello everyone, I have only been working with drupal for about 3 month now. As you all know the learning curve for drupal can be like a roller coaster ride! I am wondering if there are any of you that live in the Asheville, NC area that would love to get together and talk, play and eat drupal? I would love to make friends with people that know what the heck I'm talking about!
North CarolinaSå er det annonsert, DrupalCamp i København, og det under 1 år etter at jeg postet denne kommentaren, den 7 November 2007, med påfølgende diskusjon samme dag. Da var jeg ikke så "langt ute på jordet" allikevel. Flere mente at 2009 var det mest realistiske, men danskene ville det annerledes. Kjempeflott.
Så nå får vi håpe at det blir et kjempefint arrangement med mange deltagere. Det er mye som skal ordnes på forholdsvis kort tid. Tvi tvi Danmark. Heldigvis er det ikke så dyrt å reise. Tur retur med DFDS koster Kr.1.680, med avreise den 14 og retur den 16 kl. 17 fra køben. i 1-manslugar. Slår man seg sammen og deler en større lugar blir det rimeligere og kan man bruke bil (6 -8 timer) og da blir det enda rimeligere pr. stk. Overnatting og mat kommer i tillegg. Men her kan sikkert danskene finne rimelige overnattingsteder.
Av innhold så leser jeg at det er både for nybegynnere, og de som er kommet et steg lengre. Så for de som er interessert bør de følge med på den danske hjemmesiden.
Ole Martin
Drupal i Norge