Microsoft Teams is a mixed blessing. Like most Microsoft products it starts off with a great idea, does some of it exceptionally well and the rest of it is half-baked. Microsoft Teams Wiki Export is a perfect example. There is no readily-apparent and easy way to get your data OUT of a Wiki page you’ve created in Teams. It is stuck there forever with no way to Print, Archive, or Export the content.
This is a typical Microsoft maneuver designed to generate disdain for non-Microsoft-centric tools and boost vendor lock-in. But there is a usable, if completely convoluted, workaround. It turns out that most of these Teams-based Wiki pages that you added to your Teams tabs because it seemed like the “simple and easy” solution can be retrieved. They happen to end up in Sharepoint. Just make sure you remember the very first original name you gave the tab because any renaming of tabs is done with magical pixie dust sprinkled on a circle of leprechauns all playing the telephone game. If you have more than a few Wiki pages good luck guessing which one is the one you want if the name does not match.
Here is how I found the “magical mystery file” using the browser-based version of Microsoft Teams:
A recent Seeking Alpha article proposes the theory that Alibaba could threaten Amazon’s AWS cloud services.
Amazon has been my best investment by far.
The article has some great information about the cloud services industry. It includes a lot of facts and figures that ring true. I disagree with this article’s overall assessment, however.
Alibaba will erode AWS market share in Asia but few other regions. They are a Chinese company. I would never use them myself nor recommend the Alibaba cloud solution to my clients because of this.
China has a history of banning content and restricting the free flow of information — especially on the Internet. Shutting down a business on the Alibaba cloud and taking over the assets of anything they deem “inappropriate” or “propaganda” is well within the realm of possibility. Why would any business add that to their risk factors when you have AWS as an alternative.
Not too mention Amazon continues to innovate and introduce services at a dizzying pace. The dollars spent on investment only matters if it yields results. Based on the service offerings alone, Amazon is 10 times further ahead in this space than the closest competitor.
I’m maintaining a hold position on AMZN despite the growing popularity of Azure, Google Cloud, and Alibaba.
Vue is running on several projects to create a better admin user experience. Vuetify is layered on top and baked into WordPress themes and plugins.
You will need to add a little custom CSS to stop WordPress from stomping on the UX. You’ll also add a small localize script to seed Vue with relevant data from WordPress. A little REST applet to serve Vue requests and you get a fast good looking responsive app with far less effort than custom code, WordPress skeleton apps, React, or Angular.
Vue + Vuetify is my new go-to tool for plugins and themes. I am happier with my choice knowing that was created and is supported by small independent developers.
Get Your Certificate Signing Request (CSR)
From Amazon Linux:
cd /etc/ssl openssl req -new -key vim <domain>.<tld>.key -out <domain>.<tld>.csr
Buy Your Certificate
From Name.com purchase a cert for either a wildcard or single-host fully-qualified domain name. It must match the domain identifier . used when creating your CSR.
You’ll need the contents of the .csr file and private key you created above.
I am completely baffled by this one and hope one of my techie friends can help.
I’m using a PHP class with magic methods to set and get the properties of that class. The idea is to use private properties in the class so that the PHP magic methods can take over and determine whether to update a WordPress user meta entry, blog entry, or standard option based on which proper of the class is being retrieved or stored.