Closed (won't fix)
Project:
Privatemsg
Version:
5.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
27 Dec 2007 at 09:32 UTC
Updated:
5 May 2010 at 07:39 UTC
I have the Update status 5.x-2.0 and Privatemsg 5.x-2.x-dev (2007-Dec-21) modules installed, and update status is contiously informing me that I am out of date.
When I had the Privatemsg 5.x-2.x-dev (2007-Oct-30) module installed it all worked fine.
Thanks for your time
Stephen
Comments
Comment #1
mrgoltra commentedThis is what I am getting. I have updated several times and would work for a day then I get the update status message, thinking that there could be another update but nothing. Any ideas guys?
Update Status Message I get.
Privatemsg 5.x-2.x-dev (2007-Oct-29)
Recommended version: 5.x-2.x-dev (2008-Jan-22) Download · Release notes
Includes: Mail Editor, Privatemsg, Private message subscriptions
I
Comment #2
spjsche commentedI thought I was the only one having this problem, and so I gave up.
I have uninstalled and reinstalled to no avail, so now I switch updates off until I need to check.
Still do not know what is causing it, whether it is the update status module or the timestamp on the privatemsg module, which I have also changed with no success.
Perhaps someone could steer us in the right direction.
Thanks
Stephen
Comment #3
mrgoltra commentedI was going nuts with this. It probably something minor.
Comment #4
spjsche commentedWell, I switched on the update status and low and behold there is a new version for both update status and privatemsg, and I thought hey this has been fixed, so I duly updated them both, and guess what, it is still the same.
Oh well, I'll switch it off again, to avoid the red banner.
Thanks
Stephen
Comment #5
mrgoltra commentedyep its still there.
Comment #6
Street-1 commentedI am getting this too.
I have 5.x-2.x-dev (2008-Jan-22) installed and am being told to update to 5.x-2.x-dev (2008-Jan-22).
Comment #7
mrgoltra commentedDoes anyone know how to fix this or maybe point me to the right direction where to start. This is really getting annoying.
thanks
Comment #8
mrgoltra commentedI am surprised that its only us getting this error message?
Comment #9
Flu commentedSame issue here. My first thought was that it might have something to do with Daylight Savings.
Comment #10
berdirSorry for pinging the participants, I am closing old issues.
This version of Privatemsg is not supported anymore, maybe it is already implemented in Privatemsg for Drupal 6 and if not, you are welcome to open a new issue for it.