{"id":21331,"date":"2021-03-14T15:00:32","date_gmt":"2021-03-14T14:00:32","guid":{"rendered":"https:\/\/qodeinteractive.com\/magazine\/?p=21331"},"modified":"2021-03-12T13:35:16","modified_gmt":"2021-03-12T12:35:16","slug":"how-to-ask-for-wordpress-support","status":"publish","type":"post","link":"https:\/\/qodeinteractive.com\/magazine\/how-to-ask-for-wordpress-support\/","title":{"rendered":"How to Ask for WordPress Support the Right Way"},"content":{"rendered":"<div class=\"wpb-content-wrapper\"><p>[vc_row][vc_column][vc_column_text]Despite WordPress being a very user-friendly platform, questions and potential issues arise every day. This is true for all WordPress users, from those who are just starting to those who are very experienced. Some of the issues users encounter can be resolved simply by more practice with the WordPress platform or by searching online.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]However, sooner or later, an issue will come up that you won\u2019t be able to solve on your own, regardless of your investigation skills. To solve it, you will need to ask for WordPress support from developers, technicians, or the WordPress community. But, even the process of asking for support properly is a skill in itself, and one that plays an important role in solving the issue quickly and efficiently. Since this is not as easy as it may seem, we have created a guide on asking for WordPress support the right way. In the process, we will also cover where you could go for help and who to ask. Let us begin.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;80px&#8221;][vc_widget_sidebar sidebar_id=&#8221;new-top-picks-banner&#8221;][vc_empty_space height=&#8221;80px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h2 class=\"qodef-h4\">Where you should look for WordPress support<\/h2>\n<p>[\/vc_column_text][vc_column_text]There are a lot of places where you can find help regarding WordPress, either by asking for it or by simply going over the posts, forums, manuals, or other helpful content yourself. We will try to summarize them as best as possible in this section. But, given that there are a lot of WordPress-related resources available online, we are sure to miss some.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]As we established, there are a lot of forums and platforms where you can ask WordPress-related questions and get the answers you need. First of all, you should start with the official <a href=\"https:\/\/wordpress.org\/support\/forums\/\" target=\"_blank\" rel=\"noopener\">WordPress.org<\/a> and <a href=\"https:\/\/wordpress.com\/forums\/\" target=\"_blank\" rel=\"noopener\">WordPress.com<\/a> support forums. Besides them, all themes and plugins published on WordPress.org will have their separate forums that can be accessed after navigating to their official pages.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Other than the official WordPress forums, there are a lot of forums and platforms online that have parts dedicated to WordPress. Those include the <a href=\"https:\/\/www.reddit.com\/r\/Wordpress\/\" target=\"_blank\" rel=\"noopener\">WordPress subreddit<\/a>, <a href=\"https:\/\/www.quora.com\/\" target=\"_blank\" rel=\"noopener\">Quora<\/a>, <a href=\"https:\/\/stackoverflow.com\/\" target=\"_blank\" rel=\"noopener\">Stack Overflow<\/a>, and <a href=\"https:\/\/stackexchange.com\/\" target=\"_blank\" rel=\"noopener\">Stack Exchange<\/a>, for example. For the users who prefer reading documentation or want to widen their overall knowledge of WordPress, we advise reviewing the <a href=\"https:\/\/codex.wordpress.org\/Main_Page\" target=\"_blank\" rel=\"noopener\">Codex<\/a> and <a href=\"https:\/\/developer.wordpress.org\/\" target=\"_blank\" rel=\"noopener\">Developer\u2019s handbook<\/a>. And for users who are accustomed to learning visually, we recommend watching tutorials on <a href=\"https:\/\/wordpress.tv\/\" target=\"_blank\" rel=\"noopener\">WordPress.tv<\/a> or searching for tutorials on <a href=\"https:\/\/www.youtube.com\/\" target=\"_blank\" rel=\"noopener\">YouTube<\/a>.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Furthermore, since WordPress was initially designed as a blogging platform, there are a lot of blogs still available that cover various website-related topics intended for a wide range of readers. Therefore, in most cases, you only need to search online for a bit to find an appropriate article that covers the issue you are having or the topic you are interested in.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]We also suggest you consider some of the WordPress-related groups on social media platforms like <a href=\"https:\/\/www.facebook.com\/\" target=\"_blank\" rel=\"noopener\">Facebook<\/a> and <a href=\"https:\/\/www.linkedin.com\/\" target=\"_blank\" rel=\"noopener\">LinkedIn<\/a>.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Finally, if you are using a premium WordPress plugin or theme, you will receive premium support for a certain time, so you can ask for help from them, as well. They will have extensive documentation, knowledge bases, and FAQs that you should also review. In some cases, asking your hosting provider for help also could be integral in solving the issue.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;68px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h2 class=\"qodef-h4\">How to go about asking for WordPress support<\/h2>\n<p>[\/vc_column_text][vc_column_text]Now that you know a bit more about the ways and places where you can find information and help regarding WordPress, we can dive into the specifics of asking for help. We have condensed our advice into seven distinct, carefully constructed sections.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]In general, our advice applies whether you\u2019re asking for WordPress help in a forum or platform, or asking for support from plugin or theme authors. By following our suggestions, you will have the best chance of resolving your question or issue quickly and without stress. But, apart from reaching out for help, you should know that you are expected to perform some initial investigation like reading the plugin\u2019s FAQ section or some troubleshooting steps before asking for support. We will discuss this in one of the sections below. Without further ado, let us proceed.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;72px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h3 class=\"qodef-h5\">Create a subject title specific to your issue<\/h3>\n<p>[\/vc_column_text][vc_column_text]The first thing you should always consider when creating a support thread is to make sure that the title of the thread accurately depicts the issue while using the fewest words. This holds for all support requests that you\u2019ll be making in the places we\u2019ve mentioned.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]A carefully selected subject line can grab the attention of whoever is reading it while providing a glimpse into the issue you are having. In some cases, this can lead to a quick resolution of the support thread if the issue is familiar to the community. Meaning, it has a known solution, or it\u2019s one of the more frequently asked questions, or it\u2019s an often requested how-to, and so on.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]However, even in the cases that it doesn\u2019t lead to a quick resolution, a title that is well thought through can help clear any misunderstandings that might exist in the body of the support thread. Otherwise, any confusion could lead to the question not being answered properly. Therefore, <strong>make sure to always create subject titles that are specific and provide an idea of the issue you are having<\/strong> as it can significantly increase the chances that the issue is solved quickly.[\/vc_column_text][vc_empty_space height=&#8221;72px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h3 class=\"qodef-h5\">Be polite<\/h3>\n<p>[\/vc_column_text][vc_column_text]As our second piece of advice on how to ask for WordPress support, <strong>we suggest being polite and writing the whole support request in a well-mannered way<\/strong>. This includes not using insults, swear words, threats, or discrimination on any basis. By not adhering to this advice, your support request could easily lead to needless back-and-forths, arguing, and frustration. In extreme cases, you could even be denied assistance due to harassment. Instead, <strong>make sure to be courteous to all the people who are willing to help with your issue from the start. Then lay out all the details of your issue<\/strong> according to the guidelines we will discuss below.[\/vc_column_text][vc_empty_space height=&#8221;72px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h3 class=\"qodef-h5\">Describe your issue clearly<\/h3>\n<p>[\/vc_column_text][vc_column_text]Now that you know the tone you need to use to describe your issue, we\u2019ll look at precisely how you should explain it. <strong>Try to describe the issue as thoroughly as possible. Include the exact steps that you were doing that lead to the issue, as well as a screenshot where the issue is highlighted<\/strong>. Depending on the error, <strong>you could also create and include a video explaining the issue that appeared on your website<\/strong>. Make sure to include both the steps that lead to the issue and the issue itself on that video.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Furthermore,<strong> specify what you thought should happen but didn\u2019t<\/strong>, due to the issue. By clarifying this, you will avoid any misunderstandings among the technicians or the WordPress community that is trying to help you. This clarification could be helpful as you might simply be misunderstanding some WordPress, theme, or plugin feature, which will be, then, pointed out to you. Also, specifying this could remove any doubts as to what the issue is, in case the words you used were ambiguous.[\/vc_column_text][vc_empty_space height=&#8221;72px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h3 class=\"qodef-h5\">Provide the necessary information for troubleshooting<\/h3>\n<p>[\/vc_column_text][vc_column_text]After you describe your issue clearly, don\u2019t forget to <strong>provide the necessary information for the troubleshooting process<\/strong>. However, this information can be very sensitive. Therefore, <strong>you should carefully consider whether you should reveal it publicly, or use a private reply or other secure means of transmitting data<\/strong>. With that being said, let us discuss what that information is.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]The most important piece of information that you should <strong>include is the URL of the page where the issue is present<\/strong>. If you\u2019re contacting the support technicians of a premium plugin or theme, you should also <strong>include your login URL and a set of WordPress admin credentials<\/strong>, so that they could log in and investigate. This is the kind of information you\u2019ll want to share only privately with a trusted recipient. Additionally, in case your website has frontend protection, make sure to supply them with those credentials as well.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]However, if you don\u2019t feel comfortable with someone investigating the backend of your website, you can opt to send the page URL only, in case it\u2019s sufficient for troubleshooting the issue. And, if the page URL alone is not enough, you can consider <a href=\"https:\/\/qodeinteractive.com\/magazine\/how-to-setup-wordpress-staging-site\/\">making a staging website<\/a> as a copy of your original site. Then you can supply all the information for that website instead; namely, the page URL, login URL, and WordPress admin credentials.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]On the other hand,<strong> if you are working in localhost, you should mention that within the body of your support request<\/strong> and describe your issue in detail. Apart from screenshots and\/or video, in this case, you should also<strong> include which plugins and theme you are using, as well as their versions, including which WordPress version you are using currently<\/strong>. This will be very helpful to anyone trying to recreate your issue on their end in hopes of solving it.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Finally, if the current issue has broken your website, you should <strong>ask your hosting provider for the error log and send it within the body of the support request.<\/strong> Optionally, if you are contacting a trusted source, you should <strong>send your FTP credentials<\/strong> as well. That way the support technicians could investigate the files mentioned in the error log via FTP.[\/vc_column_text][vc_empty_space height=&#8221;72px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h3 class=\"qodef-h5\">Point out any troubleshooting steps you have done<\/h3>\n<p>[\/vc_column_text][vc_column_text]Several troubleshooting steps can be applied to a wide range of WordPress issues. Attempting some of them can help narrow down the cause of the issue or even solve it, sometimes. As such, if you are able, you should try to perform these initial troubleshooting steps before submitting a support request to speed up the resolution process. In that case, <strong>make sure to list the troubleshooting steps you have done and the results you got within the body of the support request<\/strong>. We will briefly mention what those potential troubleshooting steps are below.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]The first step includes checking for caching issues by <strong>clearing the browser and plugin cache<\/strong> when viewing the page where the problem is present. Moreover, doing this is good practice that you should use after each step we mention, as it will help to confirm the validity of your results.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Following that, you should <strong>test if your current issue is due to some of the plugins you are using or even your current theme<\/strong>. This is done by deactivating one plugin at a time from the list of your installed plugins. You can do this within the WordPress dashboard (the Plugins &gt; Installed Plugins section), if you have access to it, and review the issue afterward. Similarly, to test if your current theme is the culprit, <a href=\"https:\/\/qodeinteractive.com\/magazine\/how-to-install-wordpress-theme\/\">install and activate a default WordPress theme<\/a> instead of the one you were using up till now. Then test the status of the issue afterward.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Additionally, make sure to <strong>review your website across multiple browsers and on various devices<\/strong> to see whether the issue is only present on certain browsers or devices. Finally, try to <strong>temporarily remove any code<\/strong> (CSS, JS, or PHP) <strong>that you might have inserted into your website<\/strong> and check for the issue afterward. This is especially important to test if you have simply copied and pasted that code from somewhere, without modifying it in any way or being aware of what it does.[\/vc_column_text][vc_empty_space height=&#8221;72px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h3 class=\"qodef-h5\">Don\u2019t spam<\/h3>\n<p>[\/vc_column_text][vc_column_text]Even though this advice could apply to all sorts of WordPress support, it is most relevant to users that ask for help from plugin or theme authors using various means of communication. While any unfamiliar website issue can cause you to stress and worry, asking for support from the same source using different channels (various social media, email, phone, chat, and other means of communication) won\u2019t help solve the issue any faster. Especially if you\u2019ve submitted the initial support request at the same time. This can lead to you getting different advice if you describe the issue differently each time, and it can ultimately be considered rude and disrespectful.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]<strong>In most cases, the expected wait time for an answer on your issue(s) after submitting a support request is up to one workday<\/strong>, so being a bit patient is the best course of action.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Moreover, making follow-ups on the initial support request before the developer or support agent has replied is not advised. This is because some support platforms order their support requests based on the time of the last reply. Thus, with each subsequent follow-up you make to your support thread, you will be pushing the original support request down the queue. This can postpone resolving your issue even further and may lead to unnecessary frustration. Therefore, <strong>one simple follow-up via email or Twitter<\/strong>, for example, <strong>regarding the status of your existing support request when the wait time is near its end is more than sufficient<\/strong>. That way, you will avoid creating any mix-ups delaying the turnaround time on your ticket.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]However, <strong>if you have a lot of issues that are not related, we advise making several separate support requests for them instead of putting all the issues within a single thread<\/strong>. This will speed up the process of solving all your issues significantly. Each of your support requests will be examined by a different developer or support agent at the same time instead of having one person go through the whole list of issues one by one.[\/vc_column_text][vc_empty_space height=&#8221;72px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h3 class=\"qodef-h5\">Show gratitude after the issue has been solved<\/h3>\n<p>[\/vc_column_text][vc_column_text]<strong>After the issue has been solved, don\u2019t forget to thank all who have helped you resolve it.<\/strong> A simple thank you can go a long way, especially if you relied on the kindness of strangers on a forum. By acknowledging their work and thanking them for it, they will be more inclined to help you in the future and might assist you further than you expect.[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]Finally, after learning more about WordPress yourself, you should consider helping others to feel the same rewarding sense of satisfaction and contribute to the WordPress community.<br \/>\n[\/vc_column_text][vc_empty_space height=&#8221;68px&#8221;][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text]<\/p>\n<h2 class=\"qodef-h4\">Final Thoughts<\/h2>\n<p>[\/vc_column_text][vc_column_text]WordPress is an excellent platform, equally welcoming to all its users, from the most inexperienced to the most advanced. But, even in a perfect environment, issues are bound to happen. Some can be solved simply by searching online or combing through articles and forums, while others require you to ask for technical help. In this article, we talked about asking for WordPress support and all the advice you should follow to receive help quickly.<\/p>\n<p>[\/vc_column_text][vc_empty_space height=&#8221;28px&#8221;][vc_column_text]To summarize, you should try to be respectful, clearly explain your issue, provide enough data for the troubleshooting process, mention the steps you have already taken, and be thankful to everyone that spared their time to help you. Additionally, you should try to avoid spamming as it can be quite counterproductive. With that being said, we are sure that you already know most, or if not all the points we mentioned, since they are just common sense advice. Nevertheless, we hope that this article will prove to be helpful the next time you ask for WordPress support.<br \/>\n[\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>We&#8217;ve all been there &#8211; stuck with a problem and in dire need of WordPress support. Now, how to ask for support so that you get the help you need?<\/p>\n","protected":false},"author":11229,"featured_media":21643,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[77,4,13],"class_list":["post-21331","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-resources","tag-support","tag-tips","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/posts\/21331","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/users\/11229"}],"replies":[{"embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/comments?post=21331"}],"version-history":[{"count":0,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/posts\/21331\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/media\/21643"}],"wp:attachment":[{"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/media?parent=21331"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/categories?post=21331"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qodeinteractive.com\/magazine\/wp-json\/wp\/v2\/tags?post=21331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}