In order to execute shortcode inside a template, use the function do_shortcode('[my-shortcode-handle]'). Your shortcode needs to be registered as like normal (see WordPress codex on shortcode API) before you can use this in the template. Any attributes, inside content, etc. should be in there as well.

Before you move on to each of the aspects and how to comply with them, a security audit on your WordPress site should, in general, reveal how data is being processed and stored on your servers, and steps that are required to comply with the GDPR. The Security Audit Log plugin can help you perform a security audit on your website.

Some usual ways in which a standard WordPress site might collect user data:

Dynamics 365 Workflow Tools is a Community solution that expands Microsoft Dynamics 365 (CRM) Workflow features with lots of new posibilities. This helps you to build very advanced Codeless solutions in CRM.

By default, all methods in a zone are presented to the customer. If you have conditional free shipping and want it to be the only shown method if it’s available, you can use the following snippet to hide other methods:

The General Data Protection Regulation (GDPR) is a new EU regulation aimed at helping to strengthen data protection for EU citizens and residents both within the EU and the wider world. Essentially it says to businesses and organisations “If you want to offer your services or products to customers who are EU citizens, you better make sure you look after their personal data or else!”

One data protection regulation to rule them all

The GDPR is a single set of rules that apply to all EU member states with each member state designating a Supervisory Authority (SA) to oversee and ensure compliance of the legislation. SAs will work closely together by virtue of the cross-border nature of digital data.
What in the name of Sir Isaac H Newton happened here?
A significant part of the GDPR is about transparency and informing data subjects (individuals) about what and how their personal data is being used, by whom and for how long. GDPR requires data controllers to state what data is being processed and for what reasons. Additionally, they are required to inform data subjects about how long the data will be stored for. They must also state who the subject should contact with regards to any part of the data controller’s data processing actions.

The digital Age Of Consent

Provable consent must be explicitly given to the data processor by the data subject before their data can be processed. Additionally, the data must only be used for the purposes that consent has been given. EG if someone contacts you through your website with an enquiry of some kind, that does not give you permission to add them to your email marketing list. Verifiable consent must be given by a minor’s parent or guardian before their data can be used. Consent must be able to be withdrawn by the data subject at any time.

Pseudony-who in the what now?

The GDPR makes reference to something called pseudonimisation. Put simply, this is a process to transform data in a way that stops it from being attributed to a data subject (an individual) without the use of additional information. An example of this might be using a unique reference ID for someone rather than their name when storing their data in a database. A second table of names and corresponding IDs stored on a separate system would then be used to join the tables together and recreate the data. In this way if a data breach occurred and the personal data was stolen, the data wouldn’t expose actual names just the additional data.
For us here at Fellowship, this is the most ambiguous part of the GDPR as it relies (to a certain degree) on how you interpret pseudonimisation. An often mentioned example of pseudonimisation is encryption whereby data is held in an encrypted fashion and requires a key (stored separately) to decrypt it. Websites that use HTTPS send data over an encrypted connection so you could say that if your website has an SSL certificate you’re on your way to GDPR compliance but the data in the database itself is likely stored unencrypted so if the database was breached the personal data would still be exposed. No CMSs that we’ve ever used have stored personal data in a truly pseudonimous way. We wait to see how WordPress and the other major CMS players address this.

The General Data Protection Regulation, or GDPR, is coming into force in 2018. Ecommerce businesses and online stores will need to be prepared to adopt it before then.
In fact, any businesses taking online payments or handle consumer data need to be ready for GDPR adoption by the 25th of May 2018, when it officially comes into force.
The GDPR will be a huge change for ecommerce businesses, as by nature, any company taking orders online will be receiving a vast amount of data on a wide number of people. This means ecommerce businesses will need to be ready to implement some fairly big changes in order to comply.

The EU General Data Protection Regulation, or GDPR, is coming into action on 25 May 2018. GDPR will quickly become the new benchmark for UK business data handling and privacy laws, and across the EU.
The GDPR replaces the Data Protection Act that is currently in place, and has a much wider scope.
The aim of the GDPR is to extend the rights of individuals to their own data, and businesses handling such personal data must ensure it is secure. It gives individuals more control over their data, and outlines the regulations organisations must adhere to in order to protect it.

On this blog post I’ll walk through creating a Microsoft Flow flow for starting (and another for stopping) a set of Azure Resource Manager (ARM) VMs. Note that this is not my own original work. I implemented this based on the work of someone else I found online but can no longer find the original owner’s reference. If you do find this elsewhere please feel free to let me know in the comments.

As the official Markdown documentation states, Markdown does not provide any special syntax for tables. Instead it uses HTML <table> syntax. But there exist Markdown syntax extensions which provide additional syntax for creating simple tables.

Must sign in to both Microsoft Dynamics 365 and SharePoint to be able to view the document grid.

Only need to sign in to Dynamics 365.

List component

