Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thank you. I’ll keep you updated with our progress on this.

    Yes, our plan is to keep the list of failed pruned backups on UpdraftPlus. So that they can be clearly seen and deleted manually from UpdraftPlus. They will also be included in the automatic pruning on the next scheduled backup. This way, the leftover backups can be deleted again on each scheduled backup.

    If you don’t mind, could you please tell me how many sites you back up to a single Google Drive account? And, what is the average size of the backup file on each site?

    Hi,

    I’m so sorry that you still have this issue. We’ve identified that this Google Drive queries per minute issue could happen on these two conditions:

    1. Uploading the backup. The issue might cause the backup upload to fail. However, we’ve handled this issue by retrying the upload on the next resumptions until it succeeds. If the backup process reaches the maximum number of resumptions, and it still fails, you’ll get informed on the backup email report, which files failed to upload:

      Errors encountered:
      * Google Drive: backup_2026-01-04-0731_37_d67d91513b7d-others.zip: Failed to upload to Google Drive


      The backup files that failed to upload won’t be deleted from your server. Only the successful ones will be deleted from your server. So, your backup files are safe.
    2. Pruning the backups. The issue could cause the deletion of the backup files to fail. You’ll get informed which backup files failed to delete in the backup logs:

      0062.751 (0) Google Drive: backup_2026-01-04-0826_37_f83696719e91-plugins.zip: Deletion failed: file was not found
      0062.753 (0) Google Drive: backup_2026-01-04-0826_37_f83696719e91-themes.zip: Deletion failed: file was not found

      However, I admit that the backup sets are still removed from the backup history even if the file deletion in the Google Drive fails. And it could lead to confusion. Currently, improving the backup history is our focus to address this issue.

    Regards,
    Hisman

    Hi,

    Currently, we are in the process of improving our code related to this issue. We’ve also found that when the file pruning fails, the backup set gets removed from the backup history, causing an incomplete set of backup files to be left over in the Google Drive.

    Thanks,
    Hisman

    Yes, that’s correct. The quota needs to be adjusted from our Developer Console. Sorry for not being clear before. We’ll also be improving our code to handle this issue better when it occurs. I’ll keep you updated with our progress regarding this issue. Thank you for your patience.

    Best regards,
    Hisman

    Hi,

    I’m from the development team. I can confirm that we can replicate the issue on our end.

    The root cause of this issue is the Google Drive API’s limitation on queries per minute. The default limit is 12,000 queries per minute per user. Under normal circumstances, the chance of hitting the limits is low, but it can get higher if we have multiple websites backed up to one Google Drive account simultaneously.

    The good news is that Google allows the limits to be increased via the Developer Console, but an approval from Google is needed and it might take some time for Google to approve it. We also will improve our Google Drive integration to handle this issue better.

    Regards,
    Hisman

    hisman

    (@hisman)

    Yeah, you must add <?php on top of functions.php.

    You’re welcome. 🙂

    hisman

    (@hisman)

    Technically it’s possible, most theme developers nowadays don’t put the restriction code in their themes. But, from moral, ethics, and legal perspective, you aren’t allowed to do that.

    Please, just buy the multisite license for that theme to support the dev. Or, even better try to find theme that has GPL license, many high quality themes have GPL nowadays. And you have more freedom with GPL themes. WordPress has some great lists of devs that sell the GPL themes : https://ww.wp.xz.cn/themes/commercial/.

    hisman

    (@hisman)

    Apperance, Editor doesn’t have capability to edit the js files, it only let you edit css and php files, so don’t worry.

    Instead, just add script to load the js in your functions.php. Try this (It works for me) :

    function bus_leader_child_scripts() {
    	wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' );
    
    	wp_enqueue_script( 'bus_leader-scripts', get_stylesheet_directory_uri() . '/js/bus-leader-scripts.js', array( 'jquery', 'masonry', 'bus_leader-enquire', 'bus_leader-superfish' ), '20141026', true );
    }
    add_action( 'wp_enqueue_scripts', 'bus_leader_child_scripts' );
    hisman

    (@hisman)

    If you want to get rid the parallax and also the image, you need to delete :
    bus_leader_get_header_container() in header.php

    If you want to keep the image and only get rid the parallax effect :

    • Go to style.css and change position of .header-container .header-image from fixed to absolute
    • Go to bus-leader-scripts.js and delete :
      $(window).scroll(function(e){
      		var scrolled = $(window).scrollTop();
      		$('.header-image').css('top', -(scrolled * 0.3) + 'px');
      	});
    • Don’t forget to load bus-leader-scripts.js instead of bus-leader-scripts.min.js
    hisman

    (@hisman)

    I think it will not impact the performance anymore. From this answer, he said that the code is designed to work asynchronously, so it doesn’t really matter anymore.

    hisman

    (@hisman)

    I think it’ll work in either way.

    hisman

    (@hisman)

    Hi,

    You can navigate to Apperance > Theme Options. There is slider option in featured slider tab. Just choose disable option in there.

    hisman

    (@hisman)

    Hi,

    Yes, you you can add that information in wp-config.php. Even if it is not there yet, you can just add it in the last line of wp-config.php

    From what I read in codex, the code should be like this :

    define( 'FS_METHOD', 'ftpext' );
    define( 'FTP_HOST', 'ftp.example.org' );
    define( 'FTP_BASE', '/path/to/wordpress/' );
    define( 'FTP_USER', 'username' );
    define( 'FTP_PASS', 'password' );
    define( 'FTP_SSL', false );
Viewing 14 replies - 1 through 14 (of 14 total)