## Array Rotation in PHP

An operation to rotate an array will shift each element to the left. We can perform this function X number of times depending on the input parameters. Since the lowest index element moves to the highest index upon rotation, this is called a circular array.

All we need to do is remove the first element of the array, save it in a variable, and then attach it to the end of the array. This can be done inside of a loop that iterates the number of times that we want to rotate the data. The function can take in the original array and the number of rotations. It returns the newly rotated array:

```function rotateLeft(\$array, \$rotations) {
for(\$i=0;\$i<\$rotations;\$i++){
\$firstElement = array_shift(\$array);
array_push(\$array, \$firstElement);
}
return \$array;
}
```

Although this code will work, and gets the job done, it is slow. When I tried this as a solution on HackRank (a code challenge website) it passed 9/10 test cases. It failed once, citing “time limit exceeded”.

The problem is with array_shift. It’s a PHP function that removes “the first value of an array off and returns it.” This shortens the array by a single element, moving everything else down one index. The algorithmic efficiency (expressed in Big-O notation) of array_shift() is O(n). That means, the larger the input array, the more time it will take to complete.

Next, I tried using array_reverse and array_pop. I figured that since array_pop() has a constant algorithmic efficiency, noted as O(1), it would help. Regardless of the size of the input, it would always take the same amount of time.  But, due to the use of array_reverse (twice!) it was even slower:

```function rotateLeft(\$array, \$rotations) {
for(\$i=0;\$i<\$rotations;\$i++){
\$array = array_reverse(\$array);
\$firstElement = array_pop(\$array);
\$array = array_reverse(\$array);
array_push(\$array, \$firstElement);
}
return \$array;
}
```

Finally, I found a solution that was performant:

```function rotLeft(\$array, \$rotations) {
\$remaining = array_slice(\$array, \$rotations);
array_splice(\$array, \$rotations);
return array_merge(\$remaining, \$array);
}
```

This code does not need to use any kind of loop, which helps to speed things up. First, array_slice() grabs the elements up to the point that the data should be rotated, and saves them to the variable \$remaining. Next, array_splice() removes those same elements. Lastly, array_merge() glues the elements back together in the expected, rotated order.

This sort of computer science programming challenge can commonly be found during software engineering job interviews. When coming up with an answer, it is important to consider speed and performance. Understanding computing cost-effectiveness and Big-O can be a deciding factor in how your coding skills are judged.

## Look-and-Say in PHP

The look-and-say sequence is a series of integers. It can grow indefinitely. It is generated by reciting a number phonetically, and writing what you spoke numerically. Its popularity is attributed to famed cryptographer Robert Morris. It was introduced by mathematician John Conway. It looks like this:

```1
11
21
1211
111221
312211
13112221
```

The first line would be pronounced as “one 1”, and then written as “11” on the second line. That record would be spoken as “two 1’s”,  giving us the third line “21”. The greatest individual symbol you’ll ever find in this consecution is a 3.

This topic has lots of trivia, variations, and history that could be dug up and expounded upon. Here, I’ll explain a solution written in PHP to produce this chain of numerals. The input will be the count of how many lines, or iterations, in the series to generate. Below is the code:

```<?php

echo "Count And Say: \n";

function countAndSay(\$count=0){
\$value = 1; // initial seed
for(\$i=1;\$i<=\$count;\$i++){
echo \$value . "\n";
\$value = calcOutput(\$value);
}
}
function calcOutput(\$value){
\$value = "\$value";  // change it into a string, so we can iterate over each character
\$current = \$value[0]; // first character
\$count = 1;
\$return = '';
for (\$i = 1; \$i <= strlen(\$value); \$i++) { // keep going until we get through the whole string
if (\$current != \$value[\$i] || \$i == strlen(\$value)) { // found a different character, or end of the input string
\$return .= "\$count\$current";
\$count = 1; // reset count
\$current = \$value[\$i]; // set new current character
} else {
\$count++;
}
}
return \$return;
}

countAndSay(7);

echo "\n\n";

?>
```

I separated my code into two functions. I think this is the best approach. As an exercise, see if you can figure out how to refactor it into one. This could help you to internalize the logic as you write it out for yourself.

The initial seed value is “1”, and that is hard-coded at the top. The for-loop iterates based on the count input parameter. That means the code circles back and re-runs, with updated values, until its internal count (represented by the variable \$i ) matches the \$count variable passed into countAndSay(\$count).

