| <?php | |
| function fs_sc_location_seo_iconbox( $atts ){ | |
| // begin output buffering | |
| ob_start(); | |
| global $post; // if outside the loop | |
| $slug_to_check = 'seo'; | |
| Prefix | Description | Notes | |
|---|---|---|---|
| ac_ | Platform Client ID | Identifier for an auth code/client id. | |
| acct_ | Account ID | Identifier for an Account object. | |
| aliacc_ | Alipay Account ID | Identifier for an Alipay account. | |
| ba_ | Bank Account ID | Identifier for a Bank Account object. | |
| btok_ | Bank Token ID | Identifier for a Bank Token object. | |
| card_ | Card ID | Identifier for a Card object. | |
| cbtxn_ | Customer Balance Transaction ID | Identifier for a Customer Balance Transaction object. | |
| ch_ | Charge ID | Identifier for a Charge object. | |
| cn_ | Credit Note ID | Identifier for a Credit Note object. |
My main development workstation is a Windows 10 machine, so we'll approach this from that viewpoint.
Recently, Google Chrome started giving me a warning when I open a site that uses https and self-signed certificate on my local development machine due to some SSL certificate issues like the one below:
This is a local copy of the commands from:
This guide serves as a reference of collected information necessary for strict management of PGP keys. This includes keeping a master key that always remains
| <?php | |
| mb_internal_encoding("UTF-8"); | |
| $desc = <<<TEXT | |
| <p>Lines of text SHOULD NOT be longer than 75 octets, (och hör på den) excluding the line break. Long content lines SHOULD be split into a multiple line representations using a line "folding" technique.</p> | |
| That is, a long line can be split between any two characters by inserting a CRLF | |
| immediately followed by a single linear white space character (i.e., | |
| SPACE, <b>US-ASCII</b> decimal 32 or HTAB, US-ASCII decimal 9). Any sequence | |
| of CRLF followed immediately by a single linear white space character | |
| is ignored (i.e., removed) when processing the content type. |
