Forums : Feedback Forum
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Choosing my stack as a guest
Go to this url while logged out:
http://www.ohloh.net:7502/stacks/16910
Notice that the 'Stack this' buttons aren't there
Now filter for projects containing php, and those buttons appear, yet nothing happens when you click them.
Hi Alex,
Yes, it looks like you found a display bug. Unless you are looking at your own stack suggestions (and when you are logged out you by definition are not), you should not see the stack/ignore buttons. Our internal logic is thankfully smart enough to reject your attempt to edit some else's stack.
I'm personally responsible for this JavaScript rat's nest. :-) We are in the midst of a big UI overhaul, so I'll make sure this gets fixed in the next release.
BTW how did you end up at port 7502? I'll have to figure out how to disable that....
Robin
O.O I never noticed that.....
Thanks for taking this up :) , and I look forward to the new UI.
By the way, are you aware about the google maps developers key popup that appears every time you go to a page that uses google maps?
Google maps developers key popup?
No, I have no idea what you mean. Is this because you are erroneously browsing on port 7502?
I was just going to comment on the Google Maps issue, but for another case.
Occasionally the links in the footer point to alternative domains ohloh.org and ohloh.com. When you go through those addresses, the Google Maps widgets all fail to load, alerting you that the page is using an invalid authorization key.
Ahh, shucks, I understand what is causing this now. It's a messy caching problem.
Thanks for reporting this. I thought we had resolved these problems, but I guess not. I'll be looking into it.
Thanks for the help,
Robin