If you need support, go to the forums. If you want to help make Support awesome, stay here.
If your comment is for support, it will be deleted. If it looks like spam, it will be deleted. Sorry, but there’s no other way to keep up with things.
I made a ticket for a weird caching issue: http://core.trac.wordpress.org/ticket/26676
I think the ONLY other one that’s jumping out now is the plugins page is blank. If you’ve managed to solve that one (all I can see is ‘host fixed it!’), reply here. This is probably related to @andrea_r‘s comment: http://make.wordpress.org/support/2013/12/wherefore-the-wtfbbq-post/#comment-157012
ALso seeing issues with people unable to manage widgets. COuld be user error, dunno.
I made a conscious decision not to make one for 3.8. Not because I think the release was perfect, but because there wasn’t enough to make a post. There barely was last time. As long as we here are prepared.
http://make.wordpress.org/support/handbook/forum-moderator/stock-answers/ has the stock replies, so I think… for the most part we;re going to be alright 
So far 3.8 has been great. I haven’t seen anything blow up or gone awry.
It’s all good. 
There’s a thread or two about the 3.8 admin interface CSS but that seems to be going alright. That was expected since changing the look or styling always gets a small but vocal group of people who don’t like those changes.
Aside from that it’s been great.
“I don’t like MP6″ and “I don’t like TwentyFourteen” are not ‘bugs’ so they don’t really deserve to be made much of in this case. Same thing happened in 3.0 and 3.1 when we moved things around.
I actually went looking for this because we’re seeing a few tickets with plugin & widget issues. Like.. things disappearing. No I don’t have enough info yet.
MP6 turned itself off and … that was about it.
Oh and weird caching issues.
Hello. I often talk to people that are confused by the message that shows for plugins and themes that haven’t been updated within the past two years. They seem to ignore the fact, the message says the theme or plugin MAY have compatibility issues.
I suggest the word “may” be set as emphasized or even in bold letters:
This theme hasn’t been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
What is the confusion? I would say that that message is there specifically to tell them that they should probably look for a different plugin or theme. If an author can’t be bothered to even update the version compatibility in the readme.txt for a couple years, then the plugin isn’t one I would recommend using.
Also note that plugins and themes with this 2-year-mark on them do not show up in searches, except for exact name matches, so one would hope this issue doesn’t crop up a whole lot.
The plugin may actually work fine, but a plugin that is not well supported is not a good plugin to choose or recommend.
The confusion is a lot of users seem to think a plugin generally doesn’t work if it has this warning. If it were so, we could have them deleted right away.
I’m only saying the term “may have compatibility issues” is often read over. Yet we find plugins that do a particular job great since ages and there is no need to update or change stuff.
(Example: http://wordpress.org/plugins/simply-show-ids/ by sivel. Very simple plugin that just shows the ID’s of posts and pages in the back end lists. Certainly won’t harm if installed. May help beginners to spot ID’s easily.)
The key word there is “should.”
Perhaps they are confused because they are only getting the facts (“…hasn’t been updated in 2 years…”) and not getting the message it is trying to infer: they should probably look for a different one, as you noted.
Perhaps these users have not learned the hard way about plugin and theme compatibility so the facts have no context. “Hey, it’s free, it’s worth a shot!”
Perhaps they don’t understand that one criterion for being a good plugin is good support, and good support includes current compatibility checks.
Bold lettering may increase the read percentage but it does not provide context.
Hoping this issue doesn’t crop up is not a solution because (a) Google still includes them in search results, and (b) they are listed on a plugin author’s profile page.
More should be done:
1. Educate. Instead of a notice, make it a warning. “Use at your own risk.” Then explain why abandoned plugins are potential problems.
2. Train. By providing a link to search results for better alternatives (no cherry-picking, just the results they would get having searched themselves) you train end users to use your search before Google.
3. Qualify. Give the rating system a shelf life. 4.5 stars for WordPress 3.2 should not carry the same weight as 4.5 stars for WordPress 3.8. Two years is arbitrary; compatibility with WordPress 3.5 and up is not.
3. Be not afraid of ruffling the feathers of absent developers. Allow someone to function as a user advocate in order to recommend a better plugin.
We compile best practices because they prevent problems.
(a) Google still includes them in search results
That I can darned well fix.
That message is *supposed* to be scary. People are *supposed* to not use plugins with that message. If plugin authors cannot continue to update a readme.txt once every *2 years*, then the plugin isn’t reliable.
Plugins are about more than just code. If an author ceases to support a plugin, ceases to update a plugin, ceases to use their own plugins, then we should either remove them or find a way to get some other author to update them.
The message is a compromise solution. If I had my way, plugins not updated in over two years would be automatically removed from the listings entirely. No exceptions. Maybe that is a bit harsh, but it’s just my opinion. Two years is a *long* time to ignore a plugin completely.
As a plugin author, I would be interested in an option to delete or request deletion of obsolete plugins. They are not being updated for good reasons.
Email plugins AT wordpress.org and link to the plugin you want us to delete. We’ll do it.
Ipstenu: Done. Thanks for the tip.
I agree with @otto42 that, at the very least, the readme.txt needs to reflect the fact that the author has confirmed the plugin’s compatibility with the latest version of WordPress. There are some plugins that are, in effect, “evergreen”, meaning the code rarely, if ever, needs to be updated. However, that does not mean the readme.txt doesn’t need to be. If the author doesn’t keep that up-to-date, then as far as I’m concerned, the plugin has been abandoned, whether the code continues to function properly or not. I hope the warning message scares people away from using potentially abandoned plugins.
Great article about the benefits that active support forums/channels bring to on-line communities:
http://winthecustomer.com/community-forums-unsung-hero-social-support-infographic/
Originally shared by @fabianapsimoes.
Due to the Thanksgiving holiday in the United States the #wordpress-sfd meetup for November 28th will be unstructured but not canceled.
What that means is please meetup if you want but be aware that participation from the U.S. will be limited and possibly nonexistent.
I will review the IRC log from the meetup on Friday and will provide an update for the Support portion if there is any. If there are any support topics please feel free to discuss them and we can follow up next week.
Thanks for the update! Hope you have a very happy thanksgiving.
Thanks! Thanksgiving is always fun and I expect to eat lots. Friday I’ll be bouncing instead of walking.
During todays support and docs chat on IRC we introduced a few new faces on the access lists of the WordPress channels there to help moderate and control the behavior of the users, much like you would on the forums.
As IRC does not work with a bozo list like the forums do, we have a few alternatives available for use in such situations as outlined below. This means we can not mark users for moderation, nor preview what they are trying to say before it is said, it’s all live, and it’s all public.
We want to maintain as much transparency as we can, this is a public medium and we keep public logs of most actions (at the moment the logging devices can not log kick/ban messages), but at the same time protecting the one performing the action from any negative retaliations which may or may not occur after action is taken.
We have three (four) ways of dealing with users who are having a bad day beyond just speaking to them and informing them that their behavior is unacceptable/a bit too much and asking them to calm down or get some fresh air;
Muting (or “Quieting”) a user (/mode #channel +q Nickname) requires you already have the Operator status, or can be done through network services (/msg ChanServ quite #channel Nickname) but keeps the user in the channel, he is merely silenced and can not speak in public, this is also what hlin does automatically if someone spams.
A kick can be done either by being an Operator (/kick #channel Nickname ) or anonymously through the services of the network (/msg ChanServ kick #channel Nickname ). A kicked user is removed from the room temporarily, but may return at any point.
A ban, like a kick, can be done as an Operator (/mode #channel +b Nickname) or through network services (/msg ChanServ ban #channel Nickname ). Worth noting is that using services will also kick the user, if not you will have to manually kick the user after banning them. A ban will not by default expire unless you physically remove it.
Now that we are familiar with the ways one can deal with a user, a general guideline for when to use the various actions will most definitely be needed. This will be handy both for the users of the channel to know when a moderator should step in so they can be pinged, but also so the moderators know what action should be taken when to ensure a fair ruling.
Feedback will most definitely be required here to iron these out, but I’ve taken the liberty to provide the following suggestions to get the ball rolling;
There are many other situations of course, but these are the ones you’ll most likely meet, not only in spoken words, but also as nicknames or messages sent to the channel when leaving it (a part message).
There was also mention of a way to log (beyond IRC logs) offenders to keep tabs on what is going on as everyone might not be on at the same time etc. Thoughts on how this could be achieved in a fair manner are appreciated as we don’t want to make any public shame list at all, we only want to make IRC a welcoming place for anyone to drop by and learn a thing or two during their stay. Possibly a list restricted to moderators on g-docs or similar is an idea?
Another thing that might come up is how to deal with disputes if a user is banned and feels it was unjust. Is there a place we’d prefer them to take their appeal, and if so, where and how?
That means we need to decide on the level of transparency we wish to have, do we wish to have full transparency with users issuing the actions, or anonymize it through network services.
@sams suggested that for transparency when issuing a kick/ban we should state why in the channel after the ban since the logger does not pick up kicks/bans and only shows peoples reactions to them, would this be an acceptable approach and how would we deal with that if services are used to act?
Oh and before I forget, the fourth reasoning mentioned is only if a user should retaliate, this is much like a DDoS on a website, and extremely rare to occur, and even rarer to have any impact as most networks have security to prevent or mitigate such things. Should a disgruntled user retaliate with proxy bots or any other kind of bots that cause spam and disruptions, and it’s to such an extent that a moderator can not deal with it, drop by the kind people in the FreeNode support channel and mention that there’s a botnet and they’ll take care of it. Not that vital as it’s extremely unlikely to ever occur, but good to know just in case.
A closing thought, as it was mentioned that not everyone may be too familiar with the workings of IRC or remember commands and such, I did mention a few of the commands with quick defaults in the post, but is this something that you would prefer a more extensive outlining of made available in some form or other?
All right ladies and gentlemen, the floor is open
Just a quick note on the above -
You can’t kick or ban through chanserv on freenode.
You *can* quiet through chanserv . It’s not anonymous, as the target will always be told who set the quiet, but it can be considered less “noisy”, as no one has to op up to do it.
You can set an akick through chanserv (auto kick + ban) but only if you have +fr on the access list, and none of the current set of chanops has that.
So, in other words, most of the time the ops will need to op up to take action. ( /msg chanserv help op )
Also note that in most cases baning or quieting a nickname is sub-optimal, as it can be easily evaded. Try to quiet the host. ( /whois nick to see their full hostmask ) then /mode #wordpress +q *!*@hostpart.dot.com
freenode staff can assist with finding the right sort of quiet to set if you’re stuck – just /join #freenode if you need help there. (Hopefully no one will need it as quiets will be few and far between, anyway, but it’s good to see that there’s some more people on the access list now.)
Oh, wasn’t aware it didn’t do kick/ban, my bad on those then! Maybe an alternative for transparency then would be a way to go through hlin to remain anonymous?
I’m kind of okay with being known when/who I kick/ban, since we’re going to be warning some first.
A closing thought, as it was mentioned that not everyone may be too familiar with the workings of IRC or remember commands and such, I did mention a few of the commands with quick defaults in the post, but is this something that you would prefer a more extensive outlining of made available in some form or other?
There should be a section in the Support handbook outlining these commands. As long there’s the caveat of needing channel Op status, I don’t seen reason not to publish the commands and their respective reasonings in the handbook.
That. It’s been *cough* 17-18 years since I was last a mod on IRC and my memory is rusty. I started trying to use commands from another text based interface.
Let’s summarize a bit:
To answer those questions with my opinions…
I hope that all makes sense, but would love to hear what others think.
1. Seeing as I came up with the Google Sheet, I’m fine with it, BUT I’d like to (for now) restrict it to Admins, not mods. Unless my brain broke, mods can’t ban people anyway. And generally they alert the wp-forums list ‘Hey, this guy!’ so (and this goes with #2) we can keep track there. I DO NOT think we need to track spammers. I know Jan and I block a hundred a week, if not more. They don’t count here This is for people who go off the rails.
2. I’m okay with that. It’s important to have transparency. “. We asked you about before. Please stop this behavior.” and give it a couple minutes. Kick/ban. ” has been kick/banned for .”
3. That’s fine It’s also good to ping in #wordpress-sfd which is quieter (I am around often, but I let the content flow over me like Sherlock Holmes sometimes).
4. +1 agree
5. +1 agree.
One 1, sure thing. I didn’t realize that it was for admins now and assumed it was for mods too. I was looking at it from the IRC side only.
It all make sense to me.
I especially agree with “I’d also prefer a statement when someone gets kicked/banned so it will show in the logs” as I think that in IRC that should be included in the chat log as an explanation.
If that leads to users getting abusive (perish the thought) with the IRC OP then that can be handled separately.
Adding to my own here as we noticed today, a “contingency plan” would be ideal for when there’s nobody around who can deal with individuals who are acting out.
For now, email wp-forums (which is roughly the same as we do when someone’s being inappropriate off the forums – like when they follow you back to your email to tell you that you suck for telling them they were wrong).
A few days ago some behavior on the IRC #wordpress channel was brought to Siobhan McKeown’s attention. Take a moment and visit her post on that topic. After that visit Lindsey Kuper’s post on her experience in the #rust channel.
Back? OK.
Please do not use language based on someone’s looks or gender. It’s wrong and can’t be tolerated.
I had some difficulty expressing this in IRC but thankfully Siobhan and Mika provided me with support and they explained it well. The reason for my difficulty was simple: this is important, this problem needs to be stamped out early and I wanted to get this right.
When someone joins the #wordpress channel or posts to the support forums it is important to remember that they are either seeking help or attempting to help others. This is a good thing and that participation makes WordPress successful.
It’s not easy for everyone to join or start a public conversation. A forum post or joining an IRC channel is exposing yourself and that’s a risk. For some that can become a painful experience.
When someone replies using language that diminishes, makes people feel uncomfortable or disparages others then that participation is lost.
If the tone of the conversation includes words that focus on people’s looks or gender then that’s it. The person who wanted to join doesn’t feel welcome. That phrase about first impressions is true and an opportunity is gone. People stop participating or they never take the chance and do not even start to contribute.
At that point it’s the WordPress community that loses out.
Unlike the forums IRC is a live medium. There’s no moderation or editing and it’s easy to say something off the cuff. Everyone has bad days and may say things that they regret. And we all have a sense of humor that can be crass sometimes.
But using language based on gender or looks is not tolerable and has to stop. It’s not enough to be aware of this behavior. What will make it stop is when everyone speaks up if they see that.
“That language is not welcome here. Please stop.”
That’s it. That’s all it takes.
That reply alone raises the expectations for the whole community. That’s not a confrontation, that’s an invitation for others to join a community that does welcome everyone.
Let’s all raise those expectations. Speak up. You’ll be encouraging other people to do the same.
Yeah some people are too impatient and starts abusive language in minutes …grrrrr
Sadly the abusive language is the easy stuff. The place where it gets hard is where someone makes what would, amongst friends, be a probably acceptable joke. The causal racism and misogyny or misanthropy we’re often blind to because of its prevalence. Heavens knows I play Cards Against Humanity with some of my WordPress friends, and we make horrible jokes when sitting around together. The difference being is that those are comments made in private and amongst friends.
It’s hard on IRC, we’re talking to people who ARE our friends. But IRC is a public place. It’s not the place to make a joke about how hot a developer is, or an innuendo about hooks and hookers. Even though you’re saying these to your friends, you’re being heard by everyone. You have an audience, all the time.
The reason it’s important to step up and say “This is not okay” is that every time you don’t, you’re reinforcing the idea that it is okay. I know that sucks. I don’t personally feel that silence always means assent or approval, but take it a different way. When I see people saying things like they’d like to be ‘balls deep’ in women, and no one asks them to stop, I sure as spit don’t feel like that’s a community I want to be involved in, because clearly they have some people who are disrespectful, but worse, if I do step up, the odds are I will have not a single person in my corner for asking them to stop.
I want to stress this. I don’t find that behavior acceptable. I will ask people to stop, by name, when I see it, and I will back up anyone who says “You know, that language makes me uncomfortable. Please stop.”
You’re not alone.
Well said Jan, Mika & Siobhan. Thank you for raising the bar, and making this everyone’s responsibility.
I hereby pledge to speak up if I am witness to bad behavior in IRC!
What Jan said, what Mika said, etc. This kind of thing is one of the reasons we’re working on writing up community expectations over on the /community team.
Some things to keep in mind:
The fact that this behavior happens is in part on us — we’ve worked to make the rest of the project a more welcoming place over the past five years, and I remember #wordpress-dev being a bit more on the boys’ club end when I first got involved. As we worked on shifting tone everywhere else, we kind of left #wordpress alone. It’s time to give #wordpress the attention it deserves: not just to catch it up in the ways referenced in Jan’s post, but to bring these contributors further into the fold and recognize their efforts the way we do in the forums, docs, and other areas of contribution.
Other cultures may find the typical derogatory terms acceptable, such as calling people “dear” (out of context), so are we saying those cultures need to conform what is acceptable in the UK or US?
No. But we are saying that they, and we as Americans, have to be aware that what we say may have umi tended meanings. No on gets a free pass here. For example, in the US saying ‘dear’ is more likely to be taken as an insult because it’s sarcastic and snide. Flip it around, we call them ‘fanny packs’ and a fanny is NOT your tush in the UK.
It boils down to trying to be appropriate for the group, and when someone kindly says “Hey, did you know what that means here?” you learn and adjust.
And there is a massiv difference between “love to see you there, dear!” and “what a dear, I’d love to shag him.” Be aware of audience and context.
I’m not sure many people would like to be referred to as “dear” or “sweetie” as that can be seen as condescending. I don’t think you’d ever referred to me online that way but after I giggled I’d probably send you an email.
Just play it by ear. Intentions count for a lot and no one is asking anyone to parse every word they type through a content validator. Everyone has and continues to deal reasonably with others in the past. This is just to continue that as well as make people aware of this issue and ask that you help put a stop to it.
You know how the Forum Welcome is called er, “Welcome” and not “Forum Rules”? I don’t know who chose that wording (good job that) but this effort is along those lines. It’s important that you and all users feel welcome and not “regulated”.
There will be gaffes and that’s alright. I’m sure I’ll slip up (again) and refer to someone in a way that’s Not Cool™. Everyone gets a chance to correct their behavior.
*Drinks more coffee*
I hereby pledge to speak up if I am witness to bad behavior
I like that and I do too. That’s the best way to deal with this.
I hate being called “dear” – it puts me on edge. And I live in the UK.
Calling women “dear” (especially those who aren’t dear to you) is patronising. Here’s an excellent example: http://www.theguardian.com/politics/2011/apr/27/cameron-sexism-calm-down-dear
Good to know, I honestely didn’t.
If I get it right, not in the context of “Lieber Caspar, …” but “Caspar, mein Lieber, …” in combination with a patronising look.
There’s no moderation or editing and it’s easy to say something off the cuff. Everyone has bad days and may say things that they regret.
I’d say this applies to fourms too Sometimes people just don’t know any better too and think it’s ok. Speaking up against it in a non-confrontational manner is the best step when inappropriate
The way to deal with this is to appoint moderators who have the power to kick and ban people from the IRC channel. Currently, no one is empowered to act on behalf of the community. All they can do is ping someone else and ask them to do it for them. There are a group of very active users on IRC. Just as we have forum moderators, we should have IRC moderators.
We’ve talked before about this, but this is a good opportunity to give some of the regulars ops status. They can attend our weekly chats and provide information about what’s gone on that week for the support rep to report back on /updates/.
This is an unfortunate situation, but also an excellent opportunity to get the IRC folks more integrated into the community.
FWIW there are some technical issues with that. IRC has less granulated controls than forums. Also it’s harder to ban people since they can use another IP or nick pretty easily.
(Also I know I’m nit-picking and Shiobhan already knows this, but that’s only half of the way to deal with it. Kicking people out removes the current problem. Speaking up reinforces that it’s not cool, and prevents it from getting much worse, IMO)
Normally I do an OMGWTFBBQ post. Here’s everything in my current draft, ready for editing by everyone!
The first section is ‘Stuff we, as mods, should be aware of.’ The second is the post itself
Major changes
Auto Upgrader
* How to disable
* In order for Automatic Updates to be enabled, there are a few simple requirements:
* If the install uses FTP for updates (and prompts for credentials), automatic updates are disabled
* If the install is running as a SVN or GIT checkout, automatic updates are disabled
* If the constants DISALLOW_FILE_MODS or AUTOMATIC_UPDATER_DISABLED are defined, automatic updates are disabled
* If the constant WP_AUTO_UPDATE_CORE is defined as false, automatic updates are disabled
* Your WordPress install also needs to be able to contact WordPress.org over HTTPS connections, so your PHP install also needs OpenSSL installed and working
* Wp-Cron needs to be operational, if for some reason cron fails to work for your install, Automatic Updates will also be unavailable
* What gets updated?
* What changed. ONLY changed files!
* Only for minor releases (3.7 to 3.7.1 but NOT 3.7.1 to 3.8)
Less Major Changes
Under the Hood
For the post…. (More …)
Hello, I saw the link to this page over on #wordpress-sfd.
Under the subheading Don’t Panic: it is discussing not posting multiple times. I believe that “Post one” should be “Post once” or “Post one time”
Further down, there is a sentence about not liking the design of the WordPress Admin design. At the end of that sentence it says “…does not a bug make.” I would go with “does not make a bug.”
There are some troubleshooting steps just above the subheading Core Changes. One of them covers manual upgrading. In this sentence “…download a fresh copy of the latest.zip file of 3.5.” Should 3.5 be 3.7?
Under the subheading Not a Bug, it is talking about auto-updates. I think that “migitage security issues” should be “mitigate security issues”
Hope this helps!
–
Lorenzo
Twenty Fourteen is scheduled for 3.8 (yeah, I know, it’s in trunk for anyone running nightlies etc, but it won’t be seen when people upgrade to 3.7 on normal installs)
Fixed.
Switch to the Twenty Eleven theme should probably be updated to Thirteen or at least Twelve, since new installs don’t even get Eleven as of 3.6.
Made it 12 or 13, since 13 tends to scare people
“While you may disagree with this rational,”
I believe there’s an e missing from the end of “rationale”.
“While you may disagree with this rational,”
I believe there’s an e missing in the end of “rationale”.
Oy! Thanks!
My internship period is now over and I just wanted to take this chance to say a big thank you to everyone who supported me throughout. Special thanks go to my mentors @hanni and @ipstenu for their help and guidance, and to @jenmylo for organising WordPress’ involvement with GNOME’s OPW.
I was looking forward to meeting a few more of you in person at WordCamp Europe, however, unfortunately, due to personal circumstances, I will no longer be attending this weekend.
Getting more involved in the WordPress community has been wonderful, and I hope to continue contributing back to the community far beyond this internship. If you are, or if you know of a, woman interested in becoming more involved in open-source communities, please do consider the GNOME Outreach Program for Women: http://gnome.org/opw/. They are now accepting applicants for their next round, starting December 10th. Feel free to contact me if you want any more information on the application process.
Thank you again.
You are most welcome. I’m glad you are planning to stay involved. And 
to not being able to go to WordCamp Europe this weekend. Maybe you can make WordCamp London in November?
Thanks for all your encouragement throughout Kim! x
Hey all. Not long left of my internship now. Just a really, really quick update this week. I’ll mainly be spending my last two weeks helping @sabreuse with Troubleshooting documents. The outline for these can be found here: http://make.wordpress.org/community/troubleshooting-workshop-outline/. More to follow next week.
This is a problem that was found in the forums and turned out to be a legitimate core bug:
http://core.trac.wordpress.org/ticket/26627
Warning signs: People (or plugins/themes) using the pre_get_posts filter combined with the is_category() check can trigger the issue.
It is a regression from 3.7 behavior, so I think that it will probably be fixed in 3.8.1. In the meantime, there is a patch in the ticket.