As we’ve explained in previous posts, WordPress is a great platform, but it needs your help to stay current. The good news is that WordPress does a great job of letting you know when an update is available, it’ll show a yellow bar at the top of your Dashboard saying a new version is available and asking you to “Please update now.” Just like this:
Updating the core WordPress files keeps you secure and provides lots of cool new features with each release. The updating process itself is simple, but not without its pitfalls.
WordPress recommends backing up your database and content before any upgrade, just in case something goes terribly, horribly wrong. That seldom happens, but if it does you could be trapped with no website!
In addition, plugins have to be regularly updated, too, and they don’t always match up with the new core WordPress release. This can lead to compatibility issues that affect display and function, and can even force a plugin to stop working completely.
But never fear – Spotted Koi is here! Let us help you with our WordPress Upgrade Service, which takes all of the worry out of the process. We square away your backups, compatibility checks, and quality assurance work to get you back on track within an hour. For more information about this wonderful little service, click the link above or find the full list of Spotted Koi services here.
I’m using Firefox on a Mac, I’m going to drop to the next line now!
That should’ve been a paragraph break, now how about underlined, italics, bold and strikethrough.
Next how about bullet points
And let’s make a Link!
Google Chrome (latest version)New lineNew lineNew lineNew lineBlank line above this.Thank you!
First line.Second line. A blank line follows…A longer paragraph: “I cannot praise a fugitive and cloistered virtue, unexercised and
unbreathed, that never sallies out and sees her adversary but slinks out
of the race, where that immortal garland is to be run for, not without
dust and heat. Assuredly we bring not innocence into the world, we bring
impurity much rather; that which purifies us is trial, and trial is by
what is contrary.”Milton.
The line breaks I put in using the editor disappeared, but the line breaks in the cut-and-pasted text (which html ought to ignore) were retained. I’m using Firefox 13.0.1.
Firefox 13.0.1That was paragraph 1. This paragraph 3.This is an embedded link.
I am currently using chrome 19.0.1084.56 m – which it tells me is up to date.This line is after 2 <returns> and should start as a separate paragraph. Here is a link to the latest post on my blog.
This is not good because I now end up with white text on white bg. And haven’t a clue whether or not I’m making any typos.
Don’t know if this makes any difference or not, but you should know that the wysiwyg options available here are quite different to those on Keith Kloor’s blog.This line is after 3 <returns> … wondering if it might make any difference.Using <H2> after 2 <returns>The quick brown fox jumped over the lazy dog … and there does not seem to be any way of getting to html mode from here. But perhaps this is intentional [this line after 3 <returns> again.
Hey everyone, thanks for commenting here and testing it out, I’m getting the impression this comment plugin isn’t the best choice, please let me know your thoughts.
Hilary: FYI, the Incident text will be different on Keith’s site, we have styles applied that are specific to our site here so that will at least not be a problem.
Did anybody have better luck on the other site? Or any luck anywhere?
Thanks!
Tony