WordPress.org

Support Everything WordPress

Recent Updates Page 2 Toggle Comment Threads | Keyboard Shortcuts

  • 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?

  • Ipstenu (Mika Epstein) 5:42 pm on July 30, 2015 Permalink |
    Tags:   

    Support Team Meetup Summary for July 23rd 

    Items discussed at today’s Support Team meetup:

    WordPress 4.3 RC1

    People are testing, that’s good. More people should be testing.

    Also, don’t panic, Site Icon controls are now available in the Customizer only.

    If you find a non-alpha/beta post in the Alpha/Beta forums, please feel free to remove it by any means necessary. Let’s keep that place clean.

    OMGWTFBBQ draft post

    Items to add:

    • Cache notice (flush ’em all)
    • Shortcodes may be broken (though they were broken in 4.2.3 so…)
    • Site Icon controls are now available in the Customizer

    Codex Documentation

    Codex for 4.3 needs love – Don’t worry about the function lists, those will be added after the doc-ref is auto-updated.

    Sockpuppets

    If you find a sock puppet thread/review, delete it and block the *not-developer* user. Then email plugins@wordpress.org with all of the details. If @ipstenu is online and active, you can ping her, but the email is more reliable. Especially on weekends and off-peak hours.

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

     
  • Ipstenu (Mika Epstein) 8:34 pm on July 29, 2015 Permalink |
    Tags: agenda,   

    Agenda for July 30th Support Meetup 

    Items for discussion at tomorrow’s meetup:

    We can cull from https://make.wordpress.org/core/tag/dev-notes+4-3/ to pick out the biggest issues.

    Writing the Version 4.3 post is … painful. I tried it for 4.2 and I’ll see if I can give it a shot again but more hands welcome. Use https://codex.wordpress.org/Version_4.2 as an example.

     
  • James Huff 11:16 pm on July 23, 2015 Permalink |
    Tags:   

    Support Team Meetup Summary for July 23rd 

    Items discussed at today’s Support Team meetup:

    WordPress 4.2.3 and Shortcodes

    WordPress 4.2.3’s security fixes had to make alterations to the Shortcode API, which broke some shortcode plugins. More details on that are available in this writeup.

    WordPress 4.3 Beta 4

    People are testing, that’s good. More people should be testing.

    Also, don’t panic, Site Icon controls are now available in the Customizer only.

    If you find a non-alpha/beta post in the Alpha/Beta forums, please feel free to remove it by any means necessary. Let’s keep that place clean.

    Chrome and the HTTPS oops of 2015

    Chrome is currently forcing some non-HTTPS sites to HTTPS, most notably for us are WordPress login pages, sometimes causing 404s, certificate errors, or other fun things. The issue is being looked at and present in stable and beta Chrome release channels, so be on the lookout for reports of blogs broken in Chrome only. (Update: Fixed as of Chrome version 44.0.2403.107.)

    Helphub

    Helphub hasn’t gone anywhere yet, it’s still on the todo list. The first goal is to get organized, then probably dev work, then finally porting over good Codex articles and re-writing bad ones.

    Gamification

    We’re generally not in favor of gamification, it leads to poor quality replies, but we are in favor of some automated way to earn the Support Team badge.

    OMGWTFBBQ draft post

    Nothing to add yet, keep testing.

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

     
  • James Huff 12:29 am on July 23, 2015 Permalink |  

    Agenda for July 23rd Support Meetup 

    Items for discussion at tomorrow’s meetup:

    • WordPress 4.3 beta 4 testing continues. Find the bugs, save the world.
    • Draft OMGWTFBBQ post for 4.3. Anything new to add?

    For any other items please comment here or bring it up at tomorrow’s meetup.

    Meetups are not limited to the agenda, we will have plenty of extra time. Please bring with things you want to discuss, and if you want to absolutely make sure we discuss them, leave a comment here. :)

    The Support Meetup is 1600 UTC every Thursday in the Slack #forums channel.

     
    • Tim Nash 11:59 am on July 23, 2015 Permalink | Log in to Reply

      4.2.3 is out, critical security update, expect the usual I installed it and my site broek, how do I go back style questions.

  • Jan Dembowski 12:01 pm on July 17, 2015 Permalink |
    Tags:   

    Support Team meetup summary for July 16th 

    Items discussed at yesterday’s Support Team meetup:

    WordPress 4.3 beta 3

    Please test, test, and test some more. While it’s not always good idea to use beta versions on a production site, if you can kick the tires and identify any issues that would be appreciated. Problems can be reported in trac or the alpha/beta sub-forum.

    The planned release date for 4.3 is August 18th and that’s not a lot of time.

    OMGWTFBBQ draft post

    With each release there’s usually a master troubleshooting list. It’s almost always a straight copy and paste from the last one and made sticky. That will still be the case, but the part about clearing all the caches will be bumped up. With the changes to the editor there’s expected to be more than usual problems for cached javascript code.

    Deleting reviews for plugins/themes

    A few weeks ago there was a misunderstanding with users leaving reviews and the end result was that some reviews were deleted. That specific case has been dealt with and deleting those reviews is no longer required.

    If a moderator sees something occurring with a plugin’s reviews then yes, gather information and report it to the plugins team. For themes ping the #forums Slack channel and the TRT can be notified.

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

     
  • Jan Dembowski 10:25 am on July 15, 2015 Permalink |  

    Agenda for July 16th support meetup 

    Items for discussion at tomorrows meetup:

    • WordPress 4.3 beta 2 testing continues (you are testing, right?)
    • Draft OMGWTFBBQ post for 4.3

    For any other items please comment here or bring it up at tomorrow’s meetup.

     
  • Jan Dembowski 7:23 pm on July 9, 2015 Permalink |
    Tags:   

    Support Team meetup summary for July 9th 

    Item’s discussed at today’s Support Team meetup:

    WordPress 4.3 beta 2! Test all the things!

    Beta 2 has dropped, please test and report any issues in the Alpha/Beta sub-forum. When someone posts to that sub-forum and a trac ticket is created then post the link to the trac ticket and mark the topic as “resolved”. Do not close the topic. For topics that should not be in the Alpha/Beta sub-forum then please move them where they need to go.

    One change to be extra aware of is that there are changes to how the editor works in 4.3. Some users will have problems after the upgrade and for those users the solution will be to clear all of the caches that may be holding onto old versions of scripts. Not only the user’s browser cache but server side caches as well.

    Otto wrote a good comment to that post and when the OMGWTFBBQ draft is posted then that will be high up on the troubleshooting steps.

    If you are a forum moderator please keep an eye on the spam queue

    It’s been well maintained these last few days, but please check on the spam queue from time to time. The other night I checked and there was a post in the queue for 11 hours. If it’s spam then delete it. If it’s not then release the post. Easy. 😉

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

     
  • Jan Dembowski 11:36 am on July 7, 2015 Permalink |  

    Agenda for July 9th support meetup 

    While I was unable to attend last week’s meetup, it was still held and there was an item that’s being repeated this week.

    • Please test WordPress 4.3 beta1 (this item)
    • Moderators please review the spam queue from time to time (new item)

    For any other topics to discuss please comment here or feel free to bring it up on Thursday. The Support Meetup is 1600 UTC every Thursday in the Slack #forums channel.

     
  • Jan Dembowski 12:20 pm on June 26, 2015 Permalink |
    Tags:   

    Support Team meetup summary for June 25th 

    Participation in the meetup was low but that wasn’t unexpected. There wasn’t a posted agenda, people are on vacation or are timezone challenged due to WCEU.

    There was one item that I’d like to post and possibly make someone blush. Jackie (@abletec) you may want to stop reading this. I don’t intend to put you on the spot (honest!) but here I go.

    Jackie used Instantbird to participated in the #forums Slack channel

    I was jumping for joy. 😉

    Jackie had been collaborating with @zoonini to get the IRC gateway working for her. @jcastaneda and I had been poking at Instantbird for Windows and Jose shared what I was missing to get it connected. But Kathryn and Jackie together sorted it out. Jackie was able to join and participate in the support meetup.

    The IRC gateway to Slack isn’t perfect. The gateway pipes in server status messages a lot and that’s distracting. But it’s useable and outside of the native Slack client becoming a11y friendly this is an option.

    Accessibility is important. It’s more important than any old browser version compatibility. There’s a whole segment of WordPress users who want to get involved. Here’s the proof from Jackie that I was thrilled to read.

    But for the 1st time I really feel a part of the WP community.

    That’s it right there and that’s the whole point of getting a11y issues stamped out. The Slack IRC gateway is a step in that direction.

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

     
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