The code that we loop over outputs the current sequence value (starting with 1) as its own line (“\n” will output a new line in most programming languages) , and then calculates the next. The function that determines the next line of output, calcOutput(\$value), takes the current value as an argument.

The first thing we do is cast the integer value passed along into a string. This lets us refer to each character by index – starting at zero – and save it to a variable \$current. We start a new \$count, to keep track of how many times we see the same digit.

The next for-loop executes for the length of the \$value string. On each loop, we check if the \$current character we saved matches the subsequent one in that \$value string. It is again referenced by index, this time based on the for-loop’s iteration count represented by the variable \$i.

If it does match, one is added to the \$count variable that is keeping track of how many times we see the same character is a row. If it doesn’t match (or we’ve reached the end of the input), the \$count and \$current number are concatenated to the \$return element. At that point, the \$count is reset to 1, and the \$current value is updated.

Writing an algorithm to generate the look-and-say (also known as, count-and-say) sequence is a common coding puzzle. You might run into it during a job interview as a software engineer. As practice, see if you can simplify my example code, or even write it in a different programming language than PHP.

## CSS for Weighted Hyperlink Decoration

How to add an underline to website text should be covered in any intro to web development course. The old-fashioned HTML way uses a now-deprecated tag:

`<u>This will appear underlined!</u>`

Modern approaches use CSS to define such a style:

`<p style="text-decoration: underline;">This will appear underlined!</p>`

Even better, properly written code will separate the inline styles, like so:

```<style>
.underlined-text{
text-decoration: underline;
}
</style>
<p class="underlined-text">This will appear underlined!</p>```

For hyperlink text, I might want to hide the underline when a user mouses over it. That’s easy with the “hover” pseudo-class:

```<style>
text-decoration: underline;
}
text-decoration: none;
}
</style>
```

But, suppose I want to have that underline to become thicker instead of disappearing. That will require an advanced, super-secret CSS technique. To make it work, we will utilize box-shadow.

In the world of cascading style sheets, the box-shadow property adds a shadow effect around any HTML element. The shadow is described by its offsets, relative to the element. Leveraging this, we can create a shadow that looks like an underline. On hover, we can adjust the settings to change its appearance:

```<style>
text-decoration: none;
box-shadow: inset 0 -1px 0 rgb(15 15 15);
}
-webkit-box-shadow: inset 0 0 0 rgb(0 0 0 / 0%), 0 3px 0 rgb(0 0 0);
box-shadow: inset 0 0 0 rgb(0 0 0 / 0%), 0 3px 0 rgb(0 0 0);
}
</style>
```

Point your cursor over any of the hyperlinks in this post to see what it looks like. Experiment with the above code to make it your own.

## 7 tips for writing as a practice

Writing is the best way to develop new ideas. It exercises our ability to explain what we mean, what we want, and why. Clear writing is clear thinking.

Putting words down is good for our mind, and is calisthenics for the brain. Forcing ourselves to build coherent, connecting streams of thought flexes mental muscles that we usually ignore. Expression and mutation are two sides of the same coin.

It’s easy to state your opinions at a high level. But once you dig into it, you might realize you haven’t thought it through. At least, not recently. Writing adds flesh to otherwise gaunt stances. It turns shape-shifting clouds into crystals with obvious foundations.

Make it a habit. Turn it into a daily practice. Here are ten tips to develop a writing routine:

1. Spend time writing fiction. Short stories, character profiles, fantasy, and fan-fiction each count. Glue yourself to the keyboard, until you can say “That’s my story, and I’m sticking to it.”
2. Journal daily. Type out the things for which you have gratitude. Document your feelings. Spell out your hopes. Cast a silent incantation. Craft an ancient curse. The universe is listening. I wrote a blog post about journaling, you can read it here.
3. Don’t be a perfectionist. Put sentences down, even if you don’t like them. Keep them around, even if you hate them. But please remember, that doesn’t apply to people in your life.
4. Everything is a work-in-progress. Revisit your posts, essays and articles. Add that literary polish and be a wordsmith. This will help keep you from trying to be perfect.
5. Start a blog. Build in public. Let the world see how you think. Most people aren’t paying attention anyway. And if you can’t come up with something new, update existing pieces.
6. Editing counts. Delete unnecessary sentences. Remove unneeded words. Clarify things, find synonyms, and avoid using the word “really”.
1. When I edit, I never actually throw anything away. I borrow the “soft delete” methodology from software engineering.  I flag writing as unusable, without actually getting rid of it. That way I can revisit it, use it for subsequent ideas, and remember where my mind was.
7. Hoard notes. Keep a physical notebook. Use a note-taking app. Bookmark stuff. Markup books while you’re reading them. Keep a stack of index cards near by for when inspiration strikes
8. Write more than you promised yourself you would, but only if you feel like it.

