8 years ago
4 years ago


(Reporter: mstange, Assigned: mstange)




(1 attachment)



8 years ago
Created attachment 543608 [details] [diff] [review]

There are three possible choices for the default value of Config.wooBugURL:
 1. "php/starcomment.php"
 2. ""
 3. ""

Choice 1 has the disadvantage of only working on exactly one server: That's because the server needs access to, and normal servers don't have that. ( got it in bug 638515.)

Choice 2 has the advantage of working from every server, but might not be as reliable, as Jonathan says in bug 601743 comment 24:
(In reply to comment #24)
> Only that brasstacks is probably not quite as reliable as the tbpl machine;
> it's sort of a sandbox for a lot of automation tools, and the webserver
> sometimes gets restarted, etc.

It would also make the local starcomment.php file unnecessary, unless we changed Config.wooBugURL to "php/starcomment.php" only on and merged with repo changes on every deployment.

Choice 3 looks like a good way out.
Attachment #543608 - Flags: review?(arpad.borsos)
Comment on attachment 543608 [details] [diff] [review]

Review of attachment 543608 [details] [diff] [review]:

As discussed in icq: Is the script on really allowed to write to the woo database? Need to verify that first.
Attachment #543608 - Flags: review?(arpad.borsos) → review+

Comment 2

8 years ago
We can do that when we deploy it, and back it out if it doesn't work.
Seems to have worked out in the end.
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.