Today, we successfully upgraded all Cloud Demo and Preview instances to our 2019.4 version. Because this upgrade requires downtime, we are scheduling it within a window during non business hours. Your upgrade window depends on what data center your instance is hosted in, and is as follows:
For instances hosted in our Amsterdam data center: May 7th, 2pm-8pm PDT
For instances hosted in our Phoenix data center: May 7th, 7pm-12am PDT
Due to the way our upgrades get batched together, we can't guarantee a specific time that your upgrade will happen (and thus, your instance is down) other than that it will fall in these windows. Let us know if you have any questions about this!
Just letting everyone know about our next Cloud release which is due to hit Production on April 30th (with Previews getting the same upgrade on April 23rd). This quarterly Cloud release has a lot of good stuff in it, including bug fixes, an upgrade to the Java Development Kit, upgrades to other key libraries, and removal of the legacy content view and the outdated RTE. Because of these changes, the 2019.4 release requires downtime. You will be receiving an email in the coming days that will also call out the downtime required for this release. Feel free to reach out with any questions that you might have!
Over three years ago, the content pages in JX were complete redesigned (you can read more about that here:Content deep dive). And then again a few months later, the rich text editor was also upgraded/redesigned (more about that here:RTE deep dive). When we rolled out those new features, we also added the ability for customers to toggle them on and off, in order to acclimate themselves and their user base with the new functionality. In the upcoming 2019.4 release,these feature toggles are going to be removed and all customers will automatically use the new content types and the new RTE. Nothing needs to happen on your behalf, it will happen automatically during the upgrade, but you can also toggle them on yourselves today (if you haven't already) to start getting used to a newly, modernized view of the content pages. Again, let us know if you have any questions or concerns about this!
Our Akamai transition has now been completed for all JX Cloud customers! One last bit of bookkeeping is to update DNS, so if you are a vanity cloud customer (meaning, your site's URL is something other than *.jiveon.com) then someone from Khoros will be reaching out to you to have your technical teams update the DNS for your domain to a new Akamai edgekey host. Let us know if you have any questions about this!
Final update for the Akamai transition (read more about that here: https😕/lithosphere.lithium.com/t5/JX-Blog/Lithium-JX-Akamai-Transition/ba-p/505620), all non-vanity customers are already live on Khoros' Akamai config. If you are a Cloud customer that has a vanity URL (meaning, your site's address ends in something other than .jiveon.com), Akamai is going to start transitioning your config from the Aurea/Jive one to the new Khoros one on Monday (March 12th). We we be transitioning instances over about a week and a half, so not everyone will be migrated on Monday. This will happen with no downtime and no anticipated impact. If you notice something that doesn't seem right, please let us know!
As a quick update to the Akamai transition (read more about that here: https://lithosphere.lithium.com/t5/JX-Blog/Lithium-JX-Akamai-Transition/ba-p/505620), we are at a state after much testing and preparing that we can finally start pulling the trigger for some Lithium-JX Cloud customers. If you are a Cloud customer that does not have a vanity URL (meaning, your site's address ends in .jiveon.com), Akamai is going to "flip the switch" and transition your Akamai config from the Aurea/Jive one to the new Lithium one on Monday. This will happen with no downtime and no anticipated impact. If you notice something that doesn't seem right, please let us know!
p.s. You may see (after upgrade) that your site is running on version "2018.13." This is due to a quirk in our release system, and both "2019.1" and "2018.13" refer to the same version of the L-JX software.
Hello everyone! It is with great pleasure that I can announce some new features that will be in the forthcoming Cloud release 2019.1.
Decline and Close Functionality:
The first of which surrounds the experience in the application when an end user clicks the "Decline" button on the cookie consent banner. Here is a screenshot of the new configuration for that:
You can now specify specialty text for a page that users get redirected to when they opt to Decline. When left with the default settings, the new page that a user gets redirected to will look like this:
Cookie Consent Statistics:
Starting after your site's upgrade to 2019.1, we will start tracking all the user clicks on the Cookie Consent banner. In the Admin Console, you will now be able to get statistics on what users are selecting in your site's banner:
There is also a button to download the statistics in a csv file.
Cookie Consent Banner Theming:
We have also added the cookie consent banner to the theming tool!
Let us know if you have any questions or feedback about any of this new functionality!
As part of the ongoing efforts to transition all hosting elements of Lithium-JX from Aurea ownership to Lithium ownership, we are currently working towards transitioning the ownership of the Akamai relationship for Lithium JX customers from Aurea to Lithium. I'm writing you all to give you a little information on what is going on and what to expect during this transition.
Currently, many things are happening behind the scenes to prep for the official cutover from an Aurea Akamai account to a Lithium Akamai account for all L-JX customers. However, the official "switch flip" is tentatively scheduled to take place in mid January. We will likely test our changes on demos and preview instances a week or two prior to the official cutover date.
What is needed from me?
For the majority of customers, no action will be needed to make this change. However, for a small number of customers, you may get a request to approve/validate a new certificate to be issued for your domain. This is required as we change some CNAME records during the transition. If you receive such a request, you will need to approve it promptly. Failure to do so could result in your LJ-X instance failing to load properly once we complete the transition. In addition to this, some customers will need to make some DNS changes, such as lowering the TTL ("time to live"), updating CNAME, and increasing the TTL. You will be contacted if these changes need to be made.
Let us know if you have any other questions about this or anything else!
On Friday, October 26th, our production cloud instances were all successfully upgraded to 2018.10. Afterwards, we noticed a couple issues that necessitated a hotfix release. We have been working on that the last two weeks, and just upgraded all preview and demo instances to the hotfix yesterday. Tomorrow we will be upgrading all production cloud instances to this hotfix (2018.10.0.1), with zero downtime. The release will include everything that was in 2018.10, plus the three extra fixes listed in the release notes here: https://lithosphere.lithium.com/t5/JX-Release-Notes/Lithium-JX-2018-10-Release-Notes/ba-p/498239. Let us know if you have any questions!