Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
beta2 in my modules list, but keep having messages that I have to upload to beta1...
Then I see that beta1 and beta2 were updated practically at the same time in the projects pages.
Before copying the datestamp from beta 1 and putting that over beta 2 in the .info file as that maybe resolves this minor issue?, I like to know:
Is beta3 indeed the latest release, or was there another error with mixing beta 2 and 3 up?
Then what time is projected on the Drupal pages for the releases; UTC, or my local time? Without knowing that I can't use datastamp calculators with the date given by Drupal.
Comment | File | Size | Author |
---|---|---|---|
#8 | rubik-b1b2.patch.txt | 1.06 KB | achton |
Comments
Comment #1
ClearXS CreditAttribution: ClearXS commentedcorrection: "... mixing beta 2 and 3 up?" has to be: ... mixing beta1 and 2 up?
Comment #2
bomarmonk CreditAttribution: bomarmonk commentedUsing Rubik 6.x-3.0-beta2, but the status report tells me that I need to update to beta-1 (same error). This is probably an easy fix to the info file, but it should be made to the official release.
Comment #3
jstollerI'm having this same problem, both with the Update module and Drush. Any chance you could release a Beta3 to clear this up?
Comment #4
jstollerI tried changing the timestamp in the beta2 .info file on my server, but that doesn't seem to have worked.
Comment #5
Dave ReidAccording to the XML feed, the beta1 release was created on Drupal.org 1 second after the beta2 release node. So update.module thinks beta1 is newer. So the bigger question is wtf happened when the releases were created? There's also a bunch of Rubik D7 releases that have their dates messed up.
Comment #6
sgabe CreditAttribution: sgabe commentedSubscribing. It's really annoying.
Comment #7
jstollerI'll renew my request for a new release to correct the timestamp, but until that happens, is there any thing I can edit in my copy of the theme, or in my database, which will fix this temporarily.
Comment #8
achtonThis should get cleared up, since the update manager bugs you about this until you downgrade.
I have downgraded to B1 and applied the attached patch which contains the code differences between B1->B2, which are very minor. This clears up the problem for me, but also means that you are using a "tainted" version of Rubik (unofficial).
Comment #9
aramboyajyan CreditAttribution: aramboyajyan commentedAll old and outdated
6.x
issues are being closed.Maintainer support will be provided only for major / blocking issues.
If you feel like this issue should be re-opened, feel free to do so.
Thanks!