There are some known issues with the new glow blogs service. There were not deemed sever enough to stop the new server going live and the resulting downtime. Below you can see the known issues at the time the service went live.
You can also read about any new issues discovered.
Email Issues
There are a few issues around email addresses
A standard WordPress install uses emails addresses to add users and send users messages to inform them or in some cases to complete actions.
The new site has carried over the old glow RM easy mail addresses, which no do not work.
Users can add email addresses into the User section of the dashboard. This new email will get a confirmation with a link to follow to confirm.
Going forward this address will be able to receive notification of new comments. Currently email notification of comments is not enabled and these emails are not sent. This is reflected in the disabled state of the comment notification checkbox.
Hopefully this should not impact users in the short term as email did not work in the old glow blogs.
Deleting Blogs
Blog will not be deleted but held in an inaccessible archive and can be restored by the Super Admin
You need to respond to a confirmation email before the ‘delete’ happens.
The confirm emails often end up in spam folders, make sure you check if you think the mail does not get through.
This mail will also contain a misleading message:
if you delete your blog, please consider opening a new blog here
some time in the future! (But remember your current blog and username
are gone forever.)
some time in the future! (But remember your current blog and username
are gone forever.)
The blog will be archived, but your username will still exist.
The Flash File Uploader
The New WordPress 4 Add Media facility fixes this problem.
Vimeo embeds
The Upgrade to WordPress 4 included fixes for this issue.
The Upgrade to WordPress 4 included fixes for this issue.
Importing blogs
The Upgrade to WordPress 4 included fixes for this issue.
WordPress has a facility for importing and export from another blog. When you import the xml file it gives you a chance to map the posts from the import to existing users. The list of existing users is presented as guids, which look like a string of random characters.
My Blogs link
This issue was fixed in release phase 1.1
On the home page of each instance of blogs is a link to create blogs and a link to ‘My Blogs’. The My blogs link allows users to see a list of the blog they have a role on.
However if a user who has never logged onto the blogs service before is added to a blog by an admin they will not see this link.
Workaround, if you add users to a blog send them the link to the blog rather than the link to the Local Authority Home page.
Pupil’s comments always held for moderation
A student user’s comment is going into a moderation queue, even when they have an editor level role on a given blog.
Workaround, all comments by students will have to be moderated.
Access to non-public blogs on other Local Authorities
The blogs authentication is currently tied to the LAS instance. That means if you need access to a glow only or private blog in another Local Authority you will need the tile for that instance on your Unify Launchpad. Your school Unify administrator will be able to make that Tile available for you to your personal launch pad.
Hi Alan,
We have discovered this missing ‘My Blogs’ issue when users are added to a blog. I believe that is fixed and will be rolled out when all the interim fixes are applied. This will be after some testing etc.
As a workaround if the pupils go to the blog directly and log in through the link in the sidebar. The ‘My Blogs’ Link will appear after that.
David,
I can paste into a post from Word here. We probably need a bit more information to try and track your problem down. What version of Word, What Browser and version, Operating System.
RSS Widgets which are fed from glow blogs now refuse to load. All feeds report “RSS Error: WP HTTP Error: Connection timed out after 10001 milliseconds” I have tested the URLs with a feed verifier and they are correct and working. Is this simply that the new servers are so slow? Is there a solution that can be applied at Glow’s end? I know that there are workarounds involving burnfeeds but I am not happy to use either my own personal account or to set up dummy accounts for the school to achieve this.
Hi Graham,
I wonder could you send a bit more detail?
Where these feeds working OK before the migration?
Could you give URLs for where the feeds are coming from and where you are attempting to show them?
cheers
john