Hi!
Unfortunately I’ve not been able to replicate this problem on our end so far. I have a few questions to help me better understand what’s going on:
- Are only the settings in the “Trigger” section affected, or other settings like “Action” and “Condition” as well?
- When you change the trigger for rule 2, does it immediately populate into rule 1, or only on save?
- Do you have the latest version of the plugin (1.2.2)?
Thank you!
hello, the only thing that has a problem for me is the trigger. action and condition work fine. I am on the latest version of the plugin, yes when i change trigger for rule 2 it will immediately go to rule 1 here is a video if it helps.
https://jumpshare.com/s/XzDhMbnVbPpSqZZDTUQy
Hi!
Thanks a ton for the video – it helped a lot.
For the next test, could you please keep the browser console open for the entire reproduction of the issue and capture any errors as soon as they appear? Here is what to check:
- Open the browser console before doing anything (F12 -> Console). Then reproduce the issue step by step. If any errors appear at any moment, grab a screenshot right away, before moving to the next step or saving the rule.
- If everything above looks fine, please copy the HTML of the new rule right after you add it (before saving) and send it to us. Seeing the id attributes on those trigger checkboxes will help confirm whether the script is rewriting them correctly.
You can also message us directly via http://help.berrypress.com/. In the private chat we can look at your setup in more detail and, if needed, arrange secure temporary access to debug this on your site.
Thanks again, and let us know how it goes!
hello, i am having trouble reproducing the bug. It seems like an uncommon occurrence, last time this happened no error messages appear in the console. i’ll come back here if i see it happen again. For now i’m going to mark this as resolved.
Thanks for the update. If the issue appears again, please let us know and we will be happy to take another look 🙂
Anna, BerryPress
In the private chat we can look at your setup in more detail and, if needed, arrange secure temporary access to debug this on your site.
@kurowskanna
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their phpinfo(); output.
- Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
