Conversation
supportHello, does not seem to work on a test site with little extensions activated. The page I need help with: [ log in to see the link]
Well, I preferred to switch to another plugin. It’s a kind problematic to open an admin account 🙂
I completely understand. Can you do me a favor and try using “code” tags instead of “pre”? And see if that works. This reply was modified 5 years, 9 months ago by treeflips . This reply was modified 5 years, 9 months ago by treeflips .
OK, it works with <code> . But as I use a plugin to colorize code, I have to use pre.
Understood. We are chatting internally to decide how to support pre tags. 🙂
@treeflips I have archived your admin ask. 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 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.
Well, I preferred to switch to another plugin. It’s a kind problematic to open an admin account 🙂
I completely understand. Can you do me a favor and try using “code” tags instead of “pre”? And see if that works. This reply was modified 5 years, 9 months ago by treeflips . This reply was modified 5 years, 9 months ago by treeflips .
OK, it works with <code> . But as I use a plugin to colorize code, I have to use pre.
Understood. We are chatting internally to decide how to support pre tags. 🙂
@treeflips I have archived your admin ask. 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 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.