Julia Golomb

The errors you’re encountering in class-wp-hook.php are indicative of a problem with the way hooks (actions or filters) are being used or executed in your WordPress installation. The specific errors suggest that there’s an attempt to iterate over something that isn’t an array or object, which is causing PHP to throw warnings. Here’s how you can approach troubleshooting this issue:

1. Check for Recent Changes:

• Reflect on any recent changes made to your site. This includes updates to plugins, themes, or WordPress core, as well as any custom code modifications. If the issue started occurring after a specific change, that change is likely the culprit.

2. Theme and Plugin Conflict Check:

• Even though you’ve deactivated all plugins, it’s worth checking if the issue persists with a default WordPress theme (like Twenty Twenty-One). If the issue resolves with the default theme, the problem might be with your current theme.
• Reactivate your plugins one by one, testing each time to see if the issue reoccurs. This can help pinpoint if a specific plugin is causing the conflict.

3. Debugging:

• Enable WordPress debugging by setting WP_DEBUG to true in your wp-config.php file. This might provide more detailed error messages. Be sure to monitor the debug.log file in the wp-content directory.
• Since the error points to a specific line in class-wp-hook.php, examining the surrounding code and understanding the context might give clues. However, modifications should not be made directly in WordPress core files.

4. PHP Version:

• You’re using PHP 8.2.12. Ensure that all your themes and plugins are compatible with this PHP version. Incompatibilities can often lead to unexpected behaviors.

5. Review Custom Code:

• If you have added any custom code snippets (in your theme’s functions.php file, a site-specific plugin, or through a code snippets plugin), review them to ensure they are correctly written. Pay special attention to add_action and add_filter calls.

6. Consult Theme and Plugin Support:

• Since the issue could be related to a specific theme or plugin, consider reaching out to the support forums for your theme and plugins. They might be aware of the issue or similar reports from other users.

7. Server and Hosting Check:

• Consult with your hosting provider to see if there have been any recent changes in the hosting environment that might affect your WordPress installation.

8.Restore Backup:

• If you have a recent backup from before the issue started occurring, consider restoring it. This can help determine if the issue is with the site content or configuration.

It’s advisable to debug in a staging environment rather than on your live site. This prevents any potential disruptions to your visitors and allows you to troubleshoot more freely.

Since you’ve already tried deactivating all plugins and clearing the cache, here are a few additional steps you can take to troubleshoot and hopefully resolve this problem:

1. Theme Conflict Check:

• Sometimes, a theme can cause unexpected issues. Temporarily switch to a default WordPress theme (like Twenty Twenty-One) and see if the problem persists. If the issue stops, the problem might be with your current theme.

2. Database Inspection:

• There could be a problem with your WordPress database, particularly with the tables that store menu settings. You can use a plugin like WP-Optimize to check and repair your database. However, make sure to back up your database before doing any operations.

3. User Role and Capability Issues:

• Ensure that your user account has the appropriate roles and capabilities. Sometimes, user permissions can get corrupted or altered.

4. Check for JavaScript Errors:

• Use your browser’s developer tools (usually accessible by pressing F12) to check for JavaScript errors in the console. A JavaScript issue can interfere with how changes are saved in the WordPress admin area.

5. Server-Side Restrictions:

• Some hosting environments have restrictions or security settings that might interfere with certain WordPress features. Check with your hosting provider if they have any such settings that could be causing this issue.

6. WordPress Core Files:

• Re-upload the core WordPress files. This can be done by downloading a fresh copy of WordPress from www.ads-software.com and then using FTP to re-upload the wp-includes and wp-admin folders. Be careful not to overwrite your wp-content folder or wp-config.php file.

7. PHP Version and Configuration:

• Check if your PHP version is compatible with your WordPress version. Also, review the PHP configuration settings (like max_execution_time, memory_limit, etc.) to ensure they meet WordPress requirements.

8. Check Error Logs:

• Look into your server’s error logs and the WordPress debug log (if enabled) for any relevant error messages. These logs can provide clues about what’s going wrong.

9. WordPress REST API:

• If your site relies on the WordPress REST API (as many modern themes and plugins do), ensure that it’s working correctly. Sometimes, security plugins or server configurations can block REST API requests.

10. Manual Menu Creation:

• As a last resort, try creating a new menu manually and assigning it to the desired locations. This can help if there’s an issue with the existing menu data.

If none of these steps resolve the issue, it might be helpful to reach out to your theme’s support team. Remember to always back up your site before making any changes or updates, so you can easily restore it if something goes wrong.

