A WordPress Site Reports “This Request Is Not Valid Error” in Microsoft Word? Try This….

Recently I’ve been working on a site that required me to put the entire developmental site behind a maintenance mode site. Our maintenance mode plugin of choice is WP Maintenance Mode, as it allows me to control both the front end, styling it beautifully, whilst still continuing the development of the site.

However, when reporting on the development, we were hitting an issue with the site, in that links to the site were causing errors when being clicked on in Microsoft Word. This was the error we received:-

503-error

After investigation, the error is due to the Maintenance Mode plugin returning a “503: Service Unavailable” error. Whilst the site appears up to users, the header returns tell software that the site isn’t up, causing errors.

Thankfully, there’s an easy fix. Within your theme’s function file (or better yet in your own plugin), put in the following code:-

https://gist.github.com/rhyswynne/11139039

This returns a “200: OK” header, which means links can be clicked on in Word.

Hope that helps anybody! If you have any questions, or any way to improve the code, please let me know in the comments.

He’s Hardcore (Contributor)

So yes, I know I’ve been terrible at posting here. Been incredibly busy (good busy!) over the last month or so. I’ve a few ideas for a post, but I thought I’d give a quick post on something that I’m excited to announce.

Last night, WordPress 3.9 dropped. A fairly large update to WordPress with a bunch of new features. You can read about these features in a post I wrote for the FireCask blog. But the cool thing for me? I’m in the credits.

wordpress three point nine

This is the first time I contributed to WordPress, so I’m delighted to have made it in the credits, even if it lead to a massive refresh of my WordPress Profile Page (I should link to it in the header). So yes, massively chuffed. Hope it continues!

So yes,  my code is helping run 20% of the internet. Scary, but chuffed.

A massive thank you to WP Contributor Day for getting me started on Contributing to WordPress (you can read about my day contributing here). If you want to contribute to WordPress, connect with the community, and have a lot of pizza and beer doing so, I suggest attending one.

 

WP Flipclock Released!

So today I’m delighted to announce the release of WP Flipclock!

This plugin is quite simple, as it adds a flipping clock to your site. So for example. Upto now you have been reading this post for this long:-

There are options where you can set it to be a count up/down clock, and from a specific date. You can also specify if you count down from days, minutes or hours.

It’s very simple, and needed it for a theme I was making, so thought I’d release the plugin out to the open as well!

Read the launch notes for how to implement it into your site, and if you like the plugin, give us a good review on WordPress.org. If you don’t and can think of another feature, check out the project on Github.

This plugin uses the Flipclock.js library from ObjectiveHTML.

The First WP Contributor Day in Manchester

So the weekend just gone I attended the first ever WP Contributor Day in Manchester. It seemed like the perfect opportunity to get started and more involved in the community that exists behind WordPress, and when the opportunity arose for a day of coding and contributing, in my adopted home town of Manchester, I jumped at the chance.

I’ve been keen for about the last 6-8 months for contributing to WordPress. But – like most – I just didn’t know where to begin. I’ve a local set up and am okay with version control systems, but that’s about it. I also know I can code okay, but wasn’t sure what sort of level of knowledge was needed, and whether I’d be completely out of my depth.

After a brief talk explaining all the ways in which people could contribute to WordPress from Jenny Wong, a talk by Graham Armfield on the accessibility team and an introduction on how to set up a local Vagrant based system from Mike Little, we then grouped off. Sadly my overconfidence in my set up did show as I was still a little lost, so after struggling for a little while with running commands from on my set up I bit the bullet and decided to join the team who were still installing Vagrant. I caught up and I was finally ready to go.

Well, after lunch.

So after lunch, I thought I should walk before running, and sat down, browsing the Core Trac for WordPress and finding a few patches to test. One of the first ones that took my eye was this one. It seemed like an easy one to test and correct if need be. After 20 minutes of replicating the problem locally, and then testing the patch fixed the issue, I commented and made my first contribution to WordPress, which was promptly Instagrammed. Boom! Job done, and I had a warm feeling inside me that I helped somebody out.

wp-contributor-day-2

I cooled down the warm feeling with a “first contribution beer”, and then browsed for something else. Ticket 27039 was great, but it was a theme. I kinda felt like I cheated a bit so thought I’d look at a bug in the core I could test. Ticket 23988 provided this – an enhancement in the page that lets people know the comments that an edited comment applies to. A quick test and I could confirm the patch working as such, so another comment and another beer (can you see a trend here?).

That’s all about testing patches, but what about writing one? Ticket 25295 provided that first go – a suggestion that wasn’t patched where additional classes could be added to captions of images. Following a quick read of the guidelines on coding standards I knocked up some code that expanded the shortcode to include a “class” element, and submitted it for hopeful approval. From reading the discussion there’s a good chance the ticket will not make it into the main release, but if it does and if anybody wants to work on it, then hopefully I’ve given them a start.

After one more confirmation of a patch working (26758), we headed for a wrap up, before going to the pub to socialise and discuss the day.