## The Great Resignation

The Great Resignation is an early 2020s buzz phrase. It describes a large portion of the workforce quitting. This Big Quit has been precipitated by numerous factors, but most obviously the CoVid-19 pandemic. Truthfully, the snowball started rolling prior to the worldwide shutdown. Online freelancing and digital nomadism have been picking up steam for nearly a decade. Ubiquitous Wi-Fi, inexpensive devices, and on-demand cloud computing paved the road of the Extraordinary Exodus. The ability to work remotely, I believe, is one of the strongest drivers of this cultural shift.

Employment as we know it is a raw deal. It exploits workers and business owners. Only since the advent of the industrial revolution has the modern work schedule and environment taken this shape.

Employees are tasked to toil in serfdom. The employer is expected to be a parent. Those costs, risks, and responsibilities weigh heavily on executive shoulders. And that gravity ultimately crushes workers as exploitation.

Employer sponsored medicine took hold after World War 2. To fight inflation, the 1942 Stabilization Act was passed. That law prevented employers’ from raising wages. As a work-around to compete for high-demand workers, companies began offering health benefits as a competitive incentive. Nearly a century later, healthcare and employment are intertwined in the bleakest of scenarios.

Now can be the epoch of freedom. It’s the original promise of all the technological advances we now enjoy. Greater prosperity, with fewer shackles to hold us down. That also means businesses can enjoy larger output with less overhead.

When writing this, I was careful not to refer to employers as bosses. Ultimately, they are the clients. Workers should be expected to “manage up”, as they control labor, and in turn, production output and capital income.

It’s an absurd burden that businesses are expected to provide employees with healthcare. With that type of expectation, employers feel justified squeezing out every last drop of labor juice – be it sweat or tears.

Even worse, as workers, it’s crazy that access to medicine is tied to employment. Public health should be a public service, paid for by taxes. And, I’m not suggesting that taxes should be raised, but instead reallocated from bureaucratic waste, corruption, and cruelty.

Healthcare is among numerous benefits subsidized and off-loaded to the private sector. It has a taste similar to the Western tipping scheme found in the restaurant service industry.

## Freedom

Nine hours in an office each day doesn’t leave time for much else. It was a routine I faced for years, along with many other New York straphangers. A long daily commute was the little time I could find to read, meditate, or relax. My only exercise came from pushing deadlines, jumping through hoops, and squeezing in meetings.

An age of abundance is possible within our lifetime. Laborers are being replaced by technology. Remember, most jobs are bullshit anyway. Humanity can feed itself, and anything more is just pollution.

## Freelance

A freelance side hustle is the first step in buying your freedom. Owning, and running, your own remote business comes pretty close to what I imagine as the Digital Dream. When working as a freelance web developer I follow a process to ensure success. I am able to pitch potential clients on improvements, audits, and maintenance agreements.

## Restoring a website when EC2 fails

Recently, one of my websites went down. After noticing, I checked my EC2 dashboard and saw the instance stopped. AWS had emailed me to say that due to a physical hardware issue, it was terminated. When an instance is terminated, all of its data is lost. Luckily, all of my data is backed up automatically every night.

Since I don’t use RDS, I have to manually manage data redundancy. After a few disasters, I came up with a solution to handle it. I trigger a nightly cron-job to run a shell script. That script takes a MySQL dump and uploads it to S3.

As long as I have the user generated data, everything else is replaceable.  The website that went down is a fitness tracking app. Every day users record their martial arts progress. Below are the ten steps taken to bring everything back up.

1. Launch a new EC2 instance
2. Configure the security group for that instance –  I can just use the existing one
4. Secure the database
5. Install PhpMyAdmin – I use this tool to import the .sql file in the next step
6. Import the database backup – I downloaded the nightly .sql file dump from my S3 repo
7. Setup automatic backups, again
8. Install WordPress and restore the site’s blog
9. Configure Route 53 (domain name) and SSL (https) – make the website live again
10. Quality Assurance – “smoke test” everything to make sure it all looks correct

Use this as a checklist to make sure you don’t forget any steps. Read through the blog posts that I hyperlinked to get more details.

