beaubhavik

@mary12c Getting same error when installed and use this plugin. what’s issue there ?

So, need to debug step by step.

@waseemsannib

Error code 521 indicates that Cloudflare is unable to establish a connection to your origin web server. This can occur for several reasons, particularly after changing your DNS settings to connect your website to Cloudflare. Here’s a breakdown of potential causes and solutions: Possible Causes of Error Code 521

• Web Server Issues: Your origin server might be down or not responding. Ensure that your web server is running properly and check its error logs for any issues.
• Firewall or Security Settings: Your server’s firewall may be blocking Cloudflare’s IP addresses. Make sure that your firewall settings allow connections from Cloudflare IPs and are not set to block or rate limit them.
• Incorrect DNS Configuration: If your DNS settings are not correctly configured, Cloudflare may not be able to reach your server. Double-check that the nameservers and DNS records are set up correctly in your hosting provider’s control panel.
• SSL Configuration: If you are using HTTPS, ensure that your server is configured to accept connections on port 443. If necessary, consider switching to “Flexible” SSL in Cloudflare’s SSL/TLS settings, which can help if your origin server does not support SSL.

Steps to Resolve the Issue

1. Check Server Status: Verify that your web server is operational. You can do this by accessing it directly via its IP address.
2. Review Firewall Settings: Ensure that your firewall is not blocking Cloudflare’s IP addresses. You may need to whitelist these IPs.
3. DNS Propagation: As you mentioned, DNS changes can take up to 24 hours to propagate fully. If you have just made the changes, it may be worth waiting to see if the issue resolves itself.
4. Contact Hosting Provider: If you are unable to diagnose the problem, reach out to your hosting provider for assistance. They can check if there are any issues on their end that might be causing the connection failure.
5. Test with Development Mode: If you have access to Cloudflare, try enabling Development Mode temporarily. This can sometimes bypass caching and allow you to see if the site is accessible without Cloudflare’s interference.

Conclusion

In summary, the error code 521 is likely due to connectivity issues between Cloudflare and your origin server, which could stem from server downtime, firewall settings, or DNS misconfigurations. It is advisable to check your server’s status, review your firewall settings, and possibly wait for DNS propagation. If the issue persists, contacting your hosting provider for further assistance is recommended.

Citations:
[1] https://www.ads-software.com/support/topic/error-code-521/
[2] https://community.cloudflare.com/t/error-code-521/418286
[3] https://community.cloudflare.com/t/community-tip-fixing-error-521-web-server-is-down/42461
[4] https://community.cloudflare.com/t/getting-http-521-randomly-on-my-website-with-the-proxy-option/627172

@shameemreza Okay.

@sacconi

Yes, placing all your custom taxonomies code in a custom plugin instead of functions.php can be a good idea.

Benefits of Using a Custom Plugin :

Portability:

• If you switch themes, the custom taxonomies will still be available since they are part of the plugin, not tied to a specific theme.

Organization:

• It keeps your theme files clean and focused on design, while the plugin handles functionality.

Modularity:

• You can easily disable, update, or reuse the plugin across multiple sites without affecting the theme.

Priority in Execution:

• Plugins generally load before the theme functions, which ensures that your taxonomies are registered early in the WordPress load order. This is important if other parts of your code or other plugins depend on these taxonomies being available.
  
• Execution Order Consideration:
  WordPress loads plugins first, then the theme’s functions.php, and finally executes the core functionalities. By placing the taxonomies in a plugin, you ensure they are registered before the theme’s core logic is executed.

• This reply was modified 7 months ago by beaubhavik.

@sacconi

• Check the wp-config.php File: // define('WPCACHEHOME', '/path/to/wp-content/plugins/wp-super-cache/');
• Reinstall/Update the Caching Plugin

@chauthong Yes, that issue occurred within the settings or preferences section.

Hi @chauthong

It might be a configuration issue based on your setup. I checked on my end, and I can see those options available.

You can refer to the following screenshots for comparison:

• Screenshot 1
• Screenshot 2
• Screenshot 3
• Screenshot 4
• Screenshot 5

Let me know if this helps!

Hello @sacconi

Thanks for sharing the details. Since your edit post page opens quickly but the custom taxonomies are taking longer to load, it might be helpful to investigate the specific queries being executed. I recommend using the Query Monitor plugin, which can help you debug and analyze the database queries related to your custom taxonomies.

You can download it here: Query Monitor. Make sure to check and debug thoroughly to identify any bottlenecks.

Hello, @doublezed2

