Upgrade WP & Theme Impacts
- This topic has 3 replies, 3 voices, and was last updated 5 years, 6 months ago by .
Viewing 3 reply threads
Viewing 3 reply threads
- You must be logged in to reply to this topic.
Home › Forums › GovIntranetters › Upgrade WP & Theme Impacts
Tagged: theme update, Upgrade
Hi All,
We’d like to bring our installation of this them up to spec.
We’re currently on the version 4.34.3 and want to bring it up to the latest version.
Also our installation of Word press is a version behind and we’d like to bring it to the latest. Our current version of WP is 4.4.1 and we’re aiming to bring it to Version 5.2.1
I note that the theme isn’t reporting its name properly. It currently says “Theme Name” and the reason we’ve held off doing these upgrades for so long is that, in the past doing an upgrade on it has caused the WordPress white screen of Pain.
And to be honest I don’t want to edit the MySQL by hand to fix it.
are there any gotchas I should be aware of?
Thanks.
Hi Gavin,
You should be able to use the theme with the latest version of WP. The main concern would be your server. Your server needs to be running a minimum of PHP 5.6 in order to use the latest version of WP.
Hope that helps!
Main theme updates since 4.34 deal with auto expiry of news stories and events.
Some options (custom CSS and theme colours) have been moved to the WordPress customiser and away from the GovIntranet options – you may want to keep a copy of any custom CSS and colour settings just in case they get zapped!
Hi Guys,
Thanks for your reply.
TBH: I just snapshotted the machine and went for it.
It worked fine with only one minor snag (we need to use LDAP – which wasn’t enabled after the upgrade, and nothing to do with the theme).
I’d actually done all of the prep work I needed to do by having PHP 7 available so we just went with that.
Thanks again.
Cookie | Duration | Description |
---|---|---|
comment_author_email_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_url_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
comment_author_{HASH} | Under 1 year | This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wordpress_logged_in_[hash] | Indicates when you’re logged in, and who you are, for most interface use. | |
wp-settings-{time}-[UID] | This is used to customize your view of admin interface, and possibly also the main site interface. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | Used to distinguish users. |
_gat | 1 minute | Used to throttle request rate. |
_gid | 24 hours | Used to distinguish users. |