Version: 0.4 (using KDE 4.3.2) OS: Linux Installed from: Debian testing/unstable Packages I'm using Audex, which uses libkcddb to submit changes to the freedb.org server. Anytime I submit something I get a "successful test submission" back from freedb.org. Looks like libkcddb has test-submit@freedb.org coded into it somewhere rather than submit@freedb.org. Is libkcddb mature enough to change to really submit modifications? Hope so! :) Thanks
(In reply to comment #0) > > Looks like libkcddb has test-submit@freedb.org coded into it somewhere rather > than submit@freedb.org. > Indeed there is test-submit@freedb.org: libkcddb.kcfg:64: <default>test-submit@freedb.org</default>
Hm. I changed test-submit@freedb.org to submit@freedb.org in the file /usr/share/kde4/config.kcfg/libkcddb.kcfg Then I restarted my computer and then KDE to be sure the config file was read again. when I submit changes to freedb.org I still get a "Successful freedb test submission", not an actual submission. Also, I'm using the http method of submitting, not smtp. It appears there is another place that libkcddb is getting the email address from. ?
http://www.freedb.org/en/faq.3.html#21 says: "When submitting via e-mail, the submissions have to be sent to freedb-submit@freedb.org." @ CSights: Could you please try again with <default>freedb-submit@freedb.org</default> in libkcddb.kcfg? Thanks.
If you can provide the information requested in comment #3, please add it.
That's not really necessary, it's disabled in the code right now. Depending on if you're using the smtp or http submit method, it's either disabled from the e-mail address in libkcddb.kcfg if you're using smtp, or the line header += QLatin1String( "Submit-Mode: test\n" ); in libkcddb/httpsubmit.cpp if you're using http (where 'test' should be changed to 'submit' to enable submitting again). However, since at the moment no one is actively mantaining the library, no one has gotten around to enabling it.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.