Closed (cannot reproduce)
Project:
Statuses (Social Microblog)
Version:
7.x-1.0-beta1
Component:
Code (API)
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Nov 2012 at 02:20 UTC
Updated:
19 May 2013 at 05:49 UTC
Comments
Comment #1
8w_gremlin commentedSorry latest beta1. not dev
Comment #2
icecreamyou commentedPlease try the development build before reporting bugs. Make sure to upgrade cleanly, i.e. fully delete the old folder before replacing it and clear caches after upgrading. Also please report which Statuses submodules you have enabled and whether you have FBSMP enabled.
You're probably describing very different issues. Let's address them one at a time before we conclude anything about whether one is causing another.
Comment #3
icecreamyou commentedDo you still have this issue with the dev build?
Comment #4
liza commentedi will try this IceCream, but just an FYI: if people are updating via the UPDATE MANAGER ui, there should be some way of reminding people of doing this BEFORE hitting update. i had to roll back a whole DB due to this update. thank goodness it's a dev site, but it still means 4 hours of work lost :\
Comment #5
icecreamyou commentedReminding people to do what? Update Manager will delete the old folder and clear caches for you, but those are standard steps that are in Drupal's documentation if you're doing it manually. If you're upgrading between full point releases (as opposed to dev releases) it's your responsibility to read the release notes first to see if there are any additional upgrade steps.
Comment #6
icecreamyou commentedAny update?
Comment #7
icecreamyou commented