## Shopify App with Theme App Extensions

After writing my last post about How to create a Shopify app, I decided to build a new one as a side project. Taking myself through the entire process helped me to tighten up the details I mentioned. This one adds a sticky banner to a store’s front-end, prompting users to “click to call”.

It’s built on top of the code I used for the SplitWit Shopify app. I adjusted some of the methods to accept configuration parameters to differentiate between the two. Code had to be added to support new functionality. SplitWit already had a feature to add a sticky banner to a site’s existing UI. I used the same workflow to inject the merchant’s settings as JavaScript.

```function writeSnippetFile(\$shopify_installation_complete_id){

\$conn = \$this->connection;
\$sql = "SELECT * FROM `prompts` WHERE shopify_installation_complete_id = ?";
\$result = \$conn->prepare(\$sql);
\$result->execute(array(\$shopify_installation_complete_id));
\$row = \$result->fetch(PDO::FETCH_ASSOC);
\$phone_number = \$row['phone_number'];
\$message_text = \$row['message_text'];
\$color = \$row['color'];
\$bg_color = \$row['bg_color'];
\$position = \$row['position'];
\$display = \$row['display'];
\$mobile_only = \$row['mobile_only'];
\$filename = \$row['snippet'];

\$sticky_html = "";

if(\$display == "hide"){
\$sticky_html .= "<style>#ctc-splitwit-sticky{display:none;}</style>";
}

if(\$mobile_only == "true"){
\$sticky_html .= "<style>@media(min-width: 1000px){#ctc-splitwit-sticky{display:none;}}</style>";
}

\$sticky_html .= "<div style='font-weight:bold;".\$position.":0;position:fixed;z-index:100000;left:0px;text-align:center;padding:8px 20px;width:100%;background:".\$bg_color.";color:".\$color."' id='ctc-splitwit-sticky'><p style='margin:0px'><a href='tel:".\$phone_number."'>".\$message_text."</a></p></div>";

\$changecode = '\$("body").append("'.\$sticky_html.'")';

\$snippet_template = file_get_contents("/var/www/html/click-to-call/snippet/snippet-template.js");
\$myfile = fopen("/var/www/html/click-to-call/snippet/".\$filename, "w") or die("Unable to open file!");

\$txt = "window.CTCsplitWitChangeCode = ".\$changecode . "\n" . \$snippet_template;

fwrite(\$myfile, \$txt) or die("Unable to save file!");

fclose(\$myfile);
}
```

The app’s admin view is a simple input form with settings to control the sticky bar UI that is injected into the merchant’s store-front.

In addition to updating and refactoring my code, I wrote copy and drafted design for this digital product. I used SplitWit branding guidelines (fonts, colors, etc.) to establish an adjacent feel.

Although it’s optional, I wanted to include a promo video in the listing. Having had previously created videos for SplitWit, I was able to quickly spin one together. I already created background music files in Garage Band for other projects. Here’s the one I chose to use – feel free to borrow it for what ever you like. The text animations were exported from Keynote. I added screenshots, included stock animation from VideoPlasty, and recorded voice-over lines using a Yeti microphone.

I drafted other graphic assets that were required in the app listing using the GIMP – software I’ve used for over twenty years

A few days after submission, I received an email with required changes.

They were mostly minor issues. Things like the app’s name, a screenshot used in the listing, and an OAuth redirect bug.

One of the requests said, “Update your app to theme app extensions to ensure compatibility with Online Store 2.0 themes.”

### 2.0 themes? What does that mean?

Shopify recently announced Online Store 2.0 (OS 2.0). It’s essentially a set of improvements to the platform that makes themes and apps more flexible and maintainable. This benefits both merchants and developers. Enhanced app support means app functionality can be leveraged anywhere in a theme by using app blocks in the theme customizer.

SplitWit Click-to-Call injects HTML to manipulate a store’s user interface. That code comes from a JavaScript file that’s referenced in the page’s source code. That reference is added upon installation using the ScriptTag API. The JS file itself is generated & updated whenever a merchant clicks “save” in the app’s admin view. This required change is requesting that we provide an app block option as an alternative for compatible themes.

Shopify is encouraging OS 2.0 apps to instead use “theme app extensions” because they don’t edit theme code. It allows merchants to add your app’s UI elements, along with any settings, through its theme editor.

The documentation mentions that it “reduce[s] the effort required to integrate apps in themes”. In my particular case, it actually seems to add a step.

