Projects

magiiic-autofeatureimage
This is the long description. No limit, and you can use Markdown (as well as in the following sections).

For backwards compatibility, if this section is missing, the full length of the short description will be used, and Markdown parsed.

A few notes about the sections above:
- "Contributors" is a comma separated list of wp.org/wp-plugins.org usernames
- "Tags" is a comma separated list of tags that apply to the plugin
- "Requires at least" is the lowest version that the plugin will work on
- "Tested up to" is the highest version that you’ve successfully used to test the plugin. Note that it might work on higher versions… this is just the highest one you’ve verified.
- Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use /trunk/ for stable.
Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that’ll be used for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.

If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that’s where you put the stable version, in order to eliminate any doubt.
August 27, 2025
Grunt WP plugin tasks
(formerly barely known as olib-dev)

Dev libraries that might or might not be useful for WordPress plugins developers.

See the sister project magicoli/grunt-translation-tasks to use in a generic project (using gettext insttead of WP-specific framework).

Provides
- makereadmetxt: Builds or updates the WordPress standard plugin readme.txt compiling and reformatting README.md, INSTALLATION.md, FAQ.md, CHANGELOG.md.
- i18n: Prepares internationalization assets, updating text domains, generating POT, and converting PO files to MO.
- makemo: Converts PO files to MO using WP CLI.
Installation
1. Clone the repository into your plugin’s subfolder (e.g., at dev/grunt-wp-plugin-tasks).
2. Exclude this subfolder from distribution (e.g., add dev/grunt-wp-plugin-tasks to your .distignore).
3. Add the following workspace configuration to your plugin’s package.json:
```
"workspaces": {
 "packages": [
   "dev/grunt-wp-plugin-tasks"
 ]
}
```
4. Run "npm install" to install dependencies.
5. In your plugin’s Gruntfile.js
  - Define your plugin slug name slug (e.g. ‘my-plugin’)
  - Load the custom tasks with:
    // ...existing code... const pluginName = 'YOURPLUGINSLUG'; // replace with your slug require('./dev/grunt-wp-plugin-tasks/grunt-wp-plugin-tasks.js')(grunt, pluginName); // ...existing code...
6. Run "grunt" or invoke specific tasks (e.g., "grunt i18n") as needed.
August 27, 2025
grunt-translation-tasks
Grunt tasks for managing translations and internationalization in PHP projects using standard gettext tools.

Features
- makepot (xgettext): Extracts translatable strings from PHP files into POT template
- msgmerge: Updates existing PO files with new strings from POT file
- makemo (msgfmt): Compiles PO files to binary MO files
- i18n: Complete workflow – extract, merge, and compile translations
Installation
1. Clone this repository into your project’s dev folder:
```
git submodule add https://github.com/magicoli/grunt-translation-tasks dev/grunt-translation-tasks
```
1. Add workspace configuration to your project’s package.json:
```
"workspaces": {
 "packages": [
   "dev/grunt-translation-tasks"
 ]
}
```
1. Install dependencies:
```
npm install
```
1. Load the tasks in your Gruntfile.js:
```
// Load translation tasks
require('./dev/grunt-translation-tasks/grunt-translation-tasks.js')(grunt);
```
Usage

Available Tasks
- grunt makepot – Extract strings to POT file
- grunt msgmerge – Update PO files with new POT content
- grunt makemo – Compile PO files to MO files
- grunt i18n – Run complete translation workflow
Directory Structure

Uses standard gettext directory structure:
```
locale/
├── project-name.pot          # Template file
├── fr_FR/
│   └── LC_MESSAGES/
│       ├── project-name.po   # French translations
│       └── project-name.mo   # Compiled binary
├── nl_NL/
│   └── LC_MESSAGES/
│       ├── project-name.po   # Dutch translations
│       └── project-name.mo   # Compiled binary
└── ...
```
Supported Translation Functions

Extracts strings from these PHP functions:
- _(), __() – Basic translation
- _e() – Echo translation
- _c(), _x(), _ex() – Context translation
- _n(), _nx() – Plural translation
- esc_attr__(), esc_html__() – Escaped translation
- esc_attr_e(), esc_html_e() – Escaped echo translation
Requirements
- Node.js >= 14.0.0
- Grunt CLI
- Standard gettext tools (xgettext, msgmerge, msgfmt)
Configuration

The project name is automatically detected from your package.json. You can customize paths and options by modifying the task configuration in your Gruntfile.js after loading the tasks.
August 27, 2025
WooCommerce Domain Names
This plugin is designed for domain names resellers. Currently, it only provides the sale part, actual registration has to be done manually.
- Requires WooCommerce.
- Requires Openprovider account.
- Compatible with WooCommerce Subscriptions.
December 4, 2024
magicoli/woocommerce-bookings-sync-unpaid

Include unpaid bookings in Google Calendar synchronization, to ensure bookings waiting for payments are already blocked in external calendars.

Useful if your policy is to set an option for booking requests, or if you collect payments later.

This is a simple implementation, as documented on https://woocommerce.com/document/google-calendar-integration/#section-7

December 4, 2024
WallOli

