Alternative zu Privatemsg ?

Gute Frage, kenn auch keine Alternative - hab aber dasselbe Problem.
Bin gerade auch dabei ein Projekt auf D6 zu entwickeln, das aber nicht oberzeitkritisch ist, insofern werd ich PNs wohl erstmal weglassen und dann integrieren, sobald eine alpha oder beta von privatemsg.module draussen ist.
HEAD sollte man nicht einsetzen, da es hier noch zu erheblichen (auch DB-seitigen!) Änderungen ohne upgrad-pfad kommen kann (s. drupal.org-issue-auszüge unten).

Hoffen wir mal, dass die maintainer zügig eine Alpha rausbringen.

gruß,

daniel

_____________________________________________

http://drupal.org/node/303485

#1
litwol - September 3, 2008 - 17:34
new
Status: active » fixed

HEAD is where the most current code lives. All new development is done in HEAD. Once code is considered stable it will be split into a special release so you will get something like '6.0-1.0' as a release.

Rule of thumb is that it is NOT safe to use HEAD on your site. because new code will be added to it and it can break your site. If you are in a hurry then you dont have choice, but be careful. if you are not in a hurry then wait a few weeks until the module had it's official release. there are people working on it so it will be here soon.

_____________________________________________

http://drupal.org/node/312210

#2
mrtoner - September 24, 2008 - 07:16
new

@briggsl: Uninstall and reinstall. I'm not seeing this error with HEAD, but if you installed it over an existing version you could see this. Remember, HEAD is not even close to ready for prime time, so the db schema is likely to change -- with no upgrade path.

See http://drupal.org/node/303485

@VaZso: We broke the notification on login a few weeks ago. Look for that to be fixed shortly. BTW, HEAD is not even close... :-)

_____________________________________________