bruandet

Hi

It cannot do that. Its purpose is to hide or delete unwanted elements in the back-end, such as banners, images, ads (and basically any HTML elements).

Hi,

It’s a known issue, I reported it six months ago to core.trac.www.ads-software.com: https://core.trac.www.ads-software.com/ticket/43358
But it is still in the “Awaiting Review” state.

You can edit wp-admin/includes/file.php, search for:

   // Make sure PHP process doesn't die before loopback requests complete.
   @set_time_limit( 300 );

   // Time to wait for loopback requests to finish.
   $timeout = 100;

Insert @session_write_close(); so that it looks like this:

   // Make sure PHP process doesn't die before loopback requests complete.
   @set_time_limit( 300 );
   @session_write_close();
   // Time to wait for loopback requests to finish.
   $timeout = 100;

Obviously, next time you update WordPress you will likely need to apply the above changes again.

I can’t paste the exact command on this forum because it makes use of ‘backticks’; the forum interprets them as markdown elements.
Here it is on pastebin: https://pastebin.com/JY9UZkww

• This reply was modified 7 years, 7 months ago by bruandet.

I can see your problem: your server does not have the $PWD environment variable defined. WPTerm uses it to retrieve the current working directory.
It is possible to use the pwd command instead.

1. Search and remove this line of code:

$command = sprintf( "ABSPATH=%s;cd %s;%s 2>&1;echo [-{-%s-}-]", $abs, $cwd, $cmd, '$PWD' );

2. Replace it with this line:

$command = sprintf( 'ABSPATH=%s;cd %s;%s 2>&1;echo [-{-$(pwd)-}-]', $abs, $cwd, $cmd );

If it works, I’ll make the change to the next update of WPTerm.

• This reply was modified 7 years, 7 months ago by bruandet.
• This reply was modified 7 years, 7 months ago by bruandet.
• This reply was modified 7 years, 7 months ago by bruandet. Reason: Edited because backticks in the code secion messed with the forum code tag

You can try to debug it:

1. Go to the “settings” tab, select “system” for the PHP function and save the settings.

2. Open “wpterm.php” and locate this line:

// Run the command:
list( $res, $ret_var ) = @run_command( $command, trim( $_POST['exec'] ) );

Right below, add this code:

@file_put_contents( '/full/path/to/debug.txt', "-\$res = {$res}\n=========\n-\$ret_var = {$ret_var}\n" );

3. Replace /full/path/to/debug.txt with the full path to the debug log you want to create (it must be writable).

4. Go back to the terminal and enter the uname shell command.

5. Check the debug.txt log and paste its content here.

6. After your test, remove the line you added to the “wpterm.php” file.

Hi,

This error is displayed when the data returned (via AJAX) by the command is empty.
Did you try to select another PHP function for command execution in the “Settings” tab?

There are approximately 1 or 2 minutes between the time we upload the new release and the time we adjust the readme.txt to match the latest release. That seems to be the issue.