Back on WordPress.com

WordPress MoveAfter ten days of blogging on WordPress.org, here I am, back on WordPress.com. It’s a decision made with both hope and regret, but one that I need to make in order to continue the work I started.

Over the past three years on WordPress.com, my ability to write code (PHP and JavaScript in particular) had degraded quite a bit. I had thought that by self-hosting my blog, I’d be more motivated to try new things, and force myself to learn as I inevitably broke things on my own blog. It turns out that such a tactic had the opposite effect. I had every intention to break things and learn, with daily plans even, but I was too timid to put my rusty skills to the test on a live blog.

Considering that, my main blog is now back on WordPress.com, but I’m keeping a few self-hosted test blogs around so I can break things and learn without fear. I still learned quite a bit in just ten days, like how to have a similar setup to WordPress.com, working with caching, choosing a stats program, and how to work with Genericons (which you can do on WordPress.com with certain themes). I even helped fix two bugs in the Authy plugin.

As for the rest of you still on WordPress.org, if you use Jetpack, I submitted a few bug reports and feature requests you might like. One of those might even be my first patch one of these days.


Comments

18 responses to “Back on WordPress.com”

  1. Be brave, put your main blog on a self hosted server and test the hell out of it with dodgy code and mad ideas. It’s what I do! πŸ™‚

    1. I will, give me a few months. πŸ™‚

    2. Seriously! Worst case, VaultPress has your back. πŸ˜‰

      1. For sure, and I was using VaultPress, and will be again when I move back. πŸ˜‰

  2. Welcome home! πŸ™‚

    1. Thanks, it’s good to be back! πŸ™‚

  3. [ Smiles ] Welcome back, James!

    I am pleased to know that you were brave enough to try out the self-hosted version!

    1. Thanks! πŸ™‚

      1. [ Smiles ] You are welcome, James!

  4. You can always ask me for help with breaking your selfie πŸ™‚ (Also I’ll pimp Genericon’d for self hosting πŸ˜‰ SHORTCODES)

    1. Genericon’d is awesome! I went ahead without it as it had been bugging me that I couldn’t quite figure it out. Now that I have, I have a lovely Genericon “Follow Elsewhere” widget in my widgets area above, since we can’t exactly use Genericon’d here.

      When I’m ready to go again, I’ll take you up on that offer to help break it, but you might regret it. πŸ˜‰

  5. Welcome back to the fold. πŸ™‚ I also set myself a goal this year of becoming more familiar again with WP standalone. Regretfully, it’s not been easy to follow through on as I’d thought. (Tried to leave the comment on G+ but it wouldn’t post, dangit.)

    1. Thanks! Let’s see how we do at that goal this year. We’re both running out of time, but there’s always next year. πŸ™‚

  6. Jetpack sends out the entire article as an email to subscribers instead of the excerpt. That is not acceptable for driving traffic.

    1. It uses your feed’s setting, so at Settings -> Reading in your blog’s Dashboard, change “For each article in a feed, show” to “Summary”.

      1. It is set up that way and subscribers are still getting the full post…idk.

        1. It shouldn’t be that way. I recommend contacting Jetpack support.

  7. […] too long ago that I moved to WordPress.org after an almost three-year absence, and then quickly moved back to WordPress.com. I had a lot going on and just wasn’t ready to take the plunge. Now, I am ready to take the […]

Discover more from MacManX.com

Subscribe now to keep reading and get access to the full archive.

Continue reading