It sounds like your WordPress site experienced a security breach. The creation of an unauthorized admin user and the installation of an unrecognized plugin are clear indicators of this. You’ve taken some good immediate steps by deleting the unauthorized user, removing the unknown plugin, and changing your password. Enabling two-factor authentication (2FA) is also a great move for enhancing security. Here are some additional steps and considerations to ensure your site’s security:

1. Scan Your Website:

• Conduct a full scan of your website using Wordfence or another trusted security plugin. This will help identify any hidden malware or files that the attacker might have left behind.

2. Check User Accounts:

• Review all user accounts to ensure no other unauthorized accounts have been created. Pay special attention to accounts with administrative privileges.

3. Update Everything:

• Ensure that all your WordPress core files, themes, and plugins are up to date. Outdated software is a common entry point for attackers.

4. Review and Strengthen Passwords:

• Ensure that all user accounts, especially administrators, have strong, unique passwords. Consider using a password manager to generate and store secure passwords.

5. Audit Plugins and Themes:

• Remove any unused plugins and themes. Sometimes attackers exploit vulnerabilities in inactive themes or plugins.

5. Check File Integrity:

• Verify the integrity of your WordPress core files. You can do this by using tools like Wordfence or manually comparing your files with the original files from the WordPress repository.

6. Examine Recent Changes:

• If you have audit logging enabled, review the logs to see if there were any other changes made by the unauthorized user.

7. Hosting Environment Security:

• Check with your hosting provider to ensure there are no security issues on their end. Some providers offer additional security measures or scans.

8. Change Security Keys:

• Update your WordPress security keys. This will log out all users and is an effective measure if you suspect session hijacking.

9. Backup Your Site:

• If you don’t have recent backups, now is a good time to create one. However, ensure that you’re not backing up any compromised files.

10. Consider a Security Expert:

• If you’re unsure about any of these steps or if you want a professional to ensure your site is clean, consider hiring a WordPress security expert.

11. Monitor Your Site:

• After cleaning up, monitor your site closely for any unusual activity. Keep an eye on user accounts, file modifications, and unexpected changes.

It’s also worth noting that security breaches can sometimes occur due to factors outside of WordPress, such as compromised FTP credentials, an infected computer used to access the site, or a vulnerability in another application running on the same server. Best of luck and stay safe!

The error message “no working transports found” in WordPress typically indicates an issue with the server configuration, particularly related to how PHP is set up to handle outgoing network requests. Since you’re running WordPress on a Windows Server 2022 with IIS, here are some steps you can take to troubleshoot and resolve this issue.

Remember, making changes to server configurations and PHP settings can affect your entire website, so it’s advisable to back up your site and configuration files before making any changes.

1. Check PHP Extensions:

• Ensure that the necessary PHP extensions for network operations are enabled. Specifically, check for php_curl and php_openssl extensions. You can do this by creating a PHP file with <?php phpinfo(); ?> and accessing it through the browser. This will show you all the enabled extensions and PHP configuration settings.

2. Update PHP:

• If your PHP version is outdated, consider updating it to the latest version. Newer versions of PHP have better performance and security improvements.

3. Configure PHP.ini:

• Open your php.ini file and look for the extension=php_curl.dll and extension=php_openssl.dll lines. Make sure these lines are uncommented (i.e., not preceded by a semicolon). If they are missing, you need to add them.
• After making changes to php.ini, remember to restart IIS to apply these changes.

4. Check Firewall Settings:

• Ensure that your server’s firewall is not blocking outgoing HTTP/HTTPS requests. Sometimes, server-level firewalls or network policies can restrict internet access for applications.

5. IIS Configuration:

• Verify that IIS is properly configured for handling PHP scripts. This includes ensuring that the PHP handler is set up correctly.

6. Test Network Connectivity:

• Test the server’s network connectivity to external URLs using tools like curl or PowerShell cmdlets. This can help determine if the issue is with PHP or with the server’s network configuration.

7. WordPress HTTP API:

• WordPress uses its own HTTP API for outgoing requests. A plugin or theme might be interfering with it. Try disabling all plugins and switching to a default theme (like Twenty Twenty-One) to see if the issue persists.

8. Server Logs:

• Check the server logs for any additional error messages that might provide more context about the issue.

9. Seek Assistance:

• If you’re not comfortable making these changes, or if the issue persists, consider seeking assistance from a server administrator or a professional with experience in managing Windows servers and IIS.

10. Contact Hosting Provider:

• If your server is managed by a hosting provider, reach out to their support team for assistance. They might have insights specific to their configuration or environment that could help resolve the issue.