WallOli is a cross-platform tool designed to display a grid of videos across one or multiple screens. Leveraging VLC for video playback, this application ensures smooth and synchronized video presentations.

December 4, 2024
Ranger
Ranger is a formatter for date and time ranges, based (somewhat loosely) on Adam Shaw’s formatRange algorithm in fullCalendar.

Some Examples
```
<?php
use OpenPsaRangerRanger;
```
$ranger = new Ranger(‘en’); echo $ranger->format(‘2013-10-05’, ‘2013-10-20’); // Oct 5–20, 2013 echo $ranger->format(‘2013-10-05’, ‘2013-11-20’); // Oct 5 – Nov 20, 2013

$ranger = new Ranger(‘en_GB’); echo $ranger->format(‘2013-10-05’, ‘2013-10-20’); // 5–20 Oct 2013 echo $ranger->format(‘2013-10-05’, ‘2013-11-20’); // 5 Oct – 20 Nov 2013

$ranger = new Ranger(‘de’); echo $ranger->format(‘2013-10-05’, ‘2013-10-20’); // 05.–20.10.2013 echo $ranger->format(‘2013-10-05’, ‘2013-11-20’); // 05.10.–20.11.2013
Usage

To use Ranger in any other locale than "en", you will need to have the php-intl extension installed.

Instantiate ranger with the name of your locale as the parameter. You can also pass null to use the ini.default_locale setting. Afterwards, you can call format() with two date parameters. Accepted types are
- DateTime objects
  - strings (any format that DateTime can read)
  - Unix timestamps
  - null (which means current date).
Output Customization
```
<?php
use OpenPsaRangerRanger;
use IntlDateFormatter;
```
$ranger = new Ranger(‘en’); $ranger ->setRangeSeparator(‘ and ‘) ->setDateTimeSeparator(‘, between ‘) ->setDateType(IntlDateFormatter::LONG) ->setTimeType(IntlDateFormatter::SHORT);

echo $ranger->format(‘2013-10-05 10:00:01’, ‘2013-10-05 13:30:00’); // October 5, 2013, between 10:00 AM and 1:30 PM
December 4, 2024
Project Donations for WooCommerce

Collect donations for different projects with a WooCommerce product.

If you are like me, you work on several projects and would like to simply collect donations for them, without bothering creating and configuring a product for each project.

This plugin is mostly intended to be easy to set up. It is mostly usefull if you want to get donations and need or already use WooCommerce platform.

December 4, 2024
PHP Library for Project Version Management
This library provides tasks for automating versioning of your PHP projects.

It allows you to increment the version based on different levels (major, minor, patch, dev, beta, rc), and update version references in various files such as PHP files, README.md, package.json, and readme.txt.

Installation

Run the following command in your project directory:
```
composer require --dev magicoli/php-bump-library
```
And add the following script to your composer.json file:
```
 "scripts": {
    "bump-version": "robo --load-from=vendor/magicoli/php-bump-library/RoboFile.php bump:version"
  }
```
Usage
```
composer bump-version [level]
```
Replace [level] with the desired level of version increment, such as major, minor, patch, rc, beta, or dev. If you ommit it, the default level is patch.

Alternatively, you can run the script directly with the following command:
```
robo bump:version
# or
robo --load-from=path/to/RoboFile.php bump:version
```
Make sure to adjust RoboFile.php to the actual path of the file in your project.

About Versioning

Semantic Versioning follows a specific order of version increments:

Development stages (M.m.p-stage):
- Dev: development versions that are not yet stable or released.
- Beta: pre-release versions that are closer to the stable release but may still have minor issues.
- RC: release candidates, which are close to the final release but may require additional testing.
Releases (M.m.p):
- Patch: backward-compatible bug fixes.
- Minor: added functionality, still backward-compatible manner.
- Major: big bada boom.
Note that dev, beta, and rc versions are considered inferior to the normal versions and are typically used in pre-release stages or development cycles: 1.0-dev < 1.0-beta < 1.0-rc < 1.0.

For example, if your version is 1.0.0 and you bump it on the dev level, new version will be 1.0.1-dev (note the pach increment). If you bump the dev to beta, it will keep its main version and become 1.0.1-beta. And if you bump 1.0.1-beta without arguments, the new version will be 1.0.1.

License

This library is licensed under the AGPL-v3 License.
December 4, 2024
Oli’s Breadcrumbs
Several ways to add breadcrumbs to your pages, if your theme does not support them. If you theme already supports breadcrumbs, you probably don’t need this plugin, as it is likely to have less options.

You can add breadcrumbs with any of these methods:
- [breadcrumbs] shortcode
- Breadcrumbs widget
- Breadcrumbs Divi Module (for Divi Themes or with Divi plugin)
- Breadcrumbs Element WPBakery Page Builder (aka js_composer aka Visual Composer)
Here are the options for the shordcode.
- [breadcrumbs exclude-home="true"] do not start the breadcrumbs with home page, default false
- [breadcrumbs exclude-archives="true"] do not include main articles archive link, default false
- [breadcrumbs exclude-title="true"] do not end the breadcrumbs with the post title, default false
- [breadcrumbs separator="×"] separator, default "/"
Equivalent options are available in the widget and the Divi Module.
December 4, 2024