## Theme App Extensions

App blocks are a type of “theme app extension” supported by Shopify’s Online Store 2.0. To create an app block available in the theme editor, I added a directory to my app using the below file structure. I was able to auto-generate it with the Shopify CLI by using the command shopify extension create.

From the command line, I registered this folder as an extension, and pushed my code.

In my app block .liquid file I used the same HTML template from my original PHP snippet, swapping my database variables for Shopify block settings.

```{% if block.settings.display == "hide" %}
<style>#ctc-splitwit-sticky{display:none;}</style>
{% endif %}

{% if block.settings.mobile_only == "yes" %}
<style>@media(min-width: 1000px){#ctc-splitwit-sticky{display:none;}}</style>
{% endif %}

<div style="font-weight:bold;{{block.settings.position}}:0;position:fixed;z-index:100000;left:0px;text-align:center;padding:8px;width:100%;background:{{block.settings.bg_color}};color:{{block.settings.color}}" id="ctc-splitwit-sticky"><p style=margin:0px><a style="color:{{block.settings.color}} " href="tel:{{block.settings.phone_number}}">{{block.settings.message_text}}</a></p></div>

{% schema %}
{
"name": "Click To Call",
"target": "section",
"settings": [
{
"type": "color",
"id": "bg_color",
"label": "Banner color",
"default": "#0000FF"
},
{
"type": "color",
"id": "color",
"label": "Text color",
"default": "#FFFFFF"
},
{
"type": "text",
"id": "message_text",
"label": "Message text",
"default": "Call us now!"
},
{
"type": "text",
"id": "phone_number",
"label": "Phone number",
"default": "(212)-555-5555"
},
{
"id": "position",
"label": "Position",
"options": [
{
"value": "top",
"label": "Top"
},
{
"value": "bottom",
"label": "Bottom"
}
],
"default": "top"
},
{
"id": "display",
"label": "Display",
"options": [
{
"value": "hide",
"label": "Hide"
},
{
"value": "show",
"label": "Show"
}
],
"default": "show"
},
{
"id": "mobile_only",
"label": "Mobile only",
"options": [
{
"value": "yes",
"label": "Yes"
},
{
"value": "no",
"label": "No"
}
],
"default": "no"
}
]
}
{% endschema %}
```

The schema JSON explicates the settings inputs exposed to the merchant. I set them to match the original settings view from my app’s interface.

This approach lets Shopify maintain the app’s configurations, instead of my SplitWit server database that’s hosted on AWS EC2. That’s less data developers can capture, but also less of a hosting burden.

Any time you update the theme app extension you’ll need to re-push the code from the Shopify CLI with the command shopify extension push. The extension code is not hosted on your own server. It lives solely in the Shopify infrastructure ecosystem.

### Verify theme support

Not all themes support theme app extensions. Theme support needs to be verified at the time of installation.

The original settings view is still needed, just in case the merchant’s published theme does not support app blocks. If app blocks are supported, I don’t install the script tag snippet at all. Instead, the settings view is replaced with integration instructions telling the merchant how to activate the sticky banner from the theme editor.

If app blocks are not supported by the active theme, the snippet is installed and the settings input form displayed. Determining if the merchant’s theme supports app blocks requires adding the read_themes Shopify API scope access to the oAuth request.

```\$scopes = "write_script_tags,read_themes";
\$redirect_url = "https://".\$shop."/admin/oauth/authorize?client_id=". \$this->api_key ."&scope=".\$scopes."&redirect_uri=". \$redirect_uri ."&state=".\$nonce . "&grant_options[]=per-user";
```

I tested my code by switching from the basic “Minimalist” theme to a OS2.0 theme called “Dawn”. When the app is being installed, I do a few things to check if app blocks are supported:

