Forum Replies Created
-
Posts
-
It sounds like you’re experiencing an issue with anchor links on your website, where clicking a link doesn’t take you to the correct part of the page on the first try, but works on the second click. This can indeed be a puzzling issue. To better assist you, I have a few questions that will help narrow down the possible causes:
- Recent Changes: Have there been any recent changes to your website or updates to BoldGrid, WordPress, or any plugins that coincide with the issue starting? Knowing if something changed right before the issue appeared can help identify the cause.
- Sticky Header Confirmation: You mentioned that you don’t believe it’s an issue related to a sticky header requiring an offset, but could you confirm if your site uses a sticky or fixed header? Even if you think it’s unrelated, such headers can sometimes cause issues with anchor link positioning.
- JavaScript or CSS Modifications: Have you added any custom JavaScript or CSS to your site recently that could be affecting how the page loads or behaves?
- Theme or Plugin Conflict: Are you using a custom theme or have you installed any new plugins around the time the issue started? Sometimes, conflicts between themes or plugins can cause unexpected behavior.
- Browser Behavior: Have you noticed if this issue occurs across all web browsers or is it isolated to a specific one?
- Page Loading: Does your page have content that loads dynamically or images that might take longer to load? Sometimes, if the page content loads after the initial jump, it can affect the scroll position.
Providing answers to these questions can help diagnose the issue more accurately.
To troubleshoot this issue, we’ll first want to review the restoration log files to ensure everything restored correctly. Please find and share a copy of the logs.
How to View Restoration Logs
To view restoration logs, follow these steps:
- Go to your WordPress Dashboard and navigate to Total Upkeep -> Tools -> Logs.
- Look for the log file related to the restoration process. The filename should look similar to archive-1601663963.log.
- Open the log file
For more details, please visit:
https://www.boldgrid.com/support/total-upkeep/restoring-wordpress-backup/Hi Fred,
We’re trying to figure out if the archive is not being restored because of something in the archive itself, or something Total Upkeep is doing during the restoration process.
One way to help us understand this is to take Total Upkeep out of the equation.
Are you able to upload the archive to the WordPress directory and unzip the file manually? For example, if you’re in a GUI then right click on the zip and choose extract, or if you’re in the CLI then use the unzip command.
This will overwrite all the files in the WordPress directory, however it won’t actually restore the database (so technically not a full restoration).
If it overwrites the files without an error, then we can begin focusing on how Total Upkeep restores the archive, rather than the archive itself.
Troubleshooting File Restoration Issues with Total Upkeep: The “.” File Name Scenario
It appears you’re encountering a unique issue with Total Upkeep where the restoration process is failing due to an attempt to restore a file named “.”. This might indicate a misunderstanding by the backup utility in handling system directories or files. The “.” typically represents the current directory in Unix-like operating systems, which should not be an object of restoration by itself. This issue could possibly be linked to the compressor used during the backup process.
Understanding Compressors
Total Upkeep utilizes different compressors to create backups, including PclZip, ZipArchive, and System Zip. Each compressor has its nuances, with some being more suited to certain hosting environments or specific use cases. For instance, System Zip generally offers faster compression with lower performance costs, while PHP-based Zip options (PclZip and ZipArchive) provide more flexibility.
Changing the Backup Compressor
Given the nature of your issue, switching the compressor might help. Here’s how you can adjust the compressor settings within Total Upkeep:
- Access Total Upkeep Settings: Navigate to Total Upkeep -> Settings -> Backup Process.
- Select Backup Compressor: Choose your preferred Backup Compressor among PclZip, ZipArchive, or System Zip.
- Save Settings: After selecting a different compressor, click Save Settings to apply the change.
- Test with a Manual Backup: It’s recommended to run a manual backup to verify the new compressor works as intended without encountering the “.” file issue.
Why Try a Different Compressor?
Switching compressors can resolve issues related to file handling and compression algorithms, potentially bypassing the problem causing the restoration failure. While System Zip is generally recommended for its efficiency, trying out PclZip or ZipArchive might yield different results that circumvent the peculiar “.” file restoration error.
Additional Steps
- Review Backup Contents: Before attempting restoration again, review the backup contents to ensure no system directories or placeholder files (like “.”) are included inadvertently.
- Consult Documentation: Visit our support page for more on changing compressors and troubleshooting backup issues: Change Backup Compressor.
Hi David,
I’m sorry to hear of the issues you’re having. I can understand the frustration, and I appreciate you working with us on this. I wanted to offer another set of eyes here. Taking a step back, it looks like we’re dealing with two issues:
- When you click on various links in the dashboard, you’re getting error messages.
- Your backups are not completing.
In order to troubleshoot why your backups are not working, we need to see a copy of the backup logs. However, you cannot access your logs because of the error messages that you’re seeing. So, the first thing we need to do is figure out exactly what those critical errors are.
There are at least 3 ways to find out what those critical errors are:
- The critical errors have been emailed to you.
- If you cannot find that email, you may be able to use a plugin to view your WordPress error logs. If you wouldn’t mind trying this please, there’s a plugin called Error Log Monitor that may be able to help.
- If all else fails, your host may be able to review the error logs and provide you with the fatal errors.
Once you can get a copy of the fatal errors, please let us know and we’ll be happy to assist further.
Thanks again,
– BradHi Alex,
We’ve been working a bit throughout the week on this update. We’ve got the Amazon PHP SDK updated to version 3, and we also updated a few other things as well.
These features have been released in Total Upkeep Premium 1.5.8.
Are you able to update your version and test? You can’t actually click “Update” within WordPress to get this new version. Please instead click the link above to download the zip file, and then upload that to WordPress.
Thanks for all patience through all this, and we’re waiting to hear how everything goes!
– BradHi Alex,
This week I was able to upgrade our version of the aws-sdk-php library from version 2 to 3. There was some development work required. I did run into some snags – unfortunately I wasn’t able to get a release out this week like I wanted.
I think we’re ready to release the updates for Total Upkeep Premium though, we’re in the final testing phase now. It’s generally not a good idea to release on Friday’s, but hopefully early next week we’ll be able to release the updates.
Thanks for your patience Alex – we’ll keep you updated.
– BradHi Ravi Jayagopal,
I’m one of the developers of Total Upkeep.
In vendor\guzzlehttp\guzzle\src\ClientInterface.php we have:
/** * Client interface for sending HTTP requests */ interface ClientInterface extends HasEmitterInterface { const VERSION = '5.3.1';It looks like both plugins are including the aws-sdk-php library:
- plugins/S3MediaVaultPro/vendor/aws/aws-sdk-php/
- plugins/boldgrid-backup-premium/vendor/aws/aws-sdk-php/
We are running aws/aws-sdk-php version 2.8.31. Which version are you running?
I also mentioned you in the GitHub issue. Thanks for your help!
Hi Katy,
The answer to your question is that Managed WordPress Hosting could be either a shared account or a vps. The term “Managed” in Managed WordPress Hosting generally only means that your hosting provider is going to help you managed certain parts of your WordPress site.
For example, if you don’t use the best backup plugin we know, Total Upkeep (a BoldGrid plugin!), to backup your WordPress site, your managed hosting account may help you manage backups by doing them for you automatically.
You can follow these links to learn more about Managed WordPress Hosting and WordPress VPS Hosting.
DreamHost and InMotion Hosting offer managed hosting accounts that you may want to check out as well.
Let us know if you have any further questions!
– BradHi Zoheb, I just released a new tag, “branch.issue-376.202010021533” that should resolve this issue. Are you able to help us test this version?
I believe you’ve used WP Rollback to switch to different tags before. If you’re familiar with doing that, please give branch.issue-376.202010021533 a try and let us know if it helps. If you don’t know what I’m referring to, please see https://www.youtube.com/watch?v=LeLEdcaz4uk&t=160s
Hi George, I’m not 100%, but I believe this could be a “container” vs “container-fluid” issue. I updated one of our tutorials and wrote a little more information on this. Please see the “container vs container-fluid” section of this page:
https://www.boldgrid.com/support/page-builder/create-block-structure/#container-vs-container-fluid
I also recorded a video that explains this further. The video is embedded in that article, but you can also see it here:
If this doesn’t help, if you can provide a specific example, we’ll be more than happy to review further.
Hi giacomo. I’m sorry to hear you’re having trouble activating W3 Total Cache. Can you answer the following questions to help us troubleshoot further please:
- Have you ever installed W3 Total Cache before on this site, or is this your first time?
- Are you getting any error messages? If not, are you able to see any warnings or errors in your server logs? (You’d probably have to contact your web host if you’re not sure)
- Do you have any existing cache setup? For example, do you have another caching plugin installed, or do you have redis / mecached installed on your server?
Hi Matthew,
I’m very sorry to hear of the fatal error you’re getting when setting up Google Drive with the Total Upkeep WordPress backup plugin.
Please check your site admin email inbox for instructions.
Are you able to share the full error message at the bottom of the email that was sent to you? We should be able to resolve this after getting a copy of the email.
Thanks,
– BradHi Bill,
There are two ways to upload your WordPress backups to Google Drive. You can do a manual backup, or you can schedule an automated backup. It looks like you already know how to do a manual backup, a scheduled backup is not much harder.
To configure scheduled backups start off by going to Total Upkeep > Settings. On the Backup Schedule tab make sure you have days of the week selected, and a time of the day selected. Click the Backup Storage tab. Under backup storage, select Google Drive. Then at the bottom click save changes. That’s it! you have backups scheduled and they will automatically upload to Google Drive.
I created a video that walks through this:
We’re here to help if you have any further questions.
Thanks!
– BradHi Scott,
I wanted to piggyback off of what Jesse shared, and create a video to show you how to make these changes in the Customizer. I hope this helps!
Thanks!
– BradHi rd,
If you don’t have all of the drag handles within the editor, it may be because the page you’re editing doesn’t have the code for rows and columns in it. When you create a page from gridblocks those rows and columns are included by default, but sometimes they may be missing if you’re creating a new page starting from a blank page.
The latest version of the BoldGrid Editor actually resolves the issue you’re describing. I recommend that you upgrade your plugins.
