tom coady
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Twenty Twenty-Five] Tag fails to filter postsHopefully the image shows how the page is currently structured, if not I can share the underlying code.
Forum: WordPress Mobile App
In reply to: 403 XMLRPC errorThank you for the detailed explanation and for confirming that my site’s Jetpack connection is currently functioning as usual. I really appreciate the clarity on how the mobile apps are transitioning to the REST API while still relying on XML-RPC for certain critical functions, such as authentication and publishing as this explains some of my unexpected experiences!
Your point about XML-RPC being implemented differently in Jetpack—using token-based signatures rather than traditional username/password authentication—helps contextualize its continued support. I understand that, for now, allowing XML-RPC POST requests is key to ensuring stability while the REST-based flows mature.
I’ll keep an eye on the setup and monitor for any intermittent issues. Should anything arise, I’ll be sure to reach out. Thanks also for sharing the documentation link—I’ll review it to better understand Jetpack’s specific use of XML-RPC.
I appreciate your thorough support and the ongoing work to improve the platform. Looking forward to the continued evolution of the REST API integration.
Forum: WordPress Mobile App
In reply to: 403 XMLRPC errorOK thanks for your detailed analysis which is useful as I have started to see errors again after restarting the app using REST and the errors persist albeit much more intermittently.
My understanding is that enabling XML-RPC is a security risk because it’s an outdated protocol with vulnerabilities that are exploited for brute force attacks, DDoS amplification, and server compromise, and it should be disabled in favour of alternatives like the REST API, so I look forward to the time when the app doesn’t need the legacy protocol.
Forum: WordPress Mobile App
In reply to: 403 XMLRPC errorFinally mystery solved! It was a security setting in plesk, but I was thrown off by the continued working in iphone and intermittent on ipad suggesting xmlrpc isn’t always necessary? In any case it would be great if this call could be made without fear, but I’m sure that has been discussed many time already! I see you have commented on that too, so it would be great to know if there are plans to update the app to use REST instead!
Forum: WordPress Mobile App
In reply to: 403 XMLRPC errorThanks @fierevere but as you can see the authentication was already disabled, enabling it makes no difference when installing the app, iPhone app continues to work whereas iPad requests auth every time I create a new post and often gets stuck after gaining permission so I have to kill the app and restart it. Luckily it remembers and draft AND the permission gained so I wonder if it isn’t an iPad specific issue?
Forum: WordPress Mobile App
In reply to: 403 XMLRPC errorI noticed I hadn’t chosen the skip option, and since this screen shot disabled authentication and enabled 2FA.
It’s happening again in coadycode.co.uk even after enabling dev mode in CF – is it possible I used my allowance of failed logins and need to wait 24h?
@erania-pinnera thanks you so much for so accurately pinpointing the underlying issue! Putting CF into dev mode resolved it instantly!
Apologies for the delayed feedback – I was watching but missed your first message.
- Form submitted
- Using chrome incognito to verify ownership: An error occurred: The necessary verification token could not be found on your site. This may be related to your site using a page caching plugin. Please flush your home page cache and then try again.
Forum: Plugins
In reply to: [Google for WooCommerce] Activation slows réponse timesThank you for your message and your interest in the issue I was facing. I’m happy to provide more details on how I identified the root cause.
I noticed that the issue seemed to originate from a specific plugin that had been recently updated. To confirm this, I set up a test environment and replicated the scenario with and without the plugin update. This isolated the plugin as the source of the problem.
Fortunately the root cause is more difficult to reproduce as it’s about the way WHM distributes the load between cPanel which recommends a maximum of one per domain.
Thank you for your support and your kind wishes. I hope you have a great day too!
Best regards,
Tom
Forum: Plugins
In reply to: [Google for WooCommerce] Activation slows réponse timesThanks for your reply Zubair. Fortunately I suspect that the root cause for this reduced performance is on my Krystal server so you can close this request for now and I will reopen in case I find the issue resurfaces independently of restricted resources.
Forum: Plugins
In reply to: [Google for WooCommerce] Activation slows réponse timesThank you for sharing this information. Let’s address each point:
1. WooCommerce Performance:It’s good that you’ve tried disabling the plugin to test performance. The errors you’re seeing related to WhichBrowser\Analyser\Header\Useragent are deprecation notices, which don’t directly affect performance but indicate that the code is using outdated PHP practices. These should be addressed by the plugin developers in future updates.
To further investigate WooCommerce performance:
• Use a profiling tool like Query Monitor or New Relic to identify specific slow queries or processes.
• Check if you have unnecessary WooCommerce extensions active.
• Ensure your hosting environment is optimized for WooCommerce (proper caching, PHP version, etc.).
2. Customize-tawk-to Widget Plugin Issue:I’m glad you found and fixed that critical issue. Your solution of using memcached with an expiry time is an excellent approach. It’s unfortunate that the plugin developer hasn’t addressed this problem. Here are some suggestions:
• Consider forking the plugin and maintaining your own version with the fix.
• Share your fix on the plugin’s support forum or GitHub repository (if available) to help other users.
• Look for alternative plugins that offer similar functionality but with better maintenance.
For future reference, always be cautious with plugins that store data for each visitor, as they can quickly bloat the database.Forum: Themes and Templates
In reply to: [Twenty Twenty-Four] Cannot add new templateSolution found / problem solved from buggy plugin:
wp plugin deactivate ultimate-markdown
Referenced also at https://wphive.com/plugins/ultimate-markdown/
OK I finally resolved by editing the global restriction options page:
Restriction Method – None
I’m a bit disappointed it took me so long!
Hello,
I’m following up on my previous support request. Despite your assistance, I’m still experiencing issues:
Cache/Data Problem:
- Ticked “Remove Data on Uninstall”
- Uninstalled and reinstalled the plugin
- Page restrictions still not updating
- Cache cleared, but problem persists
Code Implementation Issue:
- Implemented provided code
- Result: Unusual text above page header
- Had to restore database to previous state
- Code appears commented out and inactive
- Code includes functions for:
- Managing user roles
- Removing specific capabilities
- Updating roles
- Removing um_instructor role from users
User Management:
- Only one key master user (my account)
- Unable to delete this account
- Limits ability to troubleshoot user issues
Current Status:
- Site requires login for all page views
- Effectively locked to outside world
Questions:
- How can I resolve the caching issue affecting page restrictions?
- What’s causing the code to appear inactive, and how can I properly implement it?
- Is there a way to safely manage user roles without compromising security?
- Can you suggest a method to allow partial site access while maintaining security?
I appreciate your continued support in resolving these issues.
- This reply was modified 1 year, 7 months ago by tom coady.
