| ![[View Software]](images/buttons/View Software.gif) ![[View Issues]](images/buttons/View Issues.gif) ![[View Issue]](images/buttons/View Issue.gif) | Type: | Bug | Severity: | Medium | | Status: | Closed Fixed | Status Comment: | Fixed in 3.16 | | Title: | Adding Bugs in Sourceforge don't work | | Version: | 2.15 |
Navigate: 1-6
| joerg | Adding Bugs in Sourceforge don't work | 20081129 04:09 |  | Does sourceforge.net have a test project for testing such things?
If not I can't check it. | | |
|
| Raziel | Re: Adding Bugs in Sourceforge don't work | 20090417 17:30 |  | @joerg
Well, is there some kind of debug version of OWB, which i could use to try to add a bug to a sourceforge project? So that i can send you the output to give you at least some feedback...
The problem is persistant, iÂīm afraid, even with 3.10 | | |
|
| joerg | Re: Adding Bugs in Sourceforge don't work | 20090418 20:25 | | It's very likely cookies related.
Did you test it with OWB version 3.8? That was the only version which uses the OWB Cookie Manager instead of the Curl workaround, for example sending mails in GMail only works with 3.8 as well, but it has too much problems on other sites and I had to disable it again. | | |
|
| Raziel | Re: Adding Bugs in Sourceforge don't work | 20090419 20:56 | | @joerg
Actually i did
I am not sure about the version, but it could have very likely been 3.8 that
made it work.
But only for one or two tries iirc, the other times it again presented me with
a blank page, so i would say, yes, it could be the cookie problem you described.
Hmm, are you (or the devs) work on the problem or already know about the reason
why it wont work?
Thanks for the info and the great work on OWB so far
Hope you will find the time to implement some of the Suggestions/Feature
Requests some time ;-)
Keep up the awesome work joerg | | |
|
| Raziel | It "seems" to work now - checking needed | 20090707 08:51 | | I just created successfully an item on the updated Sourceforge.net PATCH tracker.
I haven't tested with the bug tracker yet, but it seems Sourceforge changed something
in the cookie (or somewhere else) code and it's working now.
Can anyone confirm? | | |
|
Navigate: 1-6
|
|
