Pial
Forum Replies Created
-
Hello again
Hope you are doing well.
About your issue, We still haven’t heard back from you. So, I am assuming your issue has been resolved. I am resolving this topic.
Have a nice day!
Thank you for sharing the WordPress version you’re using.
I’ve investigated the issue on our end using the latest WordPress version (6.7.1) & PHP 8.3, but I couldn’t replicate the deprecated notice. For your reference, here’s a screen recording of our testing process: View Recording.
Could you please provide additional details or specific steps to reproduce the issue? This would help us identify the root cause and address it more effectively.
Additionally, I’d like to highlight that the Simple 301 Redirects plugin has a limited update schedule, with most updates focusing on critical improvements and security. To access the latest and most up-to-date features, we recommend migrating to BetterLinks. It’s an advanced URL management tool that allows you to manage, track, and optimize your links effortlessly. Migration is seamless, and it ensures you can take full advantage of modern capabilities.
To migrate your links please follow this steps : https://d.pr/v/i3K44UBest regards,
PialHi @markhowellsmead ,
Thank you for reaching out and reporting this issue.
Could you please share your system information, including the PHP & WordPress version you are using? Additionally, if possible, provide some steps to replicate this error. This will help us forward the details to our development team, and we will prioritize addressing the issue based on its severity.
Please note that Simple 301 Redirects follows a limited update schedule, focusing primarily on security and critical improvements.
In the meantime, I recommend exploring BetterLinks—our advanced URL management tool. It offers robust features to shorten, track, and manage links seamlessly. Plus, if you have a substantial number of existing links, you can easily migrate them to BetterLinks without any hassle.You can find comprehensive documentation here to help you get started.
Feel free to reach out if you have any further questions!
Best regards,
PialHey @bijoy001
Just checking in! Were you able to gather the requested details, such as screenshots or console logs? This information will help us investigate and resolve the issue more effectively.
Let us know how we can assist further!”Hey @saguya
Just checking in to see how things are going! Were you able to test the plugin with your workflow? Let us know if you have any feedback or need assistance—we’re here to help!”Hello @bijoy001
Thank you for bringing this to our attention. To help us better understand and resolve the issue, could you please provide the following:- A screenshot / screencast of the error popup that appears when trying to save the widget settings.
- Any relevant browser console logs.
For Windows: PressF12orCtrl + Shift + Iand navigate to the “Console” tab.
For Mac: PressCommand + Option + Iand navigate to the “Console” tab
These details will allow us to troubleshoot the problem more effectively. Let us know if you need assistance capturing this information!
Thanks!
PialHey @saguya
That’s fantastic to hear! 🎉 We’re so glad you were able to activate the plugin. It sounds like you have an incredible volume of content—BetterLinks is designed to handle even the most demanding workflows, so we’re excited for you to give it a try!If you have any questions, need assistance, or simply want to share your experience, we’re here and ready to help. Happy linking! 🚀
We’re sorry for the inconvenience you faced.
The good news is that with BetterLinks v2.2.1, we’ve resolved this issue, along with making several improvements and fixing minor bugs.
Please update to the latest version and let us know if you experience any further issues.
Thank you for your patience!Thanks for the update
Really appreciate your support and understandingDear @amirhmoradi
Following up on our previous response regarding SPYC dependency usage in BetterLinks, we wanted to ensure that all your concerns have been forwarded to our Dev team
As mentioned earlier, SPYC is solely utilized in the Device Detector module when tracking is disabled and short links are clicked, with no impact on frontend performance. However, we are committed to further optimizing the module in upcoming updates.
If you’ve experienced any specific performance issues or have test cases demonstrating an impact caused by BetterLinks, we’d greatly appreciate it if you could share those details. Our team remains ready to investigate and resolve any legitimate concerns promptly.
Looking forward to your feedback!
Best regards,
PialHello @matke1984
Thanks for confirming the fix for the archive page & Thank you for your patience. We have forwarded your feedback to our development team for further analysis. After reviewing the situation, we will get back to you with an update. We appreciate your understanding and are working diligently to resolve the issue as soon as possible.Hi @flatword
Thank you for the update! That is indeed unusual, but it’s great to hear that your JavaScript is working now, even after deactivating and deleting BetterLinks.
It’s possible that the issue was related to cached files or a temporary conflict that resolved itself after clearing the cache and removing the plugin. Sometimes, scripts or dependencies can linger in cache, causing inconsistencies until they’re fully cleared.
I understand your cautious optimism—it’s good to monitor the behavior for a bit to ensure it remains stable. If the issue arises again or if anything seems off, feel free to reach out, and I’ll be happy to assist further.
Fingers crossed it stays resolved!
Best regards,
PialHi @flatword
The issue occurs because WordPress doesn’t automatically load jQuery unless explicitly enqueued. BetterLinks likely enqueues it as part of its functionality, which is why your code works when the plugin is active but breaks when it’s deactivated. Additionally,
wp_enqueue_scriptis a PHP function and cannot be directly used in WPCode’s JavaScript snippets.To resolve this, you need to enqueue both jQuery and your custom script using WordPress’s standard
wp_enqueue_scriptfunction. Here’s how to do it: Step 1: Add a PHP Snippet in WPCodeSwitch to a PHP Snippet in WPCode and use the following code:
add_action('wp_enqueue_scripts', function () { // Enqueue WordPress's built-in jQuery wp_enqueue_script('jquery'); // Enqueue your custom script wp_enqueue_script( 'custom-script', // Unique handle for your script get_template_directory_uri() . '/path-to-your-script.js', // Replace with your script's file path array('jquery'), // Declare jQuery as a dependency null, // Optional version number true // Load in the footer ); });Step 2: Replace the Script Path
Update
/path-to-your-script.jswith the actual path to your custom script. For example:get_template_directory_uri() . '/js/my-custom-script.js'Why This Works
wp_enqueue_script: This function registers and loads JavaScript files.array('jquery'): Ensures jQuery is loaded before your custom script.true(in footer): Ensures the script loads at the bottom of the page for better performance.
Additional Notes
You can learn more about the
wp_enqueue_scriptfunction here in the WordPress Developer Reference.Best regards,
PialHello @flatword
Thanks for the Video, Yes now I understand exactly what’s the issue.
We will include a fix for this in future. In the meantime you can just Close the Notice and it will be removed entirely like this : https://d.pr/i/DPQlJp
Hope it helps
Let me know how it goes