Sometimes after a database conversion (e.g. from MySQL to MariaDB) or due to encoding issues a situation might arise when WordPress is showing weird characters. A quick way of remedying the situation would involve examining the pages to discover a pattern (what characters are being substituted, in the example below the apostrophe was replaced by â€™) then running an queries against the database to reverse the effect. Here's a quick example (common tables that store content):
UPDATE wp_posts SET post_content = REPLACE(post_content, 'Â', '')
UPDATE wp_posts SET post_content = REPLACE(post_content, 'â€™', "'")
UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, 'Â', '')
UPDATE wp_postmeta SET meta_value = REPLACE(meta_value, 'â€™', "'")
Please, keep in mind that to permanently resolve the issue you would need to get to the root of the problem and may need to adjust encoding, run a database conversion, or install a sanitizing plugin.
Skype for Business (SfB) has a very, very strong potential, I have written about it in my previous post. I can't think of any other platform that shows as much promise in terms of bridging personal and business communications as well as unifying different modes and mediums. And all of this may have started with a strategic acquisition of Skype by Microsoft in 2011.
That said, the road ahead is not without challenges. For example, interoperability with other platforms. Making SfB work with existing Video TeleConferencing (VTC) systems, many of which represent significant capital investments in organizations' infrastructure, could be of a particular importance.
After reading statements like Skype for Business is based on Session Initiation Protocol (SIP) standards and supports H.264 (MPEG-4 video coding standard) one can come to a quick conclusion that integration and/or interoperability with other VTC solutions is easy or nearly automatic. Unfortunately, the industry is not quite there yet, and there are a few obstacles to overcome. The following is not a guide, but a few notes on potential challenges and prospective solutions:
Both H.323 and SIP protocols are industry standards and represent different approaches to voice and video signaling over IP networks; H.323 was originally established by International Telecommunications Union (ITU); SIP is the work of Internet Engineering Task Force (IETF). More details are available here
SfB is based on SIP, but it also extends the standard in ways that require a gateway to handle the translation of Microsoft SIP to other standards-based signaling protocols which support video, like H.323 or SIP. There are also potential issues with media codecs and transport protocols. Signaling and media gateways are used to resolve compatibility issues. More details are available here
Skype for Business Server 2015 (on-premises) now provides for the integration with certain third-party VTC system solutions via a new server role called Video Interop Server (VIS). However, the interoperability is limited, both in terms of the types of devices as well as functionality. More details are available here
Skype for Business (SfB), formerly known as Lync, has been steadily gaining in popularity. Partly, because of the robust set of features that has been implemented over the last few releases making the product truly Enterprise ready; partly, due to the rapid proliferation of Office 365, which includes SfB's cloud counterpart. With SfB and/or Skype client software available on a wide variety of hardware platforms (personal computers, tablets, mobile devices) and across multiple operating systems (Windows, Linux, iOS, Android) a possibility of establishing a ubiquitous multi-media communications platform seems firmly within reach. And best of all, when using SfB Online, without the need to invest into an expensive infrastructure. But wait, there's more! The cloud delivers on the promises of more innovation and continuous development cycle - Skype Meeting Broadcast, PSTN Conferencing, Cloud PBX with PSTN Calling are just a few examples. Read more at -