I’ve not had much time to blog about the Blogs Update Phase 2.2 – WordPress 4.1.2 in Glow Blogs, but I spent a wee bit of time on a new blog showing the features the Blogs gain from jetpack. Imaginatively I called the blog Jetpack. There are lots on nice things for blogs and school websites in Jetpack.
There are a couple of nice new themes and other plugins too. More later.
Last week I attended the WordPress Big Media & Enterprise Meetup in London.
I was asked down to talk about Glow Blogs. Given this was a meet up of pretty serious WordPress developers I was reasonably nervous about talking to them. I decided that I’d give an overview of Glow Blogs through the lens of a look at the parallels between of the benefits of publishing in the open by pupils and teacher and open source software.
My point was that the benefits of sharing collaboration and serendipity are applicable to blogging in education and developing open source software.
The VIP wordpress folk have been kind enough to post the video WordPress For Weans – how the Scottish education system is encouraging kids to contribute with confidence
Apart from anything else this makes me realize that the number of physical tics I have when speaking means I should stick to podcasting.
I was fortunate to be speaking first, which left me able to listen to the other presentations in a more relaxed frame of mind. In each one of them I found ideas that would fit in well with the Glow program.
These presentations are beginning to find their way onto the WordPress VIP News
Steph Gray & Luke Oatham, Helpful Technology talked about WordPress On The Inside – how the UK government is deploying WordPress as an intranet platform
My main take out from this was how powerful and simple WordPress can be for providing information. Steph and Luke talked of how they hard replace a Sharepoint intranet with WordPress, one of the most interesting benefits was reducing the amount of time that people spent on the site. Rather a different aim from most sites! The site they spoke about was designed to help people:
Perhaps having a chat along the way
At the moment Glow blogs are used for school web sites, class blogs, e-portfolios, information portals and more, but this presentation points to other uses I’d not even considered if we can develop the service further.
–
Duncan Stuart is Head of Products at dxw presented on
Snakes In A Plugin – WordPress plugin security. He started by getting the room on their feet and then sitting down if they did not have various security procedures in place. Glow was one of the last ones standing, speaking to the formality of the testing that we do on the program.
Duncan then demoed hacking a WordPress site though what appeared to be a regular comment notification email.
@DGMStuart steal all my happiness showing how to hack WordPress
— john johnston (@johnjohnston) March 10, 2015
Scary stuff but I am somewhat reassured by the Scottish Government development and testing team. I’ve often moane about the time taken for testing and security, this talk clearly demonstrated how valuable this is.
Matt Haines-Young, Human Made: ‘Making WordPress shortcodes a piece of cake’ (link to video to follow)
ShortCake is a plugin that allows developers to develop further plugins to allow users to insert Content Blocks into their posts in the same sort of way they insert media. Dialogs to enter content without codes and WYSIWYG editing in the post editor after it is inserted.
This supports the kind of thing that users have been requesting for Glow Blogs and a much nicer experience for bloggers. Given that we still need to develop the process for getting plugin and enhancement requests and implementing them I am not sure how we would do this, but on a brighter note there was some discussion of this becoming part of the core WordPress system. We would then have access to it when we upgrade WordPress in Glow.
Jack Rivlin & George Marangos-Gilks, of The Tab: ‘User generated plus: blending professional journalism with a disparate network of voluntary contributors’ (again link to video to follow)
The Tab is a bit like your student paper – except better. We cover the news students care about, in a style they actually want to read.
The Tab is actually quite like a red top, not only in it colour scheme. What is interesting is the system, based on WordPress, allows a mix of professional and amateur content. This was a great demo of the power of WordPress to bring content together and present it. students from across the UK contribute to this huge online student mag.
In a TeachMeet fashion everyone headed over to a nearby bar and I had some fascinating chats. This reinforced my feeling that we can do a lot more with GlowBlogs, there are endless exciting possibilities.
I was also impressed by the amount of effort some WordPress developers put into giving things away for free. This extends way past source code to education projects of all sizes. I spoke to someone planning a huge project to educate prospective journalists through blogging in school and college, the idea being that the WordPress editor would be custolmised to help the students write balanced and well researched pieces.
If you are interested in Educational blogging I’d recommend the videos linked above, not because they are directly aimed at education but because they point to and hint of endless opportunities for different ways to use blogging in education.
Thanks to the Organizers for inviting me.
The new iOS WordPress app editor is so much better than before. I am not sure when this happened.
It is a vast improvement on the older version that I looked at before, much simpler and a reasonable WYSIWYG experience.
The only useful feature I can think of that is missing would be an in app image resize to upload photos quicker on poor connections.
I posted #glowblogs improvements: mobile a few weeks ago praising the mobile browser but this is tons nicer.
We ruled out using the mobile app for Glow reflecting security concerns from the technical team. I hope the mobile web follows some of the same design.
This post is, of course, completely constructed in the mobile app.
Like anyone with any sense I read Alan Levine’s blog religiously. It has given me more ideas to think about and play around with than any other site on the Internet.
The other day I read Share Images By Email to SPLOT Collector (this post is now well down the post list as Alan blogs like a manic).
I was very interested in this, as I’d loved posterous until it was abandoned. One of the main things I liked about posterous was the posting by email facility. This allowed me to publish photos from my phone even with a terrible connection. I first noticed this on holiday in Galloway when I didn’t see a signal all week. I did keep my posterous updated with photos because the mail app on my phone magically seemed to be able to find a signal when I was asleep and send the photos over. I’d got it in the back of my mind to replicate this behavior with WordPress sometime, Alan’s post gave me the details of how to and the impetus to do it.
I’ve already got a reclaimhosting account for quickly setting up things to play with. It took me a quick 5 minutes to install wordPress, set the theme to the one Alan recommended (Fukasawa by Anders Norén), add the Jetpac plugin to handle mail, another plugin (Auto Thumbnailer) to automatically use images as featured images and add a css tweak. All following Alan’s instructions.
This had me covered for the main features of posterous, post via email and handling images in a pretty way.
As I wanted to post multiple images I also turned on the ‘Tiled Galleries’ and Image Galley Carousel provided by Jetpac and tweaked the CSS
a bit more for that. Another couple of minutes.
The system seems to be working just the way I wanted and yesterday I added a couple more features. Posterous had an interesting feature that allowed you to automatically forward whatever you posted to other services. I had a quick search for a WordPress plugin to do this but ended up at ifttt.com. There I found: Post WordPress Featured Image to Flickr. This just deals with the first image, but a quick test proves it works. I’ll probably explore posting all the images later.
While I was on ifttt I also notice Instagram photo to WordPress blog so have thrown this into my mix. I can now post to Instagram, have that picture added to the blog and also sent on its way to flickr.
Apart for the sheer fun of doing this, it also fit in quite well with the POSSIE, own your own space agenda.
Alan’s SPLOT | Smallest Possible Learning Open Tools project is fascinating.
Smallest/Simplest * Possible/Portable * Open/Online * Learning/Living * Tool/Technology
Update: forgot to add the link to the blog: Mobile Photos — From my phone via mail
I’ve not blogged much about work recently, but this story is a good one if somewhat tangled.
We are working, in the Glow blogs team, on the next release. This is mainly to address any problems with the upgrade to WordPress 4.0.1 that came out in January.
My work includes: watching reports come through the help desk; passing on problems that come directly to me (twitter, email and phone) through to the RM. I do a wee bit of tyre kicking and talking to the test team on the way.
On Tuesday I got a mail from a teacher, to the effect that the link to My Sites from the Local Authority home pages didn’t work. Talking to Grant, one of the test team, I found out he was chasing the same problem. We kicked it around a bit and found that if a new users creates a blog on their LA before accessing My Sites, the link did not work, it leads to a list of blogs that the user has a role on.
This is not a show stopper as the user can click on any of the blogs and then the My Site link in the Admin Bar as a work around.
While testing this out we noticed that although the Admin Bar is visible on any Glow blog in your Local Authority, the My Sites link on it leads to the same error (with a list of your sites page).
Thinking these were linked I raised a call to the RM help desk. This got passed through to the team at Automattic. They have quickly fixed the first issue and recorded the fix in our system (JIRA) for following development. The code will be in the next release, hopefully in two or three weeks.
At this point we asked about the second bug, we were told that is was in WordPress core and the team had not only reported it but proposed an initial fix. It is worth pointing out that this was put into the WordPress tracking system at quarter to eleven on Thursday night:
#31314 (My Sites admin bar link broken when on blogs you have no role on) – WordPress Trac
You can see from the linked page, that the ticked was closed at 6:29 on Friday morning. The fix and some improvements are currently attracting the attention and input from three other developers who are completely unconnected from Glow.
The people that helped with this one included:
Which quite a complex system, but it seems to be working. Most of these people are on the hook and doing their job, but I wonder if a bug in a commercial system would be fixed so quickly? We don’t have the bug fixed in our system but it looks good for being sorted out in a subsequent upgrade.
For me this was pretty exciting. It feels pretty good for those of us who think that Open Source and Openness in general is a good idea in Education.
Yesterday at 4 O’Clock the glow blogs system was upgraded to WordPress 4. The site was down for around 4 minutes.
Glow blog are now running on WordPress 4, not much a a big deal as most other WordPress blogging site are doing the same. But we just upgraded >140000 blog for WordPress 2.9.2 to WordPress 4.0.1 a pretty amazing effort. Setting up from scratch would be simple enough, looking after all of the foibles of a creaky system a bit more complex.
It has been a pleasure working with the Blogs Team for this release, including:
Sonali Nakhate Project Manager; Turnbull and John MacLeod from the technical team at Scottish Government; Grant Hutton and David Orr of the test department at Scottish Government and Code For The People, now part of Automattic who managed to get aquihired by the company behind WordPress.com during the project!
We also got a ton of support in all sorts of ways from the extended glow team at the Scottish Government and Education Scotland and from many in the wider Scottish Education community.
Although this is the second phase of the blogs project it is really just the precursor to the next phase. We are starting to discuss the plans for phase three now. This is, I hope, the really exciting bit…
The Glow Help Blog is being updated and I am listing some of the main changes here: Blogs Update Phase 2 WordPress 4 – Glow Blog Help.
On of the real benefits to upgrading glow blogs to WordPress 4 will be its mobile interface. When WordPress 2.9.2 came out in 2010 we were just into the start of the mobile web and the term responsive web design had just been coined.
Now a large percentage of the population have devices in their pockets that are more than capable of posting content online.
. The WordPress dashboard now is responsive resizing and rearranging the tools to fit on my screen. Adding an image is simple and a gallery is easy enough.
WordPress now lets me select several images to insert in a post or create a gallery.
This post was started in the train, continued on the tube platform and finished on the couch all using my phone.
Personally I am not the greatest typest on any device. Many folk will be faster. Or I could start a post while mobile, capture images and save that as a draft for later.
I am looking forward to seeing how glow bloggers go mobile next year.
Since WordPress 3.9 the TinyMCE editor now automatically cleans out all but the semantic HTML from Word (or Rich text copied from elsewhere), meaning any fonts, styles, etc. You preserve headings, blockquotes, lists, links, bold, italic.
From: Peek in the SPLOT: TRU Writer
This means WordPress handles text pasted from word a lot better that the current WordPress 2.9.2 does
Even though, like Alan, I don't think writing everything in word is a great idea lots of folks do exactly that. This then should be useful for #glowblogs after the upgrade.
I'll be posting a few things here about the changes in glow blogs coming in January over the next few weeks.
Last Friday at the same time as the glow authentication changed, the new glow blogs service went live. I posted about this over on Glow Connect.
It was pretty exciting stuff, the developers were really working right up to the last minute and beyond to deliver the service. Even so we have gone live with a few know issues and have already discovered a few more.
At the start of the processes I certainly was not aware of all the complexities involved nor the scale of the job. Turns out it was a big complex job!
Luckily for me I ended up working with an amazing team, not only in the Scottish Government, but in the developers and suppliers. All of them worked long hours with very positive attitudes as I grumbled along. I am tempted to turn this post into a list of these characters and their qualities, but probably enough to say all of the blog team were essential to the process.
Stray Puppy by p medved
Attribution-NonCommercial-ShareAlike License
At the end of this phase we have a working set of WordPress MU, one for each Local Authority, running the same version of the software as before and we have the known issues linked above.
The main improvement so far is around blog creation. There is no connection to SharePoint/old glow groups. This simplifies the process a great deal. This and other Main Changes are listed in the Glow Blog Help, some of these are not improvements but changes.
One more improvement, not listed, is that you can now upload files of up to 50mb to blogs. This should make it a lot easier to podcast or share small videos without using a third party site or service.
On Wednesday I popped back to North Lanarkshire to watch my colleague Ann McCabe set up a class of e-portfolios, this was much quicker than before, taking away at least half the steps. There is still plenty of room from improvement and I got a great idea to take back to Victoria Quay from the RM help desk who I visited in the afternoon.
Given the above, if this was the end point in the process I’d be pretty disappointed. A lot of work for not much in the way of improvement. I am not disappointed due to two things, phase 2 and phase 3.
Phase 2 was looking quite simple, upgrade to a new version of WordPress. This will bring a host of benefits, better user experience especially on mobile being the main gain. More important, in the longer run, is that it gives us a much better base to develop on.
The other aspect of phase 2 will be to backfill in things that were dropped out of phase one or needs that were discovered in phase 1.
It looks like phase 2 will take a bit more work than I expected, but this will start straight off. Already some of the first problems to be discovered has been solved and the developer team are just waiting to decide when to deploy the code. Another potential ongoing problem with server load is now beginning to be understood and the team are working on finding the best solution. The team are keen that the server gets a chance to bed in and are suitably cautious about changing things on the live system, best practises for ongoing change and development are being put in place.
After we get to phase 3 of the project things might speed up a bit. We will be using WordPress 4 which will allow a lot of nice things to happen.
The one I am most excited about is giving a more flexible service. In the old glow blogs it was a constant frustration for myself and many others that our theme and plugin requests were never answered. I am not entirely sure of all the reasons for this, but having peeped behind the curtain I presume some of this was to do with testing.
Watching the new blogs service develop gave me a bit of a shock in the amount of time and effort it needs to deliver a service of this scale. Like many folk who publish stuff on the web I frequently make changes without much of a care and worry. The Technical Architects and developers for glow take a somewhat different view. There first concern is the preservation of users data and stability of the service and given they are taking care of over 100,000 blogs…
The glow blogs system now consists of 4 main servers: integration (where new code is added after code review), explore (for testing), pre-production (more testing) and live. With the older version of WordPress we are using a lot of the development and testing is manual, the testers here and volunteers going through lists of test to test the functionality of the blogs. In addition there is security, load and a many more tests.
Going forward the process should be automated, the newer version of WordPress can have a deal of automatic testing, code going onto the integrate server would be pushed through the different servers being automatically tested on the way, this gives us the possibility of a much more agile service.
On Friday last week there was a fair amount of cheering and happy faces around the glow office, since then feedback has been mainly positive. I am not really ready to celebrate yet, there still is a lot to do before we reach the point learners and teachers in Scotland have a world class blogging platform. There so many possibilities out there for doing all sorts of things with WordPress. We would, of course be really interested to hear of any ideas of what you would like from Glow blogs.
43/365 by krystian_o Attribution License
TL:DR I’ve just migrated my blog, please let me know if you find broken things and I’ll try and fix them.
In the midst of the glowblogs migration project I am involved in professional I’ve been working on a wee migration of my own. For the past nine years I’ve been blogging using pivot (later pivotx) this weekend I’ve moved to WordPress.
I started using pivot back in 2004 as my class blog mainy because it did not need a database on the website and then that cost a bit more. I stuck to it as I found it easy to theme, and adapt for various classroom projects. It seemed fairly natural to use the same system myself.
Pivotx seems to be changing but quite slowly, the promise of pivot 4 was from 2012.
I’ve been attracted to several interesting WordPress technologies and plugins and now use it for edutalk, ScotEduBlogs and my ds106 blog. The feedwordpress plugin is of especial interest.
A wish to eat my own dog food given I am promoting WordPress for glow.
Originally I though of turning the whole site/domain to WordPress, to include my ds106 blog: 106 drop in, but that looked a wee bit to tricky at the moment. I also have a bunch of straightforward html pages and experiments which I want to leave in place. Also there are a few challenges to moving the pivot posts to WordPress that seemed enough for now.
There is not a simple pivotx imported for wordpress, I found Migrating your blog from PivotX to WordPress | filmvanalledag which looked as if it was a near fit, but missed out tags and comments. I’ve also been using disqus comments for my blog but wanted to move to standard ones without losing disqus.
That filmvanalledag post gave me a great start with example.org/?feed=rss&c=*&n=10000 I used this to download the rss feed for all of my posts (>800).
I decided that the RSS import would lose all my tags and comments so went for another approach. I have a bit of experience with kludging together a standard WordPress import from other things. This is probably of little interest to anyone but myself, but briefly I use SuperCard to creat a simple pseudo database of the rss add in the missing keywords by downloading them directly from the database and then manipulate it into a wordpress friendly format, for example getting the tag list like this:
uid,"tag","contenttype",target_uid
2533,"assessment_is_for_learning","entry",1132
2535,"blogging","entry",1133
2537,"scotedublogs","entry",1135
2536,"newyear","entry",1135Directly from the database and turning it into:
<category domain="post_tag" nicename="glowscotland"><![CDATA[glowscotland]]></category> <category domain="post_tag" nicename="glowscot"><![CDATA[glowscot]]></category> <category domain="post_tag" nicename="blogging"><![CDATA[blogging]]></category> <category domain="post_tag" nicename="wordpress"><![CDATA[wordpress]]></category> <category domain="category" nicename="wwwd"><![CDATA[wwwd]]></category> <category domain="category" nicename="jj"><![CDATA[jj]]></category>
For each post.
I tested the import of my export on a local version of wordpress and also worked out some htaccess stuff.
My old blog links were like this: http://johnjohnston.info/blog/?e=2462 and wordpress expects this http://johnjohnston.info/blog/?p=2462.
It took me a fair bit of googling and testing to get something that worked, although not quite correctly, http://johnjohnston.info/?e=2464 once I turned on pretty links goes to http://johnjohnston.info/blag/what-is-openness/?e=2464, not removing the ?e=2464, ?p=2464 works properly. Once tested I created a new WordPress on the site, at /blag, set it up, did a little more testing and have just moved it to /blog after changing the urls in the General Settings Screen.
The other main problem was that I was using disqus for my comments on the old blog and being a packrat I did not want to leave them behind. So I’ve added a bit of logic to this new blog where older posts will display the disqus form and any comments but going forward I’ll use the standard WordPress ones. I can’t see any way to import the old disqus comments into WordPress at this point.
There are more things to fix, and I’ll try to pick these up as I go along. After that I’ll be looking to play around with some wordpress plugins and the like.