I have a problem with my Jhipster application. In my navbar, I have a couple of "inbox" icons, and i want them to have a "unread messages" notifications on them.
The number of unread messages depend on some of the data i got in the application.
I managed to make this right, but for some reason the notifications don't appear immediately after logging in, you have to reload the page first, which kind of kills the point of the whole notification thing.
Been looking for an answer everywhere, hope you can help me out.
Thanks in advance!
Your navbar is probably using some data returned from an $http or $resource service but you use it before the Promise gets resolved.
Related
I'm wanting to sign into Mural automatically, but their web design requires a keystroke, but I can't get my design to work. I have tried, both global send keys and send events. Furthermore, the click center input doesn't seems to register. :/ Any suggestions? The delay is implemented as a recommendation by another user:
If I understand correctly you are trying to sign into this page. I have succesfully written in its email textbox just recognizing the field with the application modeler (browser mode) and a Write stage.
As esqew suggested in the comments then when I tried to sign in there was an error saying "an email is required". The solution for me was to use Navigates, first with "Global Send Keys" action and then "Click Center" for the button.
If it is not that website and it's another one it might be helpful if you add a link to the website in your question.
There could be several reasons why your send keys or the click events are not working, in order to help you it would be necessary to see the configuration inside the stages in your object.
As clarified by jnch, the problem is resolved by using global send keys and then using another navigation stage with click center. I believe this fixes the problem since the website demands borderline human interaction.
Today I was starting a web app I am developing that embeds a Spotify widget player in an iframe. Strangely it doesn't load the widget and instead reports this message
"open.spotify.com redirected you too many times"
I went to Spotify Widget examples page and it shows the same behaviour (here's a ).
I cleaned the the cache, cookies, but it doesn't seem to sort this. Should I assume there is an API request threshold that I've just hit?
Has anyone have had the same problem and has solution?
Thanks
That was a temporary issue in our service. It's resolved now.
The _actions_on_google_ context stopped appearing in the contexts section, and I think this may be a clue to what's gone wrong.
It's just stopped doing anything, it'll get the required parameter then the JSON says it's sent it to webhook but there's only the 'secure' context in that (I remember seeing an actions on google one by default). When I remove my custom context it doesn't help, and I've updated firebase.
How do I get this back?
I think the issue was that I had deleted something in the code, maybe the }); at the end.
If you have the same issue, go OCD through your code and match everything together to check it's all good.
I have set up mozpay in my app. When I send the signed jwt with the post-back URL to the app, and then the app uses it with mozpay, during simulation, the post-back URL gets hit 6 times. I wanted to know if that's intended. If so i can work around it, but if its not intended i would rather fix that problem.
Is it possible that the 6 post-backs only occur during simulation?
Also is this any different in the charge-back URL?
Is there a setting that I can set in the signed jwt to change this?
If there is some documentation on this, I haven't been able to find it, and I would greatly appreciate a link.
What you describe is expected behavior. Since your postback URL was not responding correctly, Mozilla's server retried the post 5 additional times before giving up. As you mention, when you fixed the transaction response you no longer saw so many requests.
There was an answer here, but I dont see it anymore. The answer was fairly correct.
We were sending back "webpay: {transactionID}" what we didnt realize is that {transactionID} includes the text "webpay:" So all we had to do was send back "{transactionID}" instead.
I would set as the answer the person who posted, but i no longer see the post. Thanks.
I really hope someone can tell me more about what's going on, because I spent days searching the net and for the life of me can't say what is going on.
Here's what happened. I have a website 4nieuws.nl . On every article's page I put a like button using the Javascript SDK. All worked well. On facebook I created a fanpage for the website, facebook.com/4nieuws and every now and again I would copy an interesting article there. The like button and Javascript SDK on 4nieuws.nl uses the APP Id from an app I created specifically for that purpose.
Then I thought I might automate to publish the most popular articles on the fanpage using the PHP api. I set about getting the proper authorization key using the sequence explained on this page: http://www.typeoneerror.com/articles/post/permanent-facebook-sessions-and-posting-as-a-page
For this to work I authorized the previously mentioned app to publish on the facebook fanpages that I am admin of. And this works.
Now for the strange part. Ever since I authorized the app, if I go to 4nieuws.nl and like a page, or even 'post to facebook', the button shows 1 more like. But the like message never shows up on my personal wall. My wife, logged in to her own facebook account, gets a notification that I liked a page, but when she clicks the notification she is sent to a Facebook 404 page. When I subsequently reload the article, my 'like' is not there anymore.
Has anyone ever come across something like this ? I'm a bit anxious because I am not sure if other peoples likes on 4nieuws.nl are working as it should. I do see likes on pages but have no idea if those likes are actually registering on peoples walls.
Any help greatly appreciated.