Issue:
When clicking on “Configure Items” (screenshot: https://prnt.sc/_BP4Pta31VP8), the terms are displayed, but the left submenu (similar to “Attributes”) is not activated.

Screenshot Reference:
https://prnt.sc/So8zf9T4NLs-

Hello @chauthong ,

To resolve the issue of categories and other widgets not showing on mobile devices when using the block editor in WordPress, you can try the following steps:

1. Check User Profile Settings: Ensure that the option to disable the visual editor is not selected in your user profile. Go to?Users > Profile?and make sure the “Disable the visual editor when writing” option is unchecked.
2. Clear Browser Cache: Sometimes, cached data can cause display issues. Clear your mobile browser’s cache and cookies, then reload the block editor.
3. Disable Plugins: Conflicts with plugins can lead to issues in the block editor. Temporarily deactivate all plugins to see if the categories and widgets appear. If they do, reactivate the plugins one by one to identify the culprit.
4. Update WordPress and Theme: Ensure that you are using the latest version of WordPress and that your theme is updated. Outdated software can cause compatibility issues.
5. Use a Different Browser: Try accessing the block editor using a different mobile browser to rule out browser-specific issues.
6. Check Theme Compatibility: Some themes may not fully support the block editor. Switch to a default WordPress theme (like Twenty Twenty-Three) to see if the problem persists.
7. Inspect REST API Issues: If you have access to developer tools, check for any errors in the REST API requests. If you notice issues, you may need to adjust your server configuration (especially if using Nginx) to ensure proper handling of REST API requests.
8. Contact Support: If none of the above solutions work, consider reaching out to WordPress support forums for more tailored assistance.

By following these steps, you should be able to troubleshoot and potentially resolve the issue of missing categories and widgets in the block editor on mobile devices.

Additionally :
you’re unable to access important post settings like categories, tags, and featured images when editing on mobile, even though these work fine in the classic editor and on desktop. Let’s try to troubleshoot this problem.

Here are a few things you can try:

1. Update WordPress: Make sure your WordPress installation is up to date. Sometimes, older versions can have compatibility issues with the block editor on mobile devices.
2. Check for plugin conflicts: Temporarily deactivate all plugins and see if the issue persists. If it resolves, reactivate plugins one by one to identify which one might be causing the conflict.
3. Switch to a default theme: Try switching to a default WordPress theme like Twenty Twenty-One to rule out any theme-related issues.
4. Clear browser cache and cookies: On your mobile device, clear the browser cache and cookies, then try accessing the editor again.
5. Try a different mobile browser: If you’re using the built-in browser on your mobile device, try using a different browser like Chrome or Firefox to see if the issue persists.
6. Check screen options: In the block editor, look for a “More tools & options” menu (usually represented by three vertical dots). There might be an option to show/hide these panels.
7. Use the WordPress mobile app: Consider using the official WordPress mobile app for editing posts, which might provide a better mobile editing experience.

If none of these steps resolve the issue, it could be a bug in the current version of WordPress or the Gutenberg editor. In that case, you might want to:

1. Report the issue on the WordPress support forums or Gutenberg GitHub repository.
2. As a temporary workaround, you could continue using the classic editor on mobile devices until the issue is resolved.

Hello @fisamex

1. Increase Memory Limit: define('WP_MEMORY_LIMIT', '256M');
2. Permissions Check: ncorrect file permissions can cause issues with uploading and displaying images. Ensure that directories like wp-content, wp-includes, and wp-admin have the correct permissions, typically set to 755 for directories and 644 for files.
3. Debugging Mode: Enable debugging in WordPress to see if any specific errors are being reported. You can do this by adding the following lines to your wp-config.php file
   define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Hello @sacconi ,

To speed up the opening of custom taxonomies on your edit post pages, you can consider the following optimizations:

1. Reduce the Number of Taxonomies: If possible, minimize the number of custom taxonomies loaded at one time.
2. Optimize Database Queries: Ensure that your taxonomy queries are efficient. Using a caching plugin or optimizing database queries can significantly reduce load times.
3. Asynchronous Loading: Implement asynchronous loading for your taxonomy boxes so they don’t block the loading of other elements on the page.
4. Use AJAX: Load the content of taxonomy boxes via AJAX only when they are accessed. This will decrease the initial load time of your edit pages.

@bludotpi
by second point of 2. Interference from SMTP plugins if have.

Hi Carolin,

Thank you for your response.

The issue I’m facing is not just about the terms being displayed. The main problem is that after clicking on “Configure terms” for any attribute, the configured terms submenu is not appearing under the Products menu. This makes it confusing for a regular admin user because they can’t see the terms listed in the left menu under Products, beside the Attributes. This absence creates a navigation issue and makes it hard to know which screen they are currently on or to manage the terms efficiently.