Must download list component and upload directly to SharePoint site before connecting site to Dynamics 365.

No list component required.

Support lifecycle

This approach relies on the sandboxed solutions functionality on SharePoint. SharePoint plans to deprecate this functionality. If the sandboxed functionality isn’t available for a SharePoint site, this integration won’t work.

This approach relies on server-to-server authentication and won’t be affected by the deprecation of the sandboxed solutions functionality in SharePoint.

Does not include the SharePoint commands listed in the client-based integration column.

Custom content types

Can create new custom content types.

Can’t create new custom content types.

Previously created custom content types can still be viewed and edited but to create a new custom content type you’ll need to create it directly in SharePoint using Open SharePoint.

Absolute URLs

Supported

Unsupported

Users moving from the client-based approach to the server-based approach need to convert their absolute URLs to relative URLs. This will only work if the absolute URL provided is in a SharePoint site valid for server-based SharePoint integration.

Folder navigation

Users can create SharePoint folders while in Dynamics 365. Folders are displayed in a grid that users can navigate through.

All documents under subfolders are displayed in the Dynamics 365 grid. Relative URLs are displayed to show users where the document is located relative to the parent folder. SharePoint document views can be customized so users see only documents in a specific folder or subfolder.

Resource Throttling

Doesn’t apply.

A document library with 5000 or more documents might experience resource throttling.

If you have more than 5000 documents in your document library, you can view the documents in the default grid view. However, if you sort on columns other than the default sorted column, you might see an error indicating that the throttling limit has been exceeded. This resource throttling can affect other features. For example, Microsoft OneNote integration will not work when the SharePoint Server site has 5000 or more documents.

Anyone who is taking their online security and privacy seriously, will use a VPN – a Virtual Private Network. A VPN encrypts all user’s Internet data into a secure tunnel and creates a secure connection between one’s device and a VPN server. All the information traveling between the user’s Internet-enabled device and the secure server remains invisible to any third party. Those who want a guaranteed protection, will be disappointed that not all VPNs accept bitcoin as method of payment – but there are a few that do.

You can use any tool available to create a self-signed certificate as long as they adhere to these settings:
• An X.509 certificate.
• Contains a private key.
• Created for key exchange (.pfx file).
• Subject name must match the domain used to access the cloud service.
You cannot acquire an SSL certificate for the cloudapp.net (or for any Azure-related) domain; the certificate's subject name must match the custom domain name used to access your application. For example, contoso.net, not contoso.cloudapp.net.
• Minimum of 2048-bit encryption.
• Service Certificate Only: Client-side certificate must reside in the Personal certificate store.
There are two easy ways to create a certificate on Windows, with the makecert.exe utility, or IIS.

Makecert.exe

This utility has been deprecated and is no longer documented here. For more information, see this MSDN article.

PowerShell

PowerShell$cert = New-SelfSignedCertificate -DnsName yourdomain.cloudapp.net -CertStoreLocation "cert:\LocalMachine\My" $password = ConvertTo-SecureString -String "your-password" -Force -AsPlainText Export-PfxCertificate -Cert $cert -FilePath ".\my-cert-file.pfx" -Password $password
Note
If you want to use the certificate with an IP address instead of a domain, use the IP address in the -DnsName parameter.
If you want to use this certificate with the management portal, export it to a .cer file:
PowerShell
Export-Certificate -Type CERT -Cert $cert -FilePath .\my-cert-file.cer

Internet Information Services (IIS)

There are many pages on the internet that cover how to do this with IIS. Here is a great one I found that I think explains it well.

General Information
• When operating in a FIPS-approved mode, PKI key/certificates must be between 1024- bits and 4096-bits, inclusive.
• The supported cipher combinations allowed for SSL negotiation are limited to:
○ SSLv3/TLSv1 - RSA Key Exchange, RSA Authentication, 256 bit AES encryption, and SHA1 HMAC
○ SSLv3/TLSv1 - RSA Key Exchange, RSA Authentication, 168 bit 3DES encryption, and SHA1 HMAC
○ SSLv3/TLSv1 - RSA Key Exchange, RSA Authentication, 128 bit AES encryption, and SHA1 HMAC
Each of the above combinations uses RSA key exchange; therefore, RSA based key/certificates must be used.
• In FIPS Mode, the private key must use the PKCS#8 format and PKCS#12 compatible encryption of the private key, which allows the use of the necessary strong encryption algorithm of 3DES encryption and SHA1 hashing.
• Note that traditional PEM encoded encrypted private key files will typically start with the line:
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
Procedure
These instructions assume you have downloaded and installed the Windows binary distribution of OpenSSL. Refer to Using OpenSSL for the general instructions
The private key you want to convert must already be an RSA private key and be between 1024 and 4096 bits in length, inclusive. It is only possible to convert the storage format for the private key. Changing the type of key and its length is not possible and requires generation of a new private key.