PHPackages                             level-level/ll-voordemensen - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. level-level/ll-voordemensen

Abandoned → [wpackagist-plugin/voordemensen](/?search=wpackagist-plugin%2Fvoordemensen)ArchivedWordpress-plugin

level-level/ll-voordemensen
===========================

Unofficial plugin to access the VoordeMensen ticket platform directly from WordPress

v1.7.0(1y ago)11.7k1GPL-3.0-or-laterPHPPHP ^8.0

Since Nov 2Pushed 1y ago6 watchersCompare

[ Source](https://github.com/level-level/ll-voordemensen)[ Packagist](https://packagist.org/packages/level-level/ll-voordemensen)[ RSS](/packages/level-level-ll-voordemensen/feed)WikiDiscussions main Synced today

READMEChangelog (10)Dependencies (5)Versions (25)Used By (0)

[![GitHub Actions status](https://github.com/level-level/ll-voordemensen/workflows/Build%20%26%20test/badge.svg)](https://github.com/level-level/ll-voordemensen/actions)

VoordeMensen (ll-voordemensen)
==============================

[](#voordemensen-ll-voordemensen)

Unofficial plugin to access the VoordeMensen ticket platform directly from WordPress

⚠️ Abandoned
------------

[](#️-abandoned)

This package has been abandoned because none of our customers use this plugin anymore. Instead, VoordeMensen has [their own plugin](https://wordpress.org/plugins/voordemensen/) available in the WordPress plugin repository. You can also download it with Composer by [requiring it from WPackagist](https://wpackagist.org/search?q=voordemensen).

Installation
------------

[](#installation)

### Zip download (recommended)

[](#zip-download-recommended)

To download and install this plugin in your WordPress website, follow the steps below:

1. Go to the [releases tab](https://github.com/level-level/ll-voordemensen/releases) and find the latest release.
2. Download the zip named `ll-voordemensen-x.x.x.zip` (where x.x.x is the version number).
3. Rename the downloaded zip to `ll-voordemensen.zip`.
4. Extract the zip file. Make sure it puts the contents in a directory called `ll-voordemensen`.
5. Put the extracted folder and it's contents inside the `wp-content/plugins` directory of your WordPress installation.
6. Activate the plugin via the wp-admin panel.

### Composer installation (alternative method)

[](#composer-installation-alternative-method)

It's also possible to download the plugin via Packagist. Keep in mind that if you do, your composer should be setup in a way that packages of the type `wordpress-plugin` are installed in your `wp-content/plugins` directory.

Configuration
-------------

[](#configuration)

To configure the plugin, just fill in your client name in the VoordeMensen plugin settings screen.

Development
-----------

[](#development)

### Setup

[](#setup)

1. Create a new WordPress installation using the latest twenty-\* theme.
2. Navigate to the `wp-content/plugins` directory.
3. Clone this repo there, so it creates the `ll-voordemensen` directory.
4. Navigate to the `ll-voordemensen` directory, and from there, run:

```
composer-install
npm ci
npm run build
```

Run `composer run test` to verify results locally (more info about tests later in this file).

### Releasing

[](#releasing)

1. Merge all PR's in the `main` branch.
2. Change the version number in `ll-voordemensen.php`.
3. Wait for all GitHub Actions to finish.
4. Update the created draft release, set a tag and version name, in SEMVER structure like vX.X.X.
5. Publish the release.

### Composer

[](#composer)

Composer is used to manage the autoloading and automatic testing. More on the testing subject can be found later in this document.

### Webpack

[](#webpack)

#### Usage

[](#usage)

- `npm run start`
- `npm run lint`
- `npm run fix`
- `npm run build`
- `npm run scripts:lint`
- `npm run scripts:fix`
- `npm run styles:lint`
- `npm run styles:fix`
- `npm run browsersync`
- `npm run bundle-analyzer`

If you run into any problems locally with the initial installation of the node\_modules (especially webpack) try setting your local environment to DEV by executing the following on your CLI:

```
export NODE_ENV=development
```

The cause of the problem is probably the Node version and the default state it's in (it used to install all packages, but recently changed to production modules only).

#### Config

[](#config)

Using custom config for webpack dev server. Duplicate the `development/config.local.json.example` file and save it as `development/config.local.json`. In this file you add your own project url, set secure based on your dev protocol and set a port. This config is being used to overwrite the default URL of your local dev environment. This applies to the webpack-dev-server and browser-sync.

Example:

```
{
  "url": "http://local.my-site.test",
  "secure": false,
  "port": 1234
}
```

#### Images

[](#images)

Webpack automatically processes images used in the SCSS. For the images that you use directly in php, import them into `index.js`.

```
import 'images/logo.jpg';
```

Get the image URL in the .php files by using the `( new \LevelLevel\VoorDeMensen\Assets() )->get_assets_directory_url()` function. For example placing a logo in the header:

```