1. Get a list of the merchant’s installed themes, and check which is currently published
2. Retrieve a list of assets in the published theme
3. Check if JSON template files exist for at least one of the desired templates
```\$params = [];
\$json_string_params = json_encode(\$params);
'X-Shopify-Access-Token:' . \$access_token,
'content-type: application/json'
);

// \$install_ctc_curl_response_json = \$this->curlApiUrl("https://www.splitwit.com/service-layer/click-to-call-service.php?method=installShopifyApp&installation_complete_id=".\$installation_complete_id, \$params);

// check if this merchant's published theme supports app blocks
\$read_themes_url = "https://" . \$this->api_key . ":" . \$this->secret . "@" . \$shop . "/admin/api/2021-10/themes.json"; // list of all installed themes
\$published_theme_id = 0;
foreach (\$themes as \$theme) {
// live theme has a role of main
if(\$theme['role'] == "main"){
\$published_theme_id = \$theme['id'];
// echo "The main theme is " . \$theme['name'] . "<br /><br /><br />";
}
}

// Retrieve a list of assets in the published theme
\$get_theme_assets_url = "https://" . \$this->api_key . ":" . \$this->secret . "@" . \$shop . "/admin/api/2021-10/themes/".\$published_theme_id."/assets.json";
\$get_theme_assets_curl_response_json = \$this->curlApiUrl(\$get_theme_assets_url, \$json_string_params, \$headers, false);

// Check if JSON template files exist for at least one of the desired templates
// For other applications, you might want to check that they exist for ALL desired templates
\$assets = \$get_theme_assets_curl_response_json['assets'];
\$probably_block_support = false;
\$templates = ['index', 'cart', 'page.contact', 'product', 'collection'];

foreach (\$assets as \$asset) {
foreach (\$templates as \$template) {
if(\$asset['key'] == "templates/".\$template.".json" ){
\$probably_block_support = true;
break; // this checks that JSON template files exist for at least one of the desired templates. If you want to check that they exist for ALL desired templates, you can move this break to the 'else' condition
}else{
\$probably_block_support = false;
// break;
}
}

if(\$probably_block_support){
break;
}
}
```

1. The body of JSON templates to determine what section is set as `main`
2. The content of each `main` section and if it has a schema that contains a block of type ‘@app’

```<?php
// we can continue further checks here
// https://shopify.dev/apps/online-store/verify-support

if(\$probably_block_support){

foreach (\$templates as \$template) {
\$get_single_asset_url = "https://" . \$this->api_key . ":" . \$this->secret . "@" . \$shop . "/admin/api/2021-10/themes/".\$published_theme_id."/assets.json?asset[key]=templates/".\$template.".json";

\$get_single_asset_curl_response_json = \$this->curlApiUrl(\$get_single_asset_url, \$json_string_params, \$headers, false);
// var_dump(\$get_single_asset_curl_response_json['asset']['value']);
\$asset_value_json = json_decode(\$get_single_asset_curl_response_json['asset']['value']);
var_dump(\$asset_value_json->sections);
echo "<hr />";
// break;
}
}
```

From my testing, those last two steps were not reliable and ultimately irrelevant.

If app blocks are supported, the snippet is not created nor injected through the Shopify script_tag API. I make note of it in the database.

```\$timestamp = time();
\$snippet = md5(\$timestamp);
\$snippet = \$snippet . ".js";
\$using_app_blocks = 0;

// don't create the snippet if we think they have app block support
if (\$probably_block_support) {
\$using_app_blocks = 1;

}else{

// create snippet file
\$myfile = fopen("/var/www/html/click-to-call/snippet/".\$snippet, "w");
fclose(\$myfile);

// inject JS snippet into site
\$create_script_tag_url = "https://" . \$this->api_key . ":" . \$this->secret . "@" . \$shop . "/admin/api/2020-04/script_tags.json";
\$params = [
'script_tag' => [
'src' => 'https://www.splitwit.com/click-to-call/snippet/' . \$snippet
]
];
\$json_string_params = json_encode(\$params);
}

\$stmt = \$conn->prepare("INSERT INTO `prompts` (shopify_installation_complete_id, snippet, shop, using_app_blocks, access_token) VALUES (:shopify_installation_complete_id, :snippet, :shop, :using_app_blocks, :access_token)");
\$stmt->bindParam(':shopify_installation_complete_id', \$installation_complete_id);
\$stmt->bindParam(':snippet', \$snippet);
\$stmt->bindParam(':shop', \$shop);
\$stmt->bindParam(':using_app_blocks', \$using_app_blocks);
\$stmt->bindParam(':access_token', \$access_token);
\$stmt->execute();
```

I check for that value from the front-end to display steps for integrating the app block from the theme customizer. Shopify guidelines require that we provide merchants with post-installation onboarding instructions. Those directions replace the settings input form. Configurations will be managed through the block itself.

Although Shopify does provide recommendations for merchant onboarding, there is no boiler-plate copy. A basic explanation, with screenshots, sufficed.