Days like the WP Contributor Day in Manchester was exactly what I needed to get my leg up and started in contributing to WordPress. It was great, and everybody was so helpful. So a big thank you to Jenny & Mike for organising it, and I’m probably heading to the second one all being well. And so should you.

How To Remove Links & Remove Yourself From a Blogger’s Christmas Card List at the Same Time

I awoke recently with an email in my inbox asking me for a link removal. Whilst no longer an SEO, I still have a lot of friends and interests in the field, including a couple of sites that are slightly dodgy, including a Bid Directory that was for a long time my biggest earner. It is woefully black hat, but meh. It is just there for the sake of being there. But rather than the link removal being requested for one of my dodgy sites, it was actually aimed at a site that had a pretty good link profile and editorially approved content (albeit dormant) – Blogging Dojo.

Here is the email in full.

Dear Sir / Mam

Our Website XXXXXX has a link from your website. We request you to remove that link at earliest because the backlink is hampering our website ranking and seo very badly.

Page where our link is placed:

XXXX

We also understand that your website integrity isn’t in question here but the penalty from google is severely affecting our business. The link has already had a very negative effect on our website SEO and business.

We believe that you would take action over it immediately or in case of no action within 24 hrs, we are going to have to file a “Disavow Link” report with Google. If we do this, it may affect your site’s Google rankings…

We would greatly appreciate your help with resolving this problem.

You can also let us know once the links have been removed by return email.

If you need any more information from us, please email me and I will be happy to assist.

We apologize for any inconvenience this has caused you and do appreciate your help.

Thank you and Regards,
Joshua Bender

Interesting huh? There were a few things that irked me about this email.

We Are Not Saying Your Website is Crap But Your Website Is Crap

Lets start at the beginning, this doozy.

We also understand that your website integrity isn’t in question here….

Yes you are! The next line is this!

The link has already had a very negative effect on our website SEO and business.

So you admit to saying my website is crap, and that being linked to me is harming your business. Effectively with this line you are saying you don’t want to be linked with me? Okay, you’re saying my website, but as most bloggers put their blood, sweat & tears into blogs, it’s often difficult to say when a site ends and a person begins – case in point being The Wolf Within Me, which is written by Cass on her Lupus. By shitting over sites you’d be happy to be a part of mere months earlier, you don’t exactly endear yourself to the group that probably made your business in the first place.

Timescale

We believe that you would take action over it immediately or in case of no action within 24 hrs…..

SEO is a slow game, with work taking months to have any sort of effect, and as such by posting this timescale for link removal to us we’re stressed. I mean, why have you gone for this timescale? A self imposed deadline by the client? In which case it’s you who have screwed up by not managing client expectations well enough. Let me guess, the client bought on your “insta-SEO” packaged that “Guaranteed #1 Listings”, and this is it unraveling all around you.

The fact is, bloggers generally don’t operate on a 24 hour scale, but usually a few days or more. Take for example outreach, I know when I did it I’d often get replies a week or two later for some blogs. I try and operate on a 24 hour turnaround, but on occasions such as this I couldn’t (I headed out after work, and no I’m not sacrificing my personal life for free because you screwed up). And it had me stressed, largely because of my last point.

Outright Threatening of Bloggers

This was the kicker for me.

we are going to have to file a “Disavow Link” report with Google. If we do this, it may affect your site’s Google rankings

Sorry, but that is utter bullshit.

I just thought this left a sour taste in my mouth. There are ways to do things, and quite frankly, outright threatening people is probably not the way to do things. Even when I was at my most shadiest as an SEO, I treated the people I dealt with with respect, and even my competitors. After all, I was taught to treat SEO as a bit of a game (hell, you ‘game’ the search engine), and whilst I compete against fellow SEO’s, I treat them with respect.

By threatening me, you’re effectively saying that you are willing to sabotage me and my hobbies (or business) in order to get your business back on the straight & narrow, a path deviated from by yourself, not by me. To me, that is a monumentally dickish move.

I reached out to a few SEO’s following receiving the email (and me be absolutely fuming because of it), and Will O’Hara pointed me in the direction of this link – https://support.google.com/webmasters/answer/2604774?hl=en – which seemed to suggest that even if an SEO “Disavows” you, then by and large you are unlikely to yourself receive a penalty. That was the general consensus from the people I spoke to as well.

The Shape of Things To Come?

The inherent problem of disavow is that people take a chainsaw to a problem where a pair of scissors is probably all that’s needed. By removing links (which, in this occasion, was okay), you also remove the factor that ranked you in the first place. You’re going to have to get these links back in some way using natural methods. Those links are probably going to come from bloggers – if you threaten bloggers, they’re probably not going to link to you.

I’m just worried about what the average site owner is going to think. I mean, I’d like to think I have some SEO knowledge left in me, and I wasn’t sure the intricacies of Google’s wondeful disavow tool. Imagine what bloggers without the experience or connections that I have would do when they receive such an email?

I just think if you take the approach above, you’re biting on the hand that feeds you, and then shitting all over it. Not cool, folks.