Roadmap for official 1.0 release
litwol - February 10, 2009 - 16:22
| Project: | Privatemsg |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
We're experiencing an influx of feature requests and before we get lost in all of it we need to come up with a roadmap that will prevent us from going insane.
First of all let me say that it is a great sign that there's big spike in feature requests, that means this module works and works well for many :-D. good job everyone involved!
#1
Preventing us from going insane is a good idea :)
I don't have any personal preferences except that the API should be working and documented before going stable. And that is more or less my task. We can still add features and fix bugs when 1.0 is released, but changing the API when other modules (for example, friendlist) are using it, should be, if possible, avoided.
Well i'd *love* to have a roadmap feature on d.o, similiar to PEAR: http://pear.php.net/bugs/roadmap.php?package=PEAR, as managing such a list manually is... suboptimal :).
#2
From a quick gander, the stuff that is being worked on/ready:
#288183: Provide api function for other modules to send messages.
#367745: permissions for privatemsg_filter need to be improved.
#288960: Search private messages function requested
#370937: Block cache should be BLOCK_NO_CACHE
#371861: Flush deleted messages
#348907: Per thread/Multiple thread actions
#366170: Errors with PostgreSQL
#350344: Remove privatemsgapi.inc from module
#342733: Attachments for privatemsg
#357093: Email Notification for Drupal 6.x
EDIT - I had missed some out out, added now (fourth to eighth).
#3
I consider the following being major functionality and would like it to be pushed to 2.0 release cycle. This doesn't mean it will be neglected for long, it actually means the opposite... We will be able to focus on what is more important right now and finish with it sooner so we will be able to bring our attention to 2.0 release cycle faster:
#342733: Attachments for privatemsg
#357093: Email Notification for Drupal 6.x
#4
My main concern is about the handling of such a roadmap, I think it is very hard to maintain a list of issues by hand, every time a new one gets added or moved, we would need to update that list. nbz already tried to maintain such a list in #324380: Privatemsg: The road to Damascus once.
What if we use issue tags to create some kind of an roadmap, for example, adding "1.0" to all issues we'd like to get in until the release of 1.0. Then, the only thing we need to post somewhere (in a issue, on the project page, in the -dev release node.. ) is a link to a taxonomy page listing all issues with a specific tag.
About the naming of the release.. 1.0, 1.1, 2.0 and so on.. I personally would say that we shouldn't move to 2.x unless we need to break something, adding new features to a 1.x release sounds perfectly fine for me. But I don't know if there are any Rules/Guidelines for Modules around..
#5
rule of thumb is:
new features get point release
bug fixes get decimal point release
as for #324380: Privatemsg: The road to Damascus, i found it to be highly useful to help prioritizing which issues get reviewed and commited first. in fact /this/ issue is a request to make another roadmap to ... well u know ;)
#6
I am willing to try and keep a list updated, as even using issue tags (privatemsg-1.0 or somehting) would still require manual sifting when an issue needs to be dropped/added/moved etc.
I have added two more to the above list - first three are IMO ready to go in.
#7
Using tags wont work because some one can just tag a new issue and it would show up in the list.
The point of this list is that we cant add more issues to it than originally assigned. that will ensure that we can create the upcoming 1.0 release in a timely manner.
#8
Email notifications are working very well using the code here: http://drupal.org/node/357093
Is there presently, or are there plans for, a way to limit the mailbox size for users or automatically purge messages older than X?
#9
@RachelNY: #371861: Flush deleted messages flushes /deleted/ messages, but there's no working feature yet to purge non-deleted messages order than X.
#10
After having nbz's list a day, I take everything back... that list is definitly *very* helpful... (And if it is only for looking up the issue #, when referencing them elsewhere :). The only one I can remember is my api patch, as I've written that ~100 times...)
- You may want to include the following to your short term list
#367743: Read tab should not show on messages/new/% - bug
#298502: Better access to another user's messages - broken feature
- Maybe splitting the list up, adding litwol's statement, something like:
1.x
#
#
#
2.x
#
#
- Then you could also reference some long-term things like thresholding (messages/time, total messages, ...), integration (rules, ...) and so on.
- This would make the list not only useful for us developers, it would help users to see what the plan is for feature X and lower the amount of feature request duplicates.
- nbz's comment could then be linked from the project page, so that it doesn't get lost (that's happened with the old roadmap issue)
#11
ok, attempting a different layout.
Major feature work that will enable other stuff - ready for testing/commit:
#288183: Provide api function for other modules to send messages.
Major work not yet ready:
#348907: Per thread/Multiple thread actions
#298502: Better access to another user's messages
Minor feature work/bug fixes:
#288960: Search private messages function requested
#373092: privatemsg_title_callback should use format_plural
#367743: Read tab should not show on messages/new/%
#367745: permissions for privatemsg_filter need to be improved.
#371861: Flush deleted messages
#366170: Errors with PostgreSQL
#370937: Block cache should be BLOCK_NO_CACHE
#350344: Remove privatemsgapi.inc from module
Additional longer term features/additional modules that may be worked on after the 1.0 release:
#342733: Attachments for privatemsg
#327938: Rules Integration
#357093: Email Notification for Drupal 6.x
#12
This one required too
#370960: Remove t() from all schema descriptions
#13
I'll try to create a updated list. You might want to priorize #11 for RC3, but there are some missing things that should go in before 1.0 (imho). When I have one, I'll add a personal comment of the status of the issue
Bug fixes:
- #393858: Validate $recipients (only user objects are allowed, not uid's) - Small bugfix
- #430948: privatemsg does not work with non phptemplate based themes (Marvin/Chameleon) - Workaround proposed...
Filter refactoring/User tags:
- #442102: Replace tag checkboxes with autocomplete textfield - Step 1
- #442108: Add alternative Folder-like system - Step 2
- #442130: Move tags page to /admin and add public flag - Step 3
- #442172: Display used/public tags somewhere - Step 4
- #441042: Replace participant select - Replace the resource-intensive participant select widget with an autocomplete field.
Performance:
- #444440: privatemsg_message_load_multiple()
- #444672: static cache for thread_load
- #444682: Remove user_load() from thread_load()
Minor features, work in progress or ready:
- #371861: Flush deleted messages - is ready, contains tests
- #267814: Setting to define certain roles (e.g. staff) which a user cannot block PMs from - unblockable roles for pm_block_user, needs review
- #341370: Add "Send msg to author" link to selected node types - First version of patch, awaiting feedback. Most probably post 1.0
- #405240: Use SUM instead of COUNT for is_new in the list messages query - Display number of new messages
- #406584: Integration with Popups API - Popups integration
- #404044: Disable private message receipts - Allow user to disable the recieving of private messages
- #376005: #288183 followup: _privatemsg_send always returns TRUE. change that to return more relevant information. - fixes a bug and adds a minor feature to the api
Major features, work in progress or ready, part of privatemsg.module:
- #298502: Better access to another user's messages - could probably be delayed to a later version if we remove the permision. Not easy to implement in a good way, would like to get some feedback on my ideas
Major features, part of sub-modules:
- #342733: Attachments for privatemsg - freshly re-rolled, needs to be tested
- #327938: Rules Integration - works, but may need more events and actions..
- #69856: Message quota - works, tests should be easy to write
Other:
- #377248: Theme privatemsg a la Gmail, add classes, etc - Gmail like theme, looks great but a generic way to handle "themes/layout" needs to be found. The current solution is only implemented for the view template
Please add a comment if something important is missing. Also, this list is more or less a grouped view of the search I'm using:
http://drupal.org/project/issues/search/privatemsg?text=&assigned=&submitted=&participant=&status[]=1&status[]=13&status[]=8&status[]=14&version[]=6.x&issue_tags=
#14
#15
I hope you add a
"report this message to admin" feature.
#16
Please don't use this issue to report or comment on issues. Use either the linked, existing issues or create a new one.
#17
[deleted] - I am just confusing the issue by having an alternative listing. Comment 13 is easy enough to follow and lists more stuff.
#18
Hi Berdir, I am not sure but I can't see in your road map one important issue (I'll try to find #) about notification flag for my sent messages - which messages of them were already read. Is it done already or I missed something?
Thanks for your work on this module
Igor
http://www.somvprahe.sk
#19
mistake sql request:
file: privatemsg.module
line: 670 and 671
670: $fragments['where'][] = 'pmi.uid = %d';671: $fragments['query_args'][] = $account->uid;
change on
670: $fragments['where'][] = 'pmi.uid != pm.author';671: /* $fragments['query_args'][] = $account->uid; */
apologize, for my very bad english.
#20
Hi Guys, I guess, I need some help from you :-S
I'm totally newbee on drupal, and already addicted to it :-)! Even there are some issues, I can't handle with, because my code writing skills are not that improved at all. However, after installing the module: "privatemsg", I can't even open anymore my website. It always displays that error message:
"Fatal error: require_once() [function.require]: Failed opening required 'modules/privatemsg-6.x/styles/privatemsgapi/privatemsgapi.inc' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home/latincof/public_html/modules/activitystream-6.x/PEAR') in /home/latincof/public_html/modules/privatemsg-6.x/styles/privatemsg.module on line 15"
Yep, I checked that folder; and the file privatemsgapi.inc seems (well @ least for me) ok :-S!
Hmmm, "line 15" I have no idea,how to fix that! After uninstalling that module, the site does open again, but with a huge list of error messages :-(!
Please could someone tell me, how to fix this? That would be great :-p!
Thank you anyway, for your great efforts :-S !
#21
Hi Guys, I guess, I need some help from you :-S
I'm totally newbee on drupal, and already addicted to it :-)! Even there are some issues, I can't handle with, because my code writing skills are not that improved at all. However, after installing the module: "privatemsg", I can't even open anymore my website. It always displays that error message:
"Fatal error: require_once() [function.require]: Failed opening required 'modules/privatemsg-6.x/styles/privatemsgapi/privatemsgapi.inc' (include_path='.:/usr/lib/php:/usr/local/lib/php:/home/latincof/public_html/modules/activitystream-6.x/PEAR') in /home/latincof/public_html/modules/privatemsg-6.x/styles/privatemsg.module on line 15"
Yep, I checked that folder; and the file privatemsgapi.inc seems (well @ least for me) ok :-S(I just attached that file, so you could take a look)!
Hmmm, "line 15" I have no idea,how to fix that! After uninstalling that module, the site does open again, but with a huge list of error messages :-(!
Please could someone tell me, how to fix this? That would be great :-p!
Thank you anyway, for your great efforts :-S !
#22
Example correct SQL request for function privatemsg_privatemsg_list_sent_alter:
function privatemsg_privatemsg_list_sent_alter(&$fragments, $account) {
$fragments['primary_table'] = '{pm_index} i';
$fragments['select'][] = 'i.uid AS author';
$fragments['select'][] = 'm.subject AS subject';
$fragments['select'][] = 'm.body AS body';
$fragments['select'][] = 'm.timestamp AS timestamp';
$fragments['select'][] = 'i.thread_id AS thread_id';
$fragments['inner_join'][] = 'LEFT JOIN {pm_message} m ON i.thread_id = m.mid';
$fragments['where'][] = 'author = %d';
$fragments['query_args'][] = $account->uid;
$fragments['where'][] = 'i.uid != m.author';
$order = 'timestamp';
$sort = 'desc';
if ( isset( $_GET['order'] ) ) {
switch ( $_GET['order'] ) {
case ('subject'):
$order = 'subject';
break;
default:
$order = 'timestamp';
}
$sort = isset($_GET['sort']) && ($_GET['sort'] == 'asc' || $_GET['sort'] == 'desc') ? $_GET['sort'] : 'desc';
}
$fragments['order_by'][] = $order . ' ' . $sort;
}
#23
Can you please create new issues for bugs/problems/support requests/anything-that-is-not-discussing a roadmap?
@xlogic - the latest nightly no longer has such a function, and even if any of the query definitions have an error, please create a new issue also highlighting the problem that the code change fixes - I have no idea from looking at that code what you changed or why.
#24
xlogic, thank you very much, for your response, that kind of helped! privatemsgapi.inc is up and running :-D!
nbz , no need anymore to create an issue for it! This one is fine now, but therefore much more others appeared :-S!
Thank you guys, for taking care of them!!!
#25
Hi guys;
It's been 6 months since rc2 was released; is there any way we can roll up all the bugfixes from CVS into rc2.1 to get something clean out whilst work continues on rc3? Surely once the module has reached RC status, new feature requests should be deferred to the next cycle?
I'm having to run the current dev version on a live production site to avoid the un-prefixed pm_index table error which was fixed months ago.
Thanks for all the work,
Emyr
#26
Numbering schemes are just that - numbering schemes. Different numbers mean different things to different people.
Saying that, we do try to keep the dev nightly stable and usable (saying that, it does contain a very annoying bug at the moment where the title on messages pages are incorrectly shown as "write new message" instead of the actual message/thread subject.)
#27
I think what Emyr42 is asking for is a release that has all the latest fixes in it... and maybe lists them in the release notes? Speaking for myself, I've gotten thoroughly lost trying to keep track of what ver. I want to be using... with all the patches and everything. And usually the release notes on the dev don't say anything about what fixes and patches have been included.
So maybe this is really a minor documentation request?
#28
@nbz: Which would you recommend for a site that wants to upgrade from the Drupal 5 version, rc2 or dev? I get the impression that dev is a better choice with all of the work that has gone into it, but I'm not sure what the policy is as far as updates go -- i.e., will the .install file contain updates only for going from rc2 directly to rc3, or will there be an upgrade path for the current dev version to rc3 (or to a future dev version)?
Any advice you can give will be greatly appreciated. Thanks!
#29
@strangeways - there will be an upgrade patch (and currently rc2 and 1.x-dev both share the same database schema, so there are no differences yet).
I am using a patched 1.x-dev on a live site (there is a title on messages page bug currently in the dev nightly which is annoying).
#30
@nbz: Thank you for the info. I'll give 1.x-dev a try!
#31
Good work so far.
I've written a little supplementary module (or at least, nearly finished) that exposes a block which has an unread message count, that gets updated at a specified interval using AJAX. I'm also planning to add an unobtrusive JQuery-based notification when a new message is received (something like JGrowl - http://www.stanlemon.net/projects/jgrowl.html).
I don't know if you are planning to implement such a thing - I didn't notice anything in the roadmap above - but you're welcome to my code, if it seems appropriate?
#32
There is already such a module that has been recently implemented and works pretty well: http://drupal.org/project/pmgrowl
It may be a good idea for you to combine resources and work on that module.
(PS for others, lets leave this issue for tracking purposes and open new issues for bugfixes, features/enhancements and ideas please?)
#33
I don't see flag for read/unread messages, block with the users I ban for sending me privatemsg with link to unban.
However, it is really huge progress I found in privatemsg developing
#34
Subscribing... interesting module :)
#35
Can't quite tell from the roadmap where exactly tags become per-user. Is that in "4420102 replace tag checkboxes..." or somewhere downstream?
#36
THey do not become per user, but from #442102: Replace tag checkboxes with autocomplete textfield they start *acting* per user.
#37
OK... well, as long as users only see their own tags, that works for me... is that what you mean by "acting per user"?
#38
yes.
#39
I would add notifications feature, and tab "PM Message" which would lead to form messages/new/uid on user page, like is with "Contact"
#40
Both of those exist I think.
- There is a link on the user page to send that user a pm.
- In the 1.x-dev nightly releases there is an email notify module that allows the users to be notified.
- If you meant on screen notifications, there is the pmgrowl module does that.
Also, for feature requests, please start new issues - leave this one to track the relevant issues.
#41
There's a link, but I'm talking about tab, to unify the look with the contact module (when both are enabled this will look confusing).
One more thing - mass privatemsg sender, as there's no such functionality at the moment.
#42
ok, How I see things - A mini roadmap:
Two bugs that need to be fixed ASAP that will allow for RC3:
#430948: privatemsg does not work with non phptemplate based themes (Marvin/Chameleon)
#490650: Message sent to oneself breaks new/#replies data loading
#442102: Replace tag checkboxes with autocomplete textfield
#43
Why did *tagging* become an essential feature, and why are *folders* no longer a viable option?
PS: Everyone seems to be all over Gmail's labels, but they actually are going out of their ways to make them work more and more like old-school folders. Labels are displayed as folders via IMAP, now you can drag-and-drop messages to labels, etc.
PPS: I would personally only need an Archive folder and action, just like LinkedIn.
#44
Gabriel Radic, technical and user experience aspects of this question have already been answered multiple times. Please use the issue queue search to find it.
#45
rc3 is out, what about the following for rc4?
We define a static, rather short list of *features* (and tasks) that we want to get commited for rc4. Additionaly, we fix all normal/critical bugs that are open or will be reported while we are working on the features. This is a dynamic list aka a specific sort of the issue queue.
The bug list could be this:
http://drupal.org/project/issues/search/privatemsg?text=&assigned=&submitted=&participant=&status[]=1&status[]=13&status[]=8&status[]=14&status[]=15&priorities[]=1&priorities[]=2&categories[]=bug&version[]=6.x&issue_tags=
I am pretty open what features are added to the list, Things I'd like to see:
- Further improve tagging (folder, admin page, thread actions...)
- UX (like the tabs stuff) and DX improvements (better docs, a few fixes/improvements for our api functions.. )
- Some other things like SUM(), view other messages, the blocking patch..
Once all features are in and all bugs of that list are fixed (or set to minor, postponed for a reason, ...) we release rc4.
#46
Is there (In newest release) option "block receiving any pms?"
#47
No, but you can try to review and comment on #267814: Setting to define certain roles (e.g. staff) which a user cannot block PMs from so that it can be added.
#48
For RC4 - this is what I would like to see addressed:
Ofcourse if other ready patches can get in too, then good stuff.
#49
Lets give everyone a fair change to cast their votes. Several days from now we should lock the list for rc4 and be strict about not adding anything else to the list.
nbz do you want to own this task? say on wedneday you can lock it down and start a new issue for rc4 only.
#50
Sure, I don't mind. I do think though that some of it will be whatever patches arrive/are ready/are deemed necessary.
#51
It would be great to add this into private message roadmap - mass sending privatemessage to all users with some role
http://drupal.org/node/86670
thanks
Igor
#52
So all of this is more or less finished, excluding the folder design... It's just idling instead of being commited?
#53
The people working on privatemsg are not full time employess of privatemsg. I do think we have got quite far though - not a single bug filed since rc3.
Things will get moving - hopefully soon as I want the final (1.0) to be out ASAP, but I nor anyone else can tell or expect the other people working on the module to work on it instead of paid for contracts/employment.
#54
I realize that it's free, and that people have other obligations... and I respect the quality of work so far. It just seems that some of the above issues had been finished and ready to go for some time, but nevertheless had not been committed. Just checking in is all really...
#55
I personally find it very misleading and rude that you are encouraging users to migrate to the 6.x version. *No one should upgrade*. This module looks and behaves very differently than the 5.x version. Instead, people should be encouraged to test first and make sure they are cool with the new design. Also, they should be advised to make backups and prepare to roll back the changes the hard way, cause there is no way back once you release the upgrade.
#56
Most people will be happy.
I find misleading *and insulting* the sentiment that no one should upgrade.
Another point in favour of upgrading is that the 5.x module is more or less abandoned and none of the current developers have any experience with it, so there are bugs and who knows what else.
The listing of messages is also badly broken in 5.x when threading is enabled.
A further measure of the quality of the 6.x privatemsg is that AFAIK not a single bug has been filed since the release of rc3.
Ofcourse it will not be suitable for everyone, but telling people not to upgrade is wrong - especially when within a few months drupal core 5.x will become unsupported.
#57
It was not my intention to insult anyone. I am not addressing the quality of the code, your dedication or the satisfaction of the new adopters. All those may be just fine, I am sure. I am specifically talking about those who, like me, were happy to go on with the migration only to be disappointed by the direction this module took. Again, I am not disputing the module's quality, just the message you are promoting.
#58
I appreciate everyone feeling so strongly about this module. Confirms people involved in the development did something right if users feel so passionate about it.
Everyone is welcome to participate. No, i urge you to participate to shape the direction in which this module is moving.
I do not consider "complaints" or "criticism" as anything but valuable feedback for this module's improvement. So please do not stop being involved in it. Create tasks, contribute ideas, test patches, participate in usability feature discussions, etc...
Lets work together.
#59
@Gabriel
The suggestion is simply based on the fact that there are a few developers that work on the D6 version of privatemsg while _nobody_ is working on D5. So, if you have a problem with that version, you are pretty much on your own. This is why we recommend to use the D6 version, not because it's better.
#60
subscribe
#61
2 desires
1. could "Messages" appear as a tab when a user clicks on "My Account" (similar the way Notifications appears)?
2. tokens for the realname module and/or cck (i have a "first_name" field with content profile) for a more personalized correspondence
thanks - great module!
#62
When you make mass pm mailer by role, I wonder?
#63
Not anytime soon. Post questions like that in issue dedicated to the speciffic feature.
#64
What's involved in putting the main message page into a block that can be place into a sliding area in a theme for example?
#65
Would be very cool to have it integrated with Views, as I'm having to build what looks like a mail application though uses private messages so have to re-build pages and use organic group context etc.
#66
As some might have already seen it, I am now co-maintainer of privatemsg. That means that I can now commit patches.
We are now very close to a RC4 release. As I have commited quite a few new things, I will wait a few days before releasing it, but the -dev release should quite stable now (except #600812: inbox could be list with received messages only so you might want to wait until that is fixed.), so everyone is invited to help by testing the -dev release as soon as possible. If you encounter bugs or something that seems wrong, please open bug reports. Do *not* comment in this issue.
The (my) current plan is to add/fix a few more things after RC4 and then hopefully release a stable 1.0 after that. After that, development will start on the new 6.x-2.x-dev branch, new features will only be added to that one (and 7.x-1.x-dev of course).
You can help by testing the patches/issues that are currently available in the issue queue. Note that not all of them will be added to 1.0.
Some hints about what I'd like to do before 1.0 (NOT RC4):
- Some Data/API/UI cleanups/improvements like #502664: remove author uid from pm_index (if possible), #577448: Remove tab on user profile?, #564144: paging long threads, #559180: Delete messages and settings when a user is deleted.
- Of course all bugs we can find.
- Some Tags improvements (#442130: Move tags page to /admin and add public flag, #523064: Display tags in thread list, #444264: Add tagging actions to message listing)
Note that sub-modules will most probably not be added to the 1.x branch. (Testing is welcome anyway!) This includes:
-#327938: Rules Integration
-#342733: Attachments for privatemsg
-#563424: To: dropdown
-#69856: Message quota
-#548188: add/remove somebody to/from some discussion
#67
Hi Berdir, thanks for update.
Can you please share some info about feature - sending private message to all users of some role?
http://drupal.org/node/372201#comment-1908194
will be it added into roadmap? could be it done it till stable 1.0. or not, or this feature will be not implemented at all and wil be not added into roadmap...
I am really curious about it, because I think that it is really welcome and good feature, so I really appreciate some update about it.
thank you
Igor
#68
your best bet is to ask that question in the right place - that thread.
A problem with that issue currently is that there has been no plan of attack that workd well both for small sites and big sites - you could easily add a few million rows into the index for each message.
It would be best ot discuss the implementation details in that topic and I am sure if a working patch is produced, it will go in. The question is just how to do such a thing well.
#69
I just tagged the latest code in -dev, this means that, unless there are bugs reported until then, the current code will become the 1.0rc4 release by the end of this week.
So, again, everyone is invited to test the current -dev release and to report bugs. Note that the current -dev release might not contain the patches from today yet.
These are the current release notes, taken from CVS:
Changes since DRUPAL-6--1-0-RC3:
#70
Subs
#71
A short update about the things that need to be done before the 1.0 release can finally be published:
1. Fix all remaining bugs, see http://drupal.org/project/issues/privatemsg?text=&status=Open&priorities...
2. Add a few remaining features, these include (probably):
- #547106: Link: write to this user in views (Done)
- #559180: Delete messages and settings when a user is deleted. (Done)
- #564144: paging long threads
- #523064: Display tags in thread list (Done)
Again, I'm asking every user of privatemsg to test the latest -dev release and the mentioned issues/patches and report any bugs you can find!
#72
Thank you for the status update - looking forward to the 1.0 release!
Would like to help with testing to see privatemsg module continue to develop.
#73
Are editors now works with pm? I have installed BUEditor and with my version it's not working, also mass messages mailer by role would be great.
#74
BUEditor should work with http://drupal.org/project/wysiwyg
#75
I hope this isn't considered a cross-post as I posted this in the forum earlier.
What is the process to upgrade to this module from RC3 to RC4. I want to make sure I don't remove the tables associated with existing privatemsgs.
I've discovered I cannot perform and UNINSTALL on this module as it will remove the db tables and thus lose the exiting PMs
If I simply disable the module, move the old RC3 directory out, and move the new RC4 directory into place I get a mysql cough that says
"user warning: Unknown column 'format' in 'field list' query: INSERT INTO pm_message (subject, author, body, format, timestamp) VALUES ('Test', 1, 'test', 2, 1257975953) in /var/www/html/lonestarfishing/modules/privatemsg/privatemsg.module on line 1619."
I would like to continue testing his for you.
#76
you need to run update.php and after that the error message should go away - you should run this when updating any module as there may be database schema changes and other updates that need to be run.
@Berdir - can the rc4 release page be altered to mention this somewhere up top?
#77
Your are absolutely correct. I just ran update.php and it did not resolve the error.
Thanks much for the push forward.
#78
***FIXED****
I noticed that the default themes pushbutton and garland were missing from the themes directory. THis was preventing the update.php from properly executing.