We have a customer that is using Interchange 4.8.6. My customer was informed that there was a bug in the boa.pm. The consultant fixed the bug and sent it to my customer. The basic changes to the boa.pm file are as follows:
452,453d454
& #::logDebug(&BoA post_data response: & . ::uneval($thing) ); & 455d455
& my $sep = &&BR&&;
457c457,462
& $page =~ s/\r*&html&.*$//is;
---
& if ($opt-&{script} =~ /payment/) {
& $page =~ s#^.*?A HREF=.+\?m=$user&##si;
& $page =~ s#&.*$##s;
& } else {
& $page =~ s/\cM{2}.*$//s;
& }
459c464
& foreach ( split( /$sep/i, $page) ) {
---
& foreach ( split( /\cM|&/, $page) ) {
466d470
During cpanel's nightly refresh, it replace the modified boa.pm file. Is there anything that I can do to prevent the modified file from replacing the customize file?
452,453d454
& #::logDebug(&BoA post_data response: & . ::uneval($thing) ); & 455d455
& my $sep = &&BR&&;
457c457,462
& $page =~ s/\r*&html&.*$//is;
---
& if ($opt-&{script} =~ /payment/) {
& $page =~ s#^.*?A HREF=.+\?m=$user&##si;
& $page =~ s#&.*$##s;
& } else {
& $page =~ s/\cM{2}.*$//s;
& }
459c464
& foreach ( split( /$sep/i, $page) ) {
---
& foreach ( split( /\cM|&/, $page) ) {
466d470
During cpanel's nightly refresh, it replace the modified boa.pm file. Is there anything that I can do to prevent the modified file from replacing the customize file?
