When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
Related
I have absolutely no idea why, but on 2 websites (2 websites that I professionnaly work on, and they havent been hacked or compromised), my Chrome console keeps clearing every 500ms.
Which is pretty annoying.
I desactivated all extensions. Tried private browsing. It's the same thing.
I uninstalled chrome as well as my extensions. Same.
When I try to reproduce it on someone else's computer, I cannot.
When I use another Chrome session the issue does not happen.
I have absolutely no idea how to get rid of this or what is the exact cause of the issue.
The code running is :
setInterval(function(){console.clear();console.info('Console was cleared by browser extension.');},500);
Since I unfortunately do not seem to find the reason, my only question will be : would there be a way to desactivate that code or postpone the setinveral to a bigger number?
Thanks !
In Chrome, on the developer tools, click on the settings icon, and tick the the "Preserve Log" option so the console is not cleared.
If your websites happen to be ecommerce (Magento specially) I'll advice you to check your code well for unknown js. This is one of the "symptoms" of the Magecart credit card skimmer. Preserve log option
When I try to delete or edit a node in my realtime database, I always get the info that I have to select a key with lesser elements to change something, else it is in read-only modus.
But when I click a low level node, nothing happens. So I actually can change nothing in my DB from console :(
A week ago I didn't see this warning and everything works great!
Any idea how I can get back to working version?
I also think the german translation is not very good, because it tells me that I should activate another mode. In English it says, that the mode got activated.
You're mixing three things here:
Your database console switched to read-only mode, which happens when you have a certain amount of data under it.
The warning is badly translated. Please file a bug report for that.
The database console doesn't handle clicks correctly anymore. I already reported that internally last week, and added your report to it. This bug has been fixed internally and will go into production by May 23.
Update 5/24/17:
Problem resolved. Works now.
It seems the ability to click on a child node and promote it to be the top element of the tree is broken. Doesn't work for me either, even on a small database that is not in Read-only & non-realtime mode. I'm almost sure it was working a day or two ago.
I'm seeing the failure when using Chrome. Just tried Internet Explorer. Its works there.
First off I apologize if there has already been a similar question before, I honestly couldn't find any.
I'm currently developing a chat using Firebase and thanks to the decent docs I'm making good progress so far, so this isn't really the issue here. However, while testing I stumbled across a little issue that might possibly be a bug.
For managing presence in my chat, I am pushing values to a location that corresponds to my user's unique ID. This pushed value is then removed on disconnect.
By doing it this way, I can reliably determine a user's status without worrying about his number of concurrent connections to my Firebase (i.e. browser tabs).
This is actually working fine with Firefox, Chrome and Safari, but there seems to be an issue with Opera. When using Opera, if you close the tab in which the chat is running, the value that should be removed on disconnect is not. It will be removed eventually after like 2 minutes or so, but it is taking way too long, considering that the same thing is happening instantaneously when using another browser.
Out of curiosity I've tried the presence example using Opera and I was able to reproduce the exact same behavior. If I open the corresponding Firebase in another tab, then run the example, enter a name and finally close the tab that the example is running in, I can see that the value in the corresponding Firebase is not removed as I close the tab.
I would appreciate if you could tell me if this is just me doing something wrong or if it is actually a bug.
Regards
Muddy
Opera has a different model for page transitions than all other browsers. Most browsers fire events when loading and leaving a page. Opera actually keeps old pages hot in memory in order to make the back button faster. When you click "back" in opera it's actually resuming the old page.
As a result, there's no way for us to know exactly when someone has left a page in Opera. As a result, we're forced to simply wait for a server timeout to determine someone has left.
So, short answer, onDisconnect operations DO work in Opera, but they might take a couple of minutes to take affect. In all other browsers the operations will happen immediately if the connection was terminated cleanly, and after a few minutes if it was not.
I was having this issue for several days. I finally figured out a fix for ASP.NET programmers, and I figured I would share.
Problem
After setting a breakpoint, and then debugging my breakpoint would turn yellow with an exclamation point. When hovering over the breakpoint it would say "The breakpoint will not currently be hit. No symbols have been loaded for this document.”. I tried cleaning, rebuilding, changing various settings through my project and visual studio. Nothing worked.
Solution
I was digging around in the Solution settings. I noticed that under "Web" tab my Start Action setting was set to something other than "Current Page". After setting it back to current page everything worked out.
I hope this solves the issue for other's like me that were exhausted after trying every other suggestion/answer they could find on the internet.
The issue only happens to me on ASP.Net Projects
Right Click the Web Project
Select Property Pages
Start Options
Make sure Use current page is selected (as shown below)
This happens because your project still has errors, so run the last correct version.
Correct your mistakes, surely it is the error "CodeBehind" change it to "CodeFile" and surely the errors disappear, you can return project run without errors.
We have an application running flex sdk 4.5 and have recently encountered an issue with textInput fields which we have not been able to reproduce on our end for the better part of a month now.
Here are the symptoms:
Users opens an input form which contains several input fields (combo boxes, calendars, text inputs, etc)
User clicks inside a text field
Users types (obviously!)
** Nothing appears in the text input - we have validators on some of these fields and they do kick in properly (ie. user sees red box around textInput disappearing)
User moves cursor outside of text input field and text appears
Give or take, this is the test case we've been provided. We have been unable to reproduce this and I'm reaching out to see if anybody has heard of issues like this in the past.
They are running our flex application in the following environment:
Windows XP SP3
IE 7.0.5730.13 (locale = en-gb)
Flash Player 10.3.181.14
Upgrading either of these components is not an option. Installing the flash player debugger is not an option either.
Now we've setup a pc exactly the same way as they have on their end and still haven't reproduced. So we're really stuck at this point :)
Any suggestion is greatly appreciated. I'll provide any additional info needed.
-Marc
Feb. 2nd 2012 - Update
As I noted in my comment reply to shaun, it seems our customer was more or less precise in their description of the issue. We ran a webex session with them this morning and actually saw the issues first hand.
Here's what happens:
- User loads our application via its url
- User is able to input data and pretty much do any function for a 'random' time period
- All of a sudden, the issues start (there are more symptoms than just the one I originally mentioned):
1. Users type in text input fields and they won't see the text appear until they move the cursor out of / into any other component (could be entering an hbox, exiting a text input field, etc)
2. Combo boxes behave more or less the same. They can drop them down, but then the mouse wheel no longer refreshes the list. It actually scrolls in the background, but until the user moves the mouse, the list does not refresh
3. We also communicate between the server and client via an amf channel. The events make it to the client, but again, they won't see the screen refresh until they move their cursor.
So basically, the application still seems to work, but the screen is no longer refreshing. Could it be something to do with an invalidate / update of the display list that doesn't kick in? We'd like to get them to install the debugger version of FP, but that doesn't seem to be an option.
Another thing to keep in mind: they have a VERY bad internet connection. They average around 1-1.5mbps (megabits) which is enough for our app, but I just thought I'd let you know.
We learned that they also use a Citrix presentation layer to deploy IE 7 to the end users. We've received confirmation from the end user that even if they launch IE on their workstation (not through citrix), they get the issue also.
Another note is that we've seen no errors in our web server, jboss or application logs...
So that's the update I've got... anyone have more thoughts on this? We've more or less discarded the fonts being an issue at this point since the issue affects more than just 'fonts'. Is everything on the screen not updating anymore.