Some of you may have found out by now that the standard editor in WordPress 5 has now been permanently removed and replaced with the Gutenberg editor. Now you are stuck and not sure what to do because nothing is familiar.
For Divi users it is a bit worse because they have changed their interface as well to coincide with the release of WordPress version 5 and if you are not careful you may end up deleting your page altogether if you try to revert back to a standard editor.
When you are editing a website, particularly when carrying out formatting it is useful to have a colour palette handy so you can apply the colours used in your website.
If you have a Divi based website it is possible to set these up so that they are available whenever you want to do some editing.
In or around 2007 Home-Start had a very comprehensive guide for styles for websites and printed materials. It has changed over the years, but some of the colours are still commonly in use.
I will create the palette below with the hexadecimal RGB values and also show you how to add them to the website palette built into Divi.
Please note the guidance at the bottom of the image. The ultimate source for guidance on Home-Start branding is from Home-Start UK. Not from me. They will frequently change their guidance for branding. If in any doubt contact your sources at Home-Start UK.
All of the websites either automatically upgrade themselves, or I initiate an upgrade on most of the Divi based sites once per week through an automatic process.
From time to time a plugin developer will do something that creates an incompatibility on your site, or impair the performance.
GDPR Plugin by MOOVE Agency.
Some of you have a GDPR plugin in use from MOOVE Agency. It started off as a very simple and elegant pop up which advised you of the Privacy Statement included in websites following the GDPR regulation coming into force in May.
It worked very well for several months, and for some reason they started to change things in the plugin, and introduce some bugs. There is one at the moment that is slowing websites down. It depends on the state of the plugin on your website.
On many Home-Start sites, and some of the regional charity websites I have included one or more password based pages. You can add these yourself, it is controlled in the editing view of the page or post on the right handside where it refers to Visibility. You have the following available:
Public (and stick to the front page)
Items are normally set up as Public. If you use Public and stick to the front page, check what it does first. It may not work as you expect it to work because it relates to the template.
Password protected pages in Divi
There is an annoying problem with password protected pages in Divi, if you try to enter one the first time you will see small writing on the left and a button on the right. On a wide screen these look totally disconnected, and not obvious. If you have a non Divi based website, you are unaffected.
I have been using the new editor in WordPress on my website. It is a bit of a learning journey, but I am getting the hang of it. Like most things it needs a little effort on the part of the editor to learn how to use it.
However, I do this every day and you do not. My guidance for now, is stick with the standard editor that is currently in WordPress and leave it a few months before considering upgrading your installation. I am concerned for those of you that dip into your websites once a month or less, the learning curve is going to be too steep, and as a result websites might no longer be updated which would be a disaster.
Latest news on this: 1/10/18 Moove Agency have reported a new update to this plugin as of 8am this morning. So this problem may resolve itself without any intervention.
I have added a GDPR cookie plugin to some sites which provides a warning message at the bottom of the website. This has worked fine for five months up until a couple of days ago when the plugin author introduced a bug which affects how it is presented.
It is not a critical bug, it affects presentation more than anything else, but is annoying.
If the bottom of your website has a large white area and the text left justified on your screen tightly in the bottom left corner, then you are affected.
If your site looks like this or you can see a cog in the bottom corner of your screen then you are unaffected. The cookie warning usually looks like this for first time visitors.
This is only of interest to Divi template based websites. If you use this facility in your template and it is not Divi based, take care to check what it does before you accept using it. Different templates work in different ways.
Many of the latest Divi based designs I have been building for both Home-Starts and other groups have at least one news page, often more than one. For example a summary on the home page of the latest six news items is useful, and a fully featured news page as well for everything.
You can do this on other sites, but within the Divi environment it is very easy to use: you can have a fundraising page, and at the bottom of the page have a Fundraising blog. This is an automatic feature where any new posts which you categorise as Fundraising will appear there. They will also change over time as you add more content.
Personally I use Chrome for most of the work I do from a computer. I may use MS Edge (rarely) or Firefox to test outside of the Google Chrome environment. While doing some of that testing I was surprised to see that it can be difficult to enter some information to get past this Google Recaptcha 2 screen below.
In June of this year Google changed the map service (and many other services as well) which we use on our websites. For most of you it does not make too much difference, in some cases however you may see grey screens where a map should be present, or comments over a map. If you see this let me know please.
It depends on whether the plugins in use on your site are using a Google API (Application Programming Interface), these now require keys to be generated. That is not such a problem, but now you cannot create them without the key being assigned to an account with a credit or debit card assigned to it.
The following is from a Google Developers website, note the text in the orange section below:
The mapping information used to be free and very useful. It is still free provided the number of calls (aka visitors) to the map does not exceed a credit limit which is being provided by Google. I am understandably not happy about having my credit card associated with your site in this way because I have no control over it. At the moment each call to create a map is 0.7cents (USD) which equates currently to 28,000 views per month.
It looks as though Google is offering a £100 credit, or $200 depending on where you look on the API type on each account. I need to figure out how to manage that so that the number of calls never exceeds £100 in any billing period otherwise I start to get charged.
I guess Google have placed a lot of time and money in the development of the APIs and now they have us all hooked they are choosing to monetise them, which is not so surprising.
In some cases I have embedded maps into your websites, and in others they are generated through plugins such as Modern Tribe Calendar. Check them and if there is a problem let me know.
There is a risk that the credit being offered by Google is just a transition to full billing in the future. Time will tell.
Right now, I am looking at this problem in detail on new developments. So more to follow later when I have figured it out.
We are using cookies to give you the best experience on our website.
You can find out more about which cookies we are using or switch them off in settings.
You can adjust all of your cookie settings by navigating the tabs on the left hand side.