It sounds like you’re dealing with a challenging issue. Slow backend performance in WordPress can be caused by a variety of factors, and it can sometimes be difficult to pinpoint the exact cause. Since you’ve already tried disabling plugins and themes and optimizing the database, let’s consider some other potential causes and solutions:

1. Server and Hosting Environment:

• Server Resources: Ensure that your server has adequate resources (CPU, RAM) to handle the load, especially since you’re running a multilingual site with a significant number of articles.
• PHP Version: Check if you’re using the latest PHP version. Newer versions of PHP are generally faster and more efficient.
• Database Server: Sometimes the database server (like MySQL) can be a bottleneck. Check its performance and configuration.

2. WordPress Configuration:

• Object Caching: Implement object caching if you haven’t already. Tools like Redis or Memcached can significantly improve backend performance.
• Transient API: Check if transients are being used efficiently. A large number of expired transients can slow down the database.

3. Detailed Profiling:

• Query Monitor: You mentioned using Query Monitor but not finding it helpful. It might be worth revisiting this tool. Look specifically for long-running queries, hooks that take a long time to execute, or any external calls that are made during backend operations.
• New Relic or Similar Tools: These can provide a more detailed insight into what’s happening on your server and can help identify slow functions, database queries, and external calls.

4. WordPress Heartbeat API:

• The Heartbeat API can cause high CPU usage. You might want to control the frequency of the Heartbeat API or disable it on certain pages.

5. File System Operations:

• Sometimes, slow file system operations can be a culprit. Check if there are any backup plugins or log file operations that are running in the background.

6. External Calls:

• Check if your site makes external API calls during backend operations, which can significantly slow down response times.

7. Error Logs:

• Review the WordPress and server error logs for any warnings or errors that might indicate underlying issues.

8. Compare Configurations:

• Since you mentioned that a similar site on the same server is running fine, compare the configurations of both sites meticulously. There might be subtle differences in wp-config.php settings, .htaccess rules, or even in the server configuration.

9. User Sessions and Transients:

• Investigate how user sessions and transients are handled. A large number of sessions or transients can slow down the site.

10. Content and Database Structure:

• Analyze if the structure of your posts, custom post types, or taxonomies is causing inefficiencies, especially since you have a large number of articles.

11. Network Issues:

• Sometimes the issue might be related to network latency between your location and the server, or between the server and external services it communicates with.

12. Testing in a Staging Environment:

• Consider setting up a staging environment where you can replicate the issue and experiment without affecting the live site.

Performance optimization can often be a process of trial and error. It’s important to make one change at a time and measure its impact before moving on to the next. This approach helps in identifying what exactly improves the performance.

When the PDF contains images and figures, it is valuable to include a short, concise description as alt text. Deque U has some good documentation on this:

https://dequeuniversity.com/rules/axe/pdf/2.0/text-alternative-figure
https://www.deque.com/blog/pdf-accessibility/

Hi @haggis2022. This may be a plugin or theme conflict. I suggest that you disable all plugins, and switch to the default Twenty Twenty One theme. If the problem goes away, enable them one by one to identify the source of the problem.

If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to disable all plugins and change the theme for you, while you’re still logged in, without affecting normal visitors to your site.

Best regards.

Hi @tylerw23. WooCommerce does not have a support phone number, but you can submit a support request via the contact form on their support page: https://woocommerce.com/contact-us/. I expect that a Happiness Engineer will respond quickly.

Hi @joshuagrice!

This seems to be an issue with the Gravity Forms plugin on your site. I recommend that you post your question in that plugin’s support forum, so that their developers and support community can assist you:
https://www.ads-software.com/support/plugin/gravity-forms-custom-post-types/

Best regards.

Несколько различных плагинов позволяют совершать покупки или общаться через Whatsapp.

Посмотреть многие из них можно здесь:
https://www.ads-software.com/plugins/search/whatsapp/
(переведено с помощью Google Translate)

Here is one additional article that may be of help: https://elementor.com/blog/monday-masterclass-staging-to-live-site/

Hello @kazmpire. I suggest that you try the steps described in this article:
https://elementor.com/help/changes-dont-appear-online/.

Hello @zeusdx! These two articles may be of help to you:

How to Tweak the Performance of your LAMP Stack VPS or Dedicated Server

13 Slow WordPress Dashboard Remedies For a Faster Admin Panel

Привет @vas14. Есть много плагинов, которые могут вызвать это. Я предлагаю проверить, не использует ли ваш сайт подключаемый модуль, который может вызвать это.

С наилучшими пожеланиями.

(переведено с помощью Google Translate)

You might also find some relevant support here: https://divi.help/threads/mobile-menu-and-logo-keep-on-disappearing.2596/