Update to 0.7.0
-
I tried it on Windows Phone 8.1 yesterday, it's completely unusable - the hamburger menu doesn't bring up the menu as previously stated.
-
Updated from the Persona 0.1.x series to 0.2.0 this morning. Things might have changed (or might not have.)
-
Here is what it looks like, even after the change, when I press the menu button.
-
Safari on OS X Yosemite
When I click reply the frame is not fully visible. SO I cannot type well.
Also, when typing, I can watch the thread text move up one line for each letter I type in the reply box until there is nothing but white space visible above the reply pane.
-
We just updated from 0.7.0 to 0.7.1.
-
@scottalanmiller said:
We just updated from 0.7.0 to 0.7.1.
Nice!
I see that we have an approval banner and not a popup now. -
I notice that the "Users" page seems to actually work now. That had been busted for ages.
We shall see if it's just a good night on subsequent visits -
I just noticed that the tagging is fixed!!
-
The damn notification never stays away. I have dismissed it on my iPad in the past, but.....
-
@JaredBusch said:
The damn notification never stays away. I have dismissed it on my iPad in the past, but.....
It comes up every time I open a new time or refresh on any device.
-
Mark as read is broke. It says it does it but any thread that I have never viewed still shows an unread alert and if I go back to the u read tab it is still there.
-
I am prepping the cloud platform for a backup right now. 0.7.2 is out and we are going to check it out.
Also did a pretty large platform update for Ubuntu as well, nearly 300MB of updates.
-
We have an issue running the latest update...
30/7 03:03 [24643] - error: Error: [[error:theme-not-found]] at /opt/mangolassi2/src/meta/themes.js:133:21 at /opt/mangolassi2/node_modules/async/lib/async.js:589:17 at done (/opt/mangolassi2/node_modules/async/lib/async.js:132:19) at /opt/mangolassi2/node_modules/async/lib/async.js:32:16 at /opt/mangolassi2/node_modules/async/lib/async.js:586:21 at /opt/mangolassi2/src/meta/themes.js:62:6 at /opt/mangolassi2/node_modules/async/lib/async.js:251:17 at done (/opt/mangolassi2/node_modules/async/lib/async.js:132:19) at /opt/mangolassi2/node_modules/async/lib/async.js:32:16 at /opt/mangolassi2/node_modules/async/lib/async.js:248:21 [cluster] Child Process (24643) has exited (code: 0, signal: null) -
Is it still broke? Everytihng appears to be fine by me.
-
Yes, we are unable to update to 0.7.2. We fell back to the old code base. Thankfully I know enough about how fragile the update process is (it's literally never worked once) to never try to update in place.
-
Just had this happen while trying to up vote something.
-
It's possible that something is confused because of the database having been updated to 0.7.2 but not the application platform. I'm going to attempt to get a full, fresh install ready for this evening. I've upvoted since the update and sometimes it works.
-
@scottalanmiller said:
It's possible that something is confused because of the database having been updated to 0.7.2 but not the application platform. I'm going to attempt to get a full, fresh install ready for this evening. I've upvoted since the update and sometimes it works.
Just up voted this post and no error.. I have not refreshed browser or anything.
-
Search is crap as always.
-
Google it is.......