These updates satisfied the app review team’s request. I responded to their email, and a day later received their reply. It complained that the “app doesn’t have a functional user interface (UI)” when app blocks are enabled. That was because all of the settings were being managed by the app block data. To solve this issue, I moved the phone number and message fields back to the app’s settings view. I saved those values as metafields using the Shopify REST API.

```// write this data to custom metafields, so we can access it from app blocks
\$clickToCallRecord = \$this->getClickToCallRecord(\$shopify_installation_complete_id);
\$access_token = \$clickToCallRecord['access_token'];
\$shop = \$clickToCallRecord['shop'];
\$params = [];
\$params = [
"metafield" => [
"namespace" => "clicktocall",
"key" => "phone_number",
"value" => \$_POST['phone_number'],
"type" => "string"
],
"metafield" => [
"namespace" => "clicktocall",
"key" => "message_text",
"value" => \$_POST['message_text'],
"type" => "string"
],
];
\$json_string_params = json_encode(\$params);
'X-Shopify-Access-Token:' . \$access_token,
'content-type: application/json'
);

\$url = "https://" . \$this->api_key . ":" . \$this->secret . "@" . \$shop . "/admin/api/2021-10/metafields.json";
```

Update: The Shopify metafield POST API would only create/update a single metafield per request. I had to break it out into two calls. From what I’ve read it seems like a PUT request might do that trick for multiple fields, but for my use-case this approach is fine. Here you can see how I do it when setting default metadata on installation:

```\$params = [
"metafield" => [
"namespace" => "clicktocall",
"key" => "phone_number",
"value" => "(555)-555-5555",
"type" => "string"
]
];
\$json_string_params = json_encode(\$params);

\$url = "https://" . \$this->api_key . ":" . \$this->secret . "@" . \$shop . "/admin/api/2021-10/metafields.json";

\$params = [
"metafield" => [
"namespace" => "clicktocall",
"key" => "message_text",
"value" => "Give us a call!",
"type" => "string"
],
];
\$json_string_params = json_encode(\$params);

I populated them from the app block liquid file by accessing the global ‘shop’ object:

```<a style="color:{{block.settings.color}} " href="tel:{{ shop.metafields.clicktocall.phone_number.value }}">{{ shop.metafields.clicktocall.message_text.value }}</a>
```

After another response, they commented that I should be using “App Embed Blocks” instead of just “App Blocks”. That was because my UI component is a “floating or overlaid element”. It exists outside of the normal DOM flow and was not inline with other HTML nodes. This only required a small update to the liquid file’s schema, changing the “target” from “section” to “body”.

Although only a small difference, it does affect how merchants add Click To Call in the theme customizer. They must navigate to the Theme Settings area, and add it as an “App Embed”.

Luckily, I’m able to deep link merchants directly to that view from my onboarding instructions. The link also automatically activates my app embed. All I needed to do was get the extension’s UUID by running shopify extension info from my command line and I was able to build the URL.

```Add the Click To Call App Block from <a href="https://<?php echo \$clickToCallRecord['shop']; ?>/admin/themes/current/editor?context=apps&activateAppId=b52ccd8e-54b1-4b6d-a76f-abaed45dea97/click-to-call" target="_blank">the theme editor</a>
```

I updated my app’s home screen onboarding instructions to reflect this new flow. Everything appeared to be working when I tested, yet the app review team complained that the above issues were still unresolved. It turns out, I was able to immediately see changes to the extension that I pushed from the CLI because “development store preview” was enabled. The review team could not until I published a new version:

After that fix, the app was accepted to the Shopify App Market. If you are a Shopify merchant, check it out and let me know what you think.

## cURL PHP Abstraction

cURL is a PHP library that lets you make HTTP requests. To use it, you need to install the libcurl package. If you’re using PHP on web server, it’s probably already there. The cURL functions have a number of options, depending on what request you’d like to make. You can read all about it in the PHP official documentation.

I had a number of projects that was using it all over the place, to make a variety of requests. I was repeating a lot of code, and my mix-matching began to get confusing. Finally, I wrote a function that takes request options as arguments and does all the work:

```public function curlApiUrl(\$url, \$params, \$headers = false, \$http_verb = false){

\$curl_connection = curl_init();
// curl_setopt(\$curl_connection, CURLOPT_FOLLOWLOCATION, true);
}
curl_setopt(\$curl_connection, CURLOPT_URL, \$url);

