Chris Brown drbyte

If your site runs on Zen Cart 2.0.0 or 2.0.1, there are some core-file changes required for the encapsulated versions of various plugins to operate correctly on your storefront.

You can most likely simply replace (or add) a file to your site to enable an updated plugin's use. Be sure to have a backup copy of the original file, just in case the updated file causes issues on your site!

Depending on your updated plugin's directions, following is an overall list of the various Zen Cart base files that were changed in the zc201 to zc210 transition to enable additional features in encapsulated plugins.

General Changes

`/ajax.php`

This file, updated in releases following Zen Cart 2.0.0 via PR 6462 enables an encapsulated plugin to provide additional AJAX handlers.

How to setup a LEMP Development Environment with WSL2 & Valet Linux

FYI

This tutorial is based on a clean Ubuntu-22.04 install. Use at your own risk.

Prerequisites

WSL2 Installed. Follow this tutorial: https://learn.microsoft.com/en-us/windows/wsl/install#install-wsl-command
systemd enabled. Follow this blog post: https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/#set-the-systemd-flag-set-in-your-wsl-distro-settings

Setup

Let's say there are two branches: master and feature-one.

There are some files that you want in the master branch from the feature-one branch but not all the files. Let's say those files are:

app/Models/User.php
app/Controllers/UsersController.php

You can accomplish that by doing the following:

title: Setting Up Laravel in Ubuntu / DigitalOcean keywords: servers, laravel, coderstape, coder's tape description: Let's take a look at settting up a server from scratch for Laravel. date: April 1, 2019 tags: servers, laravel permalink: setting-up-laravel-in-ubuntu-digitalocean img: https://coderstape.com/storage/uploads/GZTXUbyGum2xeUZM9qBD5aPv8EKLwG3C8RGcRon4.jpeg author: Victor Gonzalez authorlink: https://github.com/vicgonvt

	<?php

	namespace App\Providers;

	use App\Encrypter;
	use Illuminate\Support\Str;
	use Illuminate\Support\ServiceProvider;

	class AppServiceProvider extends ServiceProvider
	{

	<?php

	namespace App\Http\Middleware;

	use Closure;
	use Illuminate\Http\Request;
	use Illuminate\Support\Facades\Config;

	class ClientHint
	{

	<div id="{{ $name }}" class="overlay">
	<a href="#" class="cancel"></a>

	<div class="modal">
	{{ $slot }}

	<a href="#" class="close">×</a>
	</div>
	</div>

	<?php

	/**
	* Class LocalValetDriver
	*
	* This class demonstrates how we might go about proxying any missing local images to a remote host. i.e; the production
	* site. This has been created with WordPress in mind but could be adjusted to work with any other system.
	*/
	class LocalValetDriver extends WordPressValetDriver {

	<?php
	use Illuminate\Support\Facades\DB;
	use Illuminate\Support\Facades\Schema;
	use Illuminate\Database\Schema\Blueprint;
	use Illuminate\Database\Migrations\Migration;
	class PermissionUpdateV1ToV2 extends Migration
	{
	/**
	* Run the migrations.
	*

	<?php

	// Example usage in a model:

	class ExampleModel extends Model
	{
	use HasUuid;

	protected $primaryKey = 'uuid';