In what has become a nearly annual tradition, WordPress has released yet another update that broke thousands of plugins across the Internet. As usual, they claim this is in the best interest of security. Thus the breaking change was done with ZERO notification to developers. It was also forced onto most sites as a “security patch release” which will update any site that does not forcibly stop automatic updates.
Communication From WordPress Core Is Horrid
While I don’t have an issue with breaking changes for true security issues, what IS a problem is pushing out a change with almost ZERO testing to millions of websites with ZERO communication. They gave absolutely no warning to thousands of sites that this “update version” was coming and that it would knowingly break things. They did not communicate to site owners so they could block updates. They did not communicate to plugin or theme developers so they could come up with new releases.
A quick intro to Vue. If you are a jQuery fan I highly recommend looking into adding Vue to your developer toolbox.
This is not an in-depth article — have too much going on these days for that. It is a more a short-hand techie crib sheet of how I got a deployment repo to auto-pull the latest changes to its develop branch over to my staging server automatically. This is pulling down a fully software environment to a directory on the server.
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.