Javascript Error
-
On the shop page of ballandeanestate.com when I try to edit this page I get the following javascript error: Uncaught TypeError: _.findWhere is not a function and I am not able to edit the page, but if I disable the commerce7 plugin then I am able to edit the page. This only happens in the builders (Oxygen) back end.
-
@lfirth Please do not share login to any site. If you do and it is found out, and it always is, then Michael could have his plugin removed from this site. It’s that serious.
@michaelbourne 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.
This includes a staging site as well
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 vistors).
- 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.
Hi @jdembowski
Understood. I searched and found the guidelines for @kmcmillan and anyone else interested: https://developer.wordpress.org/plugins/wordpress-org/using-the-forums/
@jdembowski can you and I continue this on Slack? I have some follow-ups that don’t need to be discussed here.
@lfirth this sounds like a JS conflict between Commerce7 and Oxygen. If no errors are logged in PHP (as per Jan’s instructions above), then I will know to look there. I’ll research some solutions and get back to you.
Thanks
can you and I continue this on Slack? I have some follow-ups that don’t need to be discussed here.
Please don’t. If you do, you could be banned. That would be seen as trying to use Slack as a way to get around a restriction. Also that’s not what the WordPress Slack is for.
I know it’s not easy and I know you mean well but please use the reply I wrote which many moderators helped to craft for ideas.
To future readers, my question about Slack was for Jan and I to continue talking about the repo guidelines, which we did. That was obviously lost in translation here with the previous reply. No restrictions were violated.
@lfirth The latest update 1.4.8 solves the problem with Commerce7’s JavaScript interfering with Oxygen’s builder.
@michaelbourne Thank you for looking at that for me.
The topic ‘Javascript Error’ is closed to new replies.