if(\$http_verb == "post"){
curl_setopt(\$curl_connection, CURLOPT_POST, true);
curl_setopt(\$curl_connection, CURLOPT_POSTFIELDS, \$params);
}
if(\$http_verb == "delete"){
curl_setopt(\$curl_connection, CURLOPT_CUSTOMREQUEST, "DELETE");
}
if(\$http_verb == "put"){
curl_setopt(\$curl_connection, CURLOPT_CUSTOMREQUEST, "PUT");
curl_setopt(\$curl_connection, CURLOPT_POSTFIELDS, \$params);
}
//end TODO
curl_setopt(\$curl_connection, CURLOPT_RETURNTRANSFER, true);
\$curl_response = curl_exec(\$curl_connection);
\$curl_response_json = json_decode(\$curl_response,true);
curl_close(\$curl_connection);
return \$curl_response_json;
}
```

I used this as a class method in the back-end services to create Shopify apps. It’s implementation looks like this:

```\$create_recurring_charge_url = "https://" . \$this->api_key . ":" . \$this->secret . "@" . \$shop . "/admin/api/2020-04/recurring_application_charges.json";
\$params = [
'recurring_application_charge' => [
'name' => 'Basic Plan',
'price' => 25.0,
// 'return_url' => "https://" . \$shop . "/admin/apps/splitwit",
// 'test' => true,
'return_url' => "https://www.splitwit.com/service-layer/shopify-app-service?method=confirmSubscription"
]
];
'X-Shopify-Access-Token: ' . \$access_token,
'content-type: application/json'
);
\$json_string_params = json_encode(\$params);

```

cURL’s default request type is always GET. If I want to use a different HTTP verb, I can specify it as an argument. Adding this function as an abstraction layer over existing methods helps me get things done more quickly, and kept my code clear, clean, and under control.

## Radio Button Value Checked from a Database in PHP

When building software user interfaces, I create HTML forms to manage any app settings. I’ll usually have a few text and radio inputs like this:

Using PHP, I grab a database record and access its properties to populate the form. Filling out the text inputs is straight-forward:

```<?php \$clickToCallRecord = \$db_service->getClickToCallRecord(\$installation_complete_id); ?>

<div class="form-group">
<label>Phone number:</label>
<input class="form-control" type="tel" name="phone_number" value="<?php echo \$clickToCallRecord['phone_number']; ?>" placeholder="(123)-456-7890">
</div>
<div class="form-group">
<label>Message:</label>
<input class="form-control" type="text" name="message_text" value="<?php echo \$clickToCallRecord['message_text']; ?>" placeholder="Call Us Now">
</div>
<div class="form-group">
<label>Background Color:</label>
<input class="form-control" type="text" value="<?php echo \$clickToCallRecord['bg_color']; ?>" name="bg_color">
</div>
```

Checking the correct radio input requires our code to evaluate the data value. I add a PHP variable to each of the inputs as attributes. Those variables will render to either “checked” or blank:

```<?php
\$top_checked = "";
\$bottom_checked = "";
\$position = \$clickToCallRecord['position'];
if(\$position == "top"){
\$top_checked = "checked";
\$bottom_checked = "";
}else{
\$top_checked = "";
\$bottom_checked = "checked";
}

\$show_checked = "";
\$hide_checked = "";
\$display = \$clickToCallRecord['display'];
if(\$display == "show"){
\$show_checked = "checked";
\$hide_checked = "";
}else{
\$show_checked = "";
\$hide_checked = "checked";
}

?>

<div class="form-group">
<label>Position:</label>
<div>
<div class="form-check form-check-inline">
<input <?php echo \$top_checked; ?> class="form-check-input" type="radio" name="position" value="top">
<label class="form-check-label" for="matchtype">Top</label>
</div>
<div class="form-check form-check-inline">
<input <?php echo \$bottom_checked; ?> class="form-check-input" type="radio" name="position"  value="bottom">
<label class="form-check-label" for="matchtype">Bottom</label>
</div>
</div>
</div>
<hr />
<div class="form-group">
<label>Display:</label>
<div>
<div class="form-check form-check-inline">
<input <?php echo \$show_checked; ?> class="form-check-input" type="radio" name="display" value="show">
<label class="form-check-label" for="matchtype">Show</label>
</div>
<div class="form-check form-check-inline">
<input <?php echo \$hide_checked; ?> class="form-check-input" type="radio" name="display"  value="hide">
<label class="form-check-label" for="matchtype">Hide</label>
</div>
</div>
</div>
```

This example comes from a Shopify app that helps stores increase conversions by adding a UI element prompting customers to call a phone number.