#363 closed enhancement (fixed)
Extra form field for site's url while creating a new thread on support forum
Reported by: | bravokeyl | Owned by: | SergeyBiryukov |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Support Forums | Keywords: | |
Cc: |
Description
Many times on support forums theme/plugin users ask questions related to css side or something that needs to check their site to see error/problem they are facing,but they don't give site's url in the thread , volunteers have to ask for their site url..
It will be great if we have a field for site's url while posting new thread.
Change History (25)
#3
@
10 years ago
- Cc macmanx@… added
- Keywords needs-patch added
- Priority changed from lowest to normal
Yes! Please, yes! It takes time away from the user's solution when we need to ask for a URL showing the problem.
#4
@
9 years ago
- Keywords needs-patch removed
Removing 'needs-patch' from components that are not open sourced yet, to help focus on tickets that actually need a patch.
This ticket was mentioned in Slack in #meta by sergey. View the logs.
7 years ago
#6
follow-up:
↓ 14
@
7 years ago
Are there plans to implement this? Are there plans to allow patches to be submitted? This issue is a no-brainer. I don't know how many times I've had to say exactly this phrase to users:
https://wordpress.org/support/topic/give-donation-button-is-stuck/
This ticket was mentioned in Slack in #meta by webdevmattcrom. View the logs.
7 years ago
This ticket was mentioned in Slack in #forums by webdevmattcrom. View the logs.
7 years ago
#9
@
7 years ago
Just to chime in again and make my case for why this issue is so important. Every single support ticket that comes in has a source. Naturally, some requests involve only the wp-admin screens, but in order for Support to provide support we have to either replicate the problem perfectly (which could require 100's of words from the user), or at least see the problem live in order to have an informed opinion. It's baffling, but many users just simply don't consider this fact at all, so they describe their problem with a sentence or two, and leave us in the dark without a link.
PLEASE. This is important.
This ticket was mentioned in Slack in #forums by clorith. View the logs.
7 years ago
#11
@
7 years ago
The URL field obviously won't be a required field, so you are possibly going to need to ask the users for this regardless (just to set expectations right)
This should be a field that's hidden until a user signs in, to avoid the potential outcries we have today of "Google sees my site".
#12
@
7 years ago
Good points @Clorith -- we can also make sure that when its output on the screen that the link has a nofollow as well.
#13
@
7 years ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from new to closed
In 5757:
#14
in reply to:
↑ 6
@
7 years ago
- Keywords 2nd-opinion removed
Replying to webdevmattcrom:
Are there plans to allow patches to be submitted?
Just to clarify, the forums are open-sourced already (both the plugin and the theme), so we do accept patches :)
#17
@
7 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
as we don't want reviews to have links, can that field be suppressed on a new review?
#22
follow-up:
↓ 24
@
7 years ago
as discussed with other ru. support team members, it would be nice to
- Have an indication in RSS feed that support url is present for topic
(Yes. RSS is not dead yet)
- Have at least indication for not logged in users that support url is present
( In case someone logged out, or using paranoid privacy extensions in their browser)
Indication can be url itself (if made open for everyone) or just an icon/whatever with message "url available only for logged in users"
Just searched for this ... because I was going to suggest it otherwise. Great idea ... and potential very useful and a time efficiency for supporting plugins (and themes?)