WordPress.org

Support Everything WordPress

Welcome to the official blog for the WordPress Support team.

Need help with a WordPress issue? You can find help with your WordPress problem by posting in the support forums or asking on the #wordpress IRC channel.

Want to get involved?

Answering a question in the support forums or on IRC is one of the easiest ways to get started. Everyone knows the answer to something!

We have a detailed handbook to help contributors learn how to work with the forums and IRC.

Weekly Meetings

As well as discussing support issues here on the blog, we use Slack for group communication.

Our weekly team meeting is on Thursdays at 16:00 UTC in #forums on Slack.

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Jan Dembowski 1:23 am on September 3, 2015 Permalink |  

    Agenda for the Thursday September 3rd meetup 

    A little last minute but here are the items on the agenda for the next meetup:

    Please feel to bring up any item you’d like discussed in the comments or at the meetup itself.

     
  • Jan Dembowski 12:00 pm on August 28, 2015 Permalink |
    Tags:   

    Support Meetup Summary for August 27th 

    Items discussed at yesterday’s Support Team Meetup:

    The WordPress 2015 survey

    If you haven’t already done so, please take a few minutes and fill out the WordPress 2015 survey. The information is anonymous and feedback is good.

    The WordPress 4.4 Wishlist

    Scott Taylor is the 4.4 release lead and has a post in make/core titled “WordPress 4.4: What’s on your wishlist?” This is a great chance to post what you’d like to see in WordPress 4.4 and as Scott wrote, it can be anything: big or small.

    Don’t redo The Clone Wars or get into The Fork Awakens

    Please don’t engage in ‘ZOMG! They stole my plugin!’ fights on the forums. Send the developer to “plugins[at]wordpress.org” and the plugins team will handle it. Public shaming of that sort of thing is ugly, unkind, and not to be encouraged.

    If a moderator encounters a topic like that then please leave the note and close the topic.

    Any big WordPress 4.3 problems?

    This is a repeat item but there does not seem to be any major issues with 4.3. Except for a missing checkbox when creating new users the topic have been mild.

    There has been a number of repeat topics about 4.3 but those have mostly been the result of aggressive caching somewhere.

    WordCamp US Contributor Day and the Community Summit

    As more information is available on the WordCamp US site it will be shared in the #forums channel and communicated on make/support too. There is a lot of interest in the support team meeting in person and providing support live and together. Contributor days are fun and it’s a great chance to meet in person the people you’ve been collaborating with.

    View the meetup transcript in the Slack archives. (A Slack account is required)

     
  • Jan Dembowski 10:11 am on August 26, 2015 Permalink |  

    Agenda for Thursday August 27th meetup 

    Items for this weeks meetup.

    For any other items please reply in the comments or feel free to bring it up in the Slack #forums channel.

     
  • Jan Dembowski 11:28 pm on August 20, 2015 Permalink |
    Tags:   

    Support Meetup Summary for August 20th 

    Items discussed at today’s Support Team Meetup:

    WordPress 4.3 was released

    Congratulations to the core team, it really looks like another great release. 😉

    On Tuesday the most recent version was dropped. In the support forums the OMGWTFBBQ post was updated with just a few new items. It’s really been a smooth upgrade and the volume of problem topics was not different from when some minor version number releases.

    Keep in mind that the splitting of existing taxonomy terms means that users who talk about downgrading back to 4.2.x is not safe. The predefined replies have this added now (thanks @macmanx) in case it comes up.

    Unless you have a backup that you can restore from, downgrading is a dangerous process, which is why backing up before upgrading is strongly recommended both in the upgrade instructions and automatic upgrade interface.

    It would be better to solve your current problem. Would you please describe what is wrong?

    Some hosts have apparently upgraded there customers to 4.3 and except for some “I wish I’d made a child theme” topics it’s been good.

    2015 Community Summit Dates

    The topic of contributor day came up for WordCamp US and the 2015 Community Summit post was discussed. Give it a read and vote in the poll there regarding the  dates for if the summit occurs before or after WCUS.

    View today’s meetup transcript in the Slack archives. (A Slack account is required)

     
  • Jan Dembowski 1:44 am on August 19, 2015 Permalink |  

    Agenda for August 20th meetup 

    Items for the next meetup:

    Any items for this week’s meetup please feel free to comment here or bring it up at the meetup.

     
  • Jan Dembowski 10:59 am on August 12, 2015 Permalink |  

    Agenda for the August 13th Support Team meetup 

    No real agenda this week except for preparing for 4.3 to drop next week on the targeted date of Tuesday August 18th.

     
  • Jan Dembowski 11:48 am on August 7, 2015 Permalink |
    Tags:   

    Support Meetup Summary for August 6th 

    Items discussed at yesterday’s Support Team meetup:

    The draft OMGWTFBBQ post is up

    It still needs editing but the old template still works. With 4.3 there have been updates to TinyMCE and the version numbers may cause some confusion. The built-in TinyMCE component is now at 4.2.3. As with server side caching, this may contribute to visual editor support topics.

    I should be able to update the What’s New part this weekend. If anyone has any suggestion then comment on that post or ping the #forums channel on Slack.

    Test the WordPress 4.3 release candidate

    Test, test and test some more. You can use the beta tester plugin and switch to the nightlies, it’s a great way to kick the tires. If you do test then please use caution. I use the nightlies on own installation but I don’t do anything exotic with any plugins. Consider installing on a test site first.

    View today’s meetup transcript in the Slack archives. (A Slack account is required)

     
  • Jan Dembowski 2:37 pm on August 3, 2015 Permalink |  

    Agenda for the August 6th Support Team meetup 

    Items for discussion at Thursday’s meetup:

    • The draft OMGWTFBBQ post for 4.3 is up. The server side caching parts need fleshing out and I’m brain stuck for adding the new 4.3 features and changes.
    • Test, test and test again the current 4.3-RC1 release. The scheduled release date is still targeted for August 18th and that’s not a lot of time left.

    For any items to add please comment and it will be discussed too.

     
  • Jan Dembowski 12:08 pm on August 3, 2015 Permalink |  

    Draft 4.3 OMGWTFBBQ post 

    This will get updated frequently before thr 4.3 release and it’s very 4.2’ish copy pasta right now.

    READ THIS FIRST – WordPress 4.3 Master List

    First introductory post:

    Hooray! 4.3-NAME is here! But OMGWTFBBQ!? WordPress 4.3 broke everything?

    Don’t Panic!

    Before you go any further, make sure you’ve updated your plugins and themes to the latest versions, clear your browser’s cache and cookie and re-log into your WordPress dashboard.

    Still having problems? Okay, read on!

    This thread contains the known issues with plugins and themes found in 4.3. Please read this WHOLE topic and come back and check again later, as it will be updated.

    Remember to be calm, be patient and be respectful. Volunteers are out here to try and help you, but we need your help too. All of the normal forum rules still apply. Remember, you are just as important as everyone else.

    If your post doesn’t show up right away, please be patient. With the higher than normal post volume, more posts get flagged as spam by our auto-spam tool. We’re working hard to keep the queue clear, but making multiple posts slows us down, as we have to go back and check if you already posted. Post once.

    • Do use proper capitalization in post titles and body. Punctuate your sentence properly and humanely, it helps us read.
    • Do use descriptive subject lines. “All permalinks broken since 4.2” is much better than “Augh! Help ASAP! This version is terrible!”
    • Do describe the problem clearly. Explain what you’re seeing, include error messages and link to screenshots if needed. Linking to your site, if the problem is on the front-end, also helps.
    • Do be patient. We know it sucks to be down, but posting multiple times doesn’t get you help any faster.
    • Do make your own topic unless you are using the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme and configurations as the original poster. You may find it weird, but it will be easier for us to help you specifically if you have your own topic.
    • Do mark your topic as resolved when it’s fixed so we know not to come looking there anymore.
    • Do remember you’re not alone.

    Also keep in mind that not liking the direction of WordPress’s design does not a bug make. If you don’t like a feature, please don’t make a series of posts complaining about it. Look and see if someone already did, and post there, or consider joining the process earlier on (like in Beta or even test via SVN). What you’re seeing today is the result of thousands of hours of work and testing, and unless something is outright broken, it’s highly unlikely to be changed.

    Again, before you post:

    Make sure you’ve read the entire Master List post – and the New Features in 4.3 Codex Articlehttps://codex.wordpress.org/Version_4.3

    Go to your own install’s about page – `http://example.com/wp-admin/about.php` – to see what’s new.

    And then make sure you’ve tried…

    • Flushing any caching plugins you might be running, as well as server and/or browser caches. Not just your browser, but any op cache or content network cache as well such as Cloudflare. That will solve many weird Javascript issues.
    • If your host provider has a “Purge Varnish” option or if you can ask your provider to flush memcache on your server.
    • Deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin (read “How to deactivate all plugins when you can’t log in to wp-admin” if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to `mu-plugins-old`
    • Switching to the Twenty Fifteen theme to rule out any theme-specific problems. If you can’t log in to change themes, you can remove the theme folders via FTP so the only one is `twentyfifteen`. That will force your site to use it.
    • Manually upgrading. When all else fails, download a fresh copy of the latest.zip file of 4.3 (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server (NOTE: do not delete the `wp-content` directory or your `wp-config.php` file) Read the Manual Update directions first.

    Next post:

    CORE CHANGES

    What’s New:

    • Site Icons are available for you to add to your site for phone applications, icon in the browser tab, etc. via the Customizer.
    • Edit your menus in the Customizer. The previous menu editing options are remaining in place.
    • Better passwords. The system will default to generating strong passwords. These can be replaces manually.
    • Quick preview of links. Hovering over a link in the visual editor will pop-up a box with the link and permit you to edit it there.

    What’s Changed:

    • Editor changes
      • Formatting shortcuts
      • Updated version of TinyMCE
    • Comments on pages defaults to off
    • Your shortcodes may be broken (that was in 4.2.3, didn’t you notice?) so please update your plugins and themes.
    • Admin backend table changes

    Next post:

    NOT A BUG

    My layout is all weird on the Dashboard

    Flush your cache. If you’re using server caches, or a plugin, flush them too, especially Memcached/APC stuff. They can be sticky. This includes Cloudflare and Pagespeed and Varnish. Anything that caches.

    I’ve upgraded and the posts are not styled correctly

    Check if you are running `mod_pagespeed` and if you are try disabling it to see if your posts render correctly.

    Next post as needed (probably will be needed):

    KNOWN ISSUES

    [List plugins and themes we know are broken]

    Next post as needed (this one was deleted out of the 4.2 post):

    REPORTED OOPSIES

    [List bugs in 4.3 – Hopefully not needed!]

    Please comment below with suggested changes and missing details. Or if you are an editor here, feel free to make updates as necessary. This post has revisions so there’s not much possible harm in editing. 😉

     
    • Ipstenu (Mika Epstein) 4:12 pm on August 3, 2015 Permalink | Log in to Reply

      Added to “Not a Bug”: This includes Cloudflare and Pagespeed and Varnish. Anything that caches.

    • Jan Dembowski 5:16 pm on August 17, 2015 Permalink | Log in to Reply

      Updated What’s new and what’s changed.

    • Stephen Edgar 10:53 am on August 18, 2015 Permalink | Log in to Reply

      The “Manually upgrading” section mentions deleting `wp-admin`/`wp-includes`, should adding a mention to *not* delete `wp-content` along side that, you know just to be complete and we can say:

      “It’s not like we didn’t tell you you to NOT delete your wp-content folder”

  • Jan Dembowski 10:37 pm on July 31, 2015 Permalink |  

    Draft Instantbird for Windows instructions 

    These were put together from working with @zoonini, @jcastaneda and @abletec. They’re a draft instructions and hiding the IRC server status messages aren’t dealt with in these instructions yet.

    Step 1. Create a Slack account for yourself in the WordPress team.

    Step 2. Obtain your IRC gateway information from the Slack page.

    Your IRC Gateway account information will look something like this using my username and obscured password.

    Host: wordpress.irc.slack.com
    User: jan_dembowski
    Pass: wordpress.XxXxXxXxXxXxXXxXXxxX

    Step 3. Install Instantbird for Windows.

    Once installed the application will run for the first time and setup an account for you. The IRC protocol is not displayed by default, scroll to the bottom and select “Show all protocols”.

    Step 4. Select the IRC protocol and proceed. You will be asked for a “Username:” and “Server:”

    Enter your username from the Slack Gateway page. In my case that would be “jan_dembowski”

    For the servername use “wordpress.irc.slack.com”

    Step 5. You will be prompted for a password. Leave that field blank, in a later step the real username and password will be enters via the configuration editor.

    Step 6. You will be prompted for a Local Alias. This is for display purposes only and can be left blank.

    Step 7. Uncheck the box labeled “Connect this account automatically.” It won’t work at this step and can be enabled later.

    Step 8. Close the Accounts window. This is to get it out of the way.

    Step 9. Open the Options dialog box. In Windows this can be accomplished via the key board shortcuts alt-T and then the O key.

    Step 10. Under the Advanced tab go to the Config Editor. From that tab you can use the alt-E keyboard shortcut. A dialog box will appear and you’ll need to bypass the warning by clicking “I’ll be careful, I promise!”

    Step 11. Here’s where it gets tricky. You need to add two new entries into the configuration editor. This can be accomplished by right clicking inside the now opened configuration editor and then use the keyboard shortcut W then S. This will create a new string value.

    In that new dialog box paste in this preference name.

    messenger.account.account1.options.username

    And hit enter.

    The next part will be to enter the string value. This is the Slack IRC Gateway user field. With me as an example I used “jan_dembowski”. This is the real user ID field for the Slack IRC gateway. The one previously entered in at install time isn’t actually used.

    Now for the gateway password preference. Once again right click inside the configuration, use the keyboard shortcut W then S and create this new string value.

    messenger.account.account1.options.serverPassword

    And in the next dialog box enter your account password from the IRC Slack gateway page. For my example I’ll use “wordpress.XxXxXxXxXxXxXXxXXxxX”

    Step 12. Exit the Configuration Editor and click OK on the Options box.

    Step 13. Connect to Slack. Using the keyboard shortbut alt-T then A then O. This will tell Instantbird to connect to the Slack IRC gateway for the first time,

    If all the steps were done correctly the following will happen: your Instantbird will lock up and become unresponsive. Once it calms down you should be in the #announcements Slack channel.

    There will be messages like this littered in the client.

    6:26:46 PM – Channel mode -v set by macmanx.

    6:31:22 PM – Channel mode -v set by johnparkinson.

    Those are very distracting but I think they can be hidden with a CSS plugin for Instantbird. More on that later.

     
    • Jackie McBride 11:00 pm on July 31, 2015 Permalink | Log in to Reply

      Very nice, Jan. Might I assist w/a few minor proofreading things?

      Also, it would appear those strings assume that no account has been set up previously on Instantbird. I’m not entirely sure of the technicalities, but even when I deleted a previous account & entered those strings, my Instantbird installation blew up fairly spectacularly, & I was forced to nuke all profiles & reinstall. So even though I promised I’d be careful, I guess I wasn’t careful enough lol.

      If Instantbird does need to be uninstalled, then that should be done via the ‘Programs and Features’ aplet in control panel. After the program has been uninstalled, and preferably after a reboot has been initiated, the relevant profile can be deleted. It’s found under users\username\AppData\local\instantbird. Instantbird can then be reinstalled, & those strings should work just fine.

      Might it be worth putting notes to that effect in a ‘Troubleshooting’ section at the end of the document?

      • Jan Dembowski 11:33 pm on July 31, 2015 Permalink | Log in to Reply

        That’s a great idea and proofread away. 😉

        Were you able to get rid of the server messages on the Instantbird client?

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel