Fayyaz

Hi @amie01 ,

Thank you for reaching out!

We’ve thoroughly tested all features, including backup on WP 6.7, and all features work flawlessly.

We’ve already received your support ticket along with the debug logs and will continue assisting you further through the ticket. Rest assured, we’re here to help resolve the issue promptly.

Cheers,
Fayyaz

• This reply was modified 1 day, 12 hours ago by Fayyaz.
• This reply was modified 1 day, 12 hours ago by Fayyaz.

Hi @abdullahtariq10 ,

Thank you for considering WP STAGING Pro!

1. Push Process: It overwrites only the selected files and database tables. However, incremental updates are not possible.
2. Different Domains/Servers: The staging sites are created on the same server, and the push works on the same server. The backup and restore works for different domains/servers.

For PRO-related questions, please contact us via this form. We’re here to help.

Cheers
Fayyaz

Hi @marsseven ,

The issue you’re experiencing might be due user role. To resolve this:

1. Confirm that the new account has sufficient permissions (Administrator Role) to view the staging site.
2. Alternatively, you can make the staging site publicly available.

If the issue persists, please contact through this form:?Support Form, and we’ll assist you further.

Cheers!
Fayyaz

Hi @webworks ,

The WP Staging and default login pages are loading fine. Have you made any recent changes to the staging site configurations that might have affected the login?

Please contact through this form: Support Form, and we’ll assist you further.

Cheers!
Fayyaz

• This reply was modified 2 days, 9 hours ago by Fayyaz.

HI @kashkelvis ,

The site https://johannai3.sg-host.com/stage1 shows error 403 – Forbidden. It indicates the files are not located at the specified directory stage1. The other reasons could be file permissions, .htaccess rules, or server restrictions. Please check:

1. The files for staging site stage1 are available in the directory.
2. File permissions: Folders 755, files 644.
3. .htaccess for restrictive rules.
4. Any hosting or security blocks.

Please share the debug logs from wp-content/uploads/wp-staging/logs to our support team through this form: Support Form, and we’ll assist you further.

Cheers!
Fayyaz

• This reply was modified 2 days, 22 hours ago by Fayyaz.

Hi @danbae ,

Thank you for reaching out and for your enthusiasm in working with WP STAGING. We’re glad to hear you’ve found the plugin useful!

We noticed you’ve developed a Chrome extension to address permalink structure issues on a staging site. While we appreciate your initiative,? we recommend following our official documentation on how to activate post name permalinks here:?How to Activate Permalinks on a Staging Site.

For security and privacy reasons we usually do not recommend third party chrome extensions as we have no insights into the code and don’t know what data is collected.

We also like to ask you that you add something like this to the description of your chrome extension:

“This extension is an independent tool and is not affiliated with, endorsed by, or officially connected to WP Staging, its parent company, or its developers. “WP Staging” is a trademark of WP Staging, and all brand names, logos, and trademarks belong to their respective owners. This extension is provided “as is,” without warranties of any kind.“

If you have any further questions or need assistance, please don’t hesitate to ask. We’re here to help make your experience with WP STAGING as smooth as possible.

Cheers,
Fayyaz

Hi @paul0li ,

Thank you for following up!

I can confirm I responded to your support ticket #71345 on November 9th, the same day. However, I didn’t receive a reply from you. I’ve just sent another follow-up email—please feel free to respond directly to that thread.

Hi @salker12 ,

Thank you for your kind words! We’re delighted that WP Staging and our support team could help restore your site smoothly. Your trust means a lot to us, and we’re here whenever you need us!

Hi @kimmiej5 ,

Could you please share the exact error message or a screenshot of the issue you’re experiencing? We’ve also received your support ticket, including the debug logs, and from these logs, it appears that the backups have been created successfully on multiple instances.

To help us assist you further, could you confirm this or provide any additional details by replying directly to your support ticket? I have already sent you a reply to your email.

Cheers
Fayyaz

Hi @wpapm ,

We constantly update the plugin to introduce new features, but the features you have mentioned are working as intended. Feel free to check the change logs.

1. The header should be orange if WP Staging is active on the staging site.
2. You can still select directories and databases—please share a screenshot if there’s an issue.
3. Only admins can access the staging site; confirm if WP Staging is active on the staging site.
4. Activate permalinks on the staging site to fix redirection.

I hope this helps!

If the issue persists, feel free to contact our support team via this form: Support Form, and we’ll assist you further.

Cheers,
Fayyaz

• This reply was modified 1 month ago by Fayyaz.

Hi @miranda2024 ,

Thank you for reaching out and providing the error details. The issue seems related to the mu-plugins/sso.php file causing the 500 error.

Please try this guide: Fixing WordPress 500 Error.

If the issue persists, please share the debug logs from wp-content/uploads/wp-staging/logs or contact our support team through this form: Support Form, and we’ll assist you further.

Cheers!
Fayyaz

Hi @resaresa ,

Thank you for sharing the logs. The issue you’re facing is due to memory exhaustion on your server.

To resolve this, please follow this guide: Fixing PHP Fatal Error: Allowed Memory Size Exhausted.

If you’re running a smaller server, I recommend adjusting the performance settings using this guide: Performance Settings for Small Servers. We have also received your ticket for dedicated support, and we’ll assist you there as well.

Feel free to reach out if you need further assistance!

Hi @snmpromo ,

The 500 Internal Server Error can often be due to plugin or theme conflicts. Please try this guide: Fixing WordPress 500 Error.

If the issue persists, please share the debug logs from wp-content/uploads/wp-staging/logs or contact our support team through this form: Support Form, and we’ll assist you further.

Cheers!
Fayyaz

Hi @georgebr ,

Thank you for sharing the screenshots. Based on what I can see, it seems there may be an issue with file validation during the backup restoration process. To investigate further, I would recommend you provide the complete debug logs from wp-content/uploads/wp-staging/logs. These logs will give us more detailed information to investigate the problem.

For further troubleshooting, you can also contact our support team via this form: Support Form, and we’ll assist you promptly.

Looking forward to your response!

Hi @kosmikkreeper ,

I tested your site https://learnmuscles.com, and it’s currently working as intended. If you’re experiencing the database connection error on a staging site, please ensure the database credentials in the wp-config.php file are correct, and your site doesn’t exceed resource limitations on your hosting account.

For further troubleshooting, please share the complete debug logs. You can also contact our support team through this support form, and we’ll assist you promptly.