That code was from the version from a modded build on my test bed. it was probably

 $scripturl = "$boardurl/Dobackup.$yyext"; 

for your version.

okay, thanks, works. but this line was not there.

our $scripturl = "$boardurl/Dobackup.$yyext"; 

old version ?

This should not be a problem with 2.7
The problem you're having with 2.6.12 is that DoBackup.pl is part of a mod.

The 2.6.12 version of DoBackup.pl find:

 require Paths;

 if   ( -e ('YaBB.cgi') ) { $yyext = 'cgi'; }
 else                     { $yyext = 'pl'; }
 our $scripturl = "$boardurl/Dobackup.$yyext"; 

and replace with

 our $script_root = $ENV{'SCRIPT_FILENAME'};
 if ( !$script_root ) {
     $script_root = $ENV{'PATH_TRANSLATED'};
 }
 $script_root =~ s/\/Dobackup[.](pl|cgi)//igxsm;
 push @INC, $script_root;
 require Paths;

 my $yyext = 'pl';
 if   ( -e ('YaBB.cgi') ) { $yyext = 'cgi'; }
 else                     { $yyext = 'pl'; }
 our $scripturl = "$boardurl/Dobackup.$yyext"; 

After the server change. YaBB 2.6.12. Could also be at 2.7. Pop up. Is not tested yet.

Quote:

Unfortunately it does not work either. But let it be good, I just reopened the forum. The problem is simple, the paths on the new server are very different. Even an adjustment did not work. YaBB 2.7 is now working. There I find in the endurance test so far no errors.

My goof. 
Before the 'require Paths' it should be:

 our $script_root = $ENV{'SCRIPT_FILENAME'};
 if ( !$script_root ) {
     $script_root = $ENV{'PATH_TRANSLATED'};
 }
 $script_root =~ s/\/BackupFix[.](pl|cgi)//igxsm;
 push @INC, $script_root; 

Now I get Internal Server Error. I'll send you the FTP data and the URL via PM. The error would certainly not occur if I could make a direct move from Plesk to Plesk. The forum went well for 4 years. If it can not be otherwise, then I put it on again. I do not want to extend the contract from the old server unnecessarily, it costs all the money.
I've set up a test domain on the new server so I can get it to work. Actually, I wanted to play YaBB 2.7, but the installation of the mods does not really work.

Find :

require Paths; 

add before:

 $script_root =~ s/\/BackupFix[.](pl|cgi)//igxsm;
 push @INC, $script_root; 

Oddly enough, this one didn't throw errors in 2.7 on your server.

I still get this error message.

Quote:

I will probably have the changes in the SVN sometime this evening (my time).

I still think there was a folder ownership misconfiguration with the Plesk server set up.

Executables in the cgi-bin should run as 'nobody' (which is basically the same as 'everybody') and should 'own' all the files and folders it can find - which is why Perl scripts have the potential of so extremely dangerous in the hands of malicious people or people who don't know what they're doiing. (And why we have to be so careful to not allow bad code to get in from the outside.)

But if YaBB's script was trying to create a file or write to a file in a folder that was 'owned' by someone other than 'nobody' then it couldn't write or create the file.

That's crazy. The new server can be YaBB 2.7 and I got along with chmod 755.
However, he does not find the path here either. I am waiting for the SVN.

The same FTP data, again boardmod.

I could not even start the setup on the old server.

YaBB test is still on the old server. But I'll leave it that way, so that we have the certainty that YaBB 2.7 runs everywhere. Is of course no guarantee.

However, you have no chance with the new Plesk. (Web Admin Edition).

Please PM me the FTP to where your 2.7 install is and I'll check it later today or tomorrow. It may be something simple that went wrong - or not.

I doubt the current build of 2.7 will work on your new server as the Perl installed on it doesn't like getting the required path using Cwd

Great, that works the new server. That was a lot of work and then find and test the right tool. Now I'll see what he says to yabb 2.7. The old server does not want to.
You can see how different Perl responds on other servers.

Got in and got it.

Apparently the Perl on your new server didn't like using the $cwd variable even though that bit of code is what's recommended by other perl Mongers dealing with '.' being disabled.

Deriving the proper path from $ENV{'SCRIPT_FILENAME'} worked. This is the fix that will be going into 2.6.12 on the SVN.

In YaBB.pl changing this:

     # Make sure the module path is present
     require Paths;
     push @INC, "$boarddir/Modules";

     if ( $ENV{'SERVER_SOFTWARE'} =~ /IIS/sm ) {
         $yyIIS = 1;
         if ( $PROGRAM_NAME =~ m{(.*)(\\|/)}xsm ) {
             $yypath = $1;
         }
         $yypath =~ s/\\/\//gxsm;
         chdir $yypath;
         push @INC, $yypath;
     }

     $yyexec      = 'YaBB';
     $script_root = $ENV{'SCRIPT_FILENAME'};
     if ( !$script_root ) {
         $script_root = $ENV{'PATH_TRANSLATED'};
     }
     $script_root =~ s/\/$yyexec\.(pl|cgi)//igxsm; 

to this:

    $script_root = $ENV{'SCRIPT_FILENAME'};
     if ( !$script_root ) {
         $script_root = $ENV{'PATH_TRANSLATED'};
     }
     $yyexec      = 'YaBB';
     $script_root =~ s/\/$yyexec\.(pl|cgi)//igxsm;
     push @INC, $script_root;

     # Make sure the module path is present
     require Paths;
     push @INC, "$boarddir/Modules";

     if ( $ENV{'SERVER_SOFTWARE'} =~ /IIS/sm ) {
         $yyIIS = 1;
         if ( $PROGRAM_NAME =~ m{(.*)(\\|/)}xsm ) {
             $yypath = $1;
         }
         $yypath =~ s/\\/\//gxsm;
         chdir $yypath;
         push @INC, $yypath;
     } 

I made related changes to AdminIndex.pl and managed to get a backup.

Yeah, I'm going to need FTP access so I upload a copy of env.pl and see what's happening.

Since the YaBB 2.6.12 Setup completed YaBB.pl should run with $cwd added to the @INC array.

You can also try replacing the

push @INC, $cwd;  

with

use lib "$cwd";