Skip to content

Commit

Permalink
refactor!: change plugin permalink to meet WordPress Plugin Directory…
Browse files Browse the repository at this point in the history
… requirements

- Modify plugin permalink structure as requested by WordPress.org reviewers
- Update code to comply with wpackagist-plugin/plugin-check standards
- Migrate from deprecated acf-field-type-template to official acf-example-field-type
- Add ACF check during plugin activation
- Integrate Wonolog ^2.x for improved logging capabilities
- Move translations management to Crowdin platform

BREAKING CHANGE: Plugin permalink has been changed to meet WordPress.org requirements
BREAKING CHANGE: The plugin now requires ACF to be installed and active to work
  • Loading branch information
frugan-dev committed Oct 30, 2024
1 parent afed661 commit ad5d66b
Show file tree
Hide file tree
Showing 49 changed files with 3,616 additions and 3,922 deletions.
1 change: 1 addition & 0 deletions .env.dist
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@ MARIADB_DATABASE=wordpress
# 6.3.2 -> 25 Gennaio 2024, PHP 8.2.12, Composer 2.6.5
# 6.5.4 -> 5 Giugno 2024, PHP 8.2.20, Composer 2.7.7
# 6.6.1 -> 31 Luglio 2024, PHP 8.2.22, Composer 2.7.7
# 6.6.2 -> 24 Ottobre 2024, PHP 8.2.25, Composer 2.8.1
# ankitpokhrel/tus-php:^2.4 requires PHP >= 8.x
# jameelmoses/wordpress-kint-debugger:^2.0 requires PHP >= 8.x
WORDPRESS_TAG=latest
Expand Down
8 changes: 4 additions & 4 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,14 +11,14 @@ To set up a development environment, please follow these steps:
1. Clone the repo

```sh
git clone https://github.com/frugan-dev/acf-uppy
git clone https://github.com/frugan-dev/upload-field-with-uppy-for-acf
```

2. TODO

## Issues and feature requests

You've found a bug in the source code, a mistake in the documentation or maybe you'd like a new feature? Take a look at [GitHub Discussions](https://github.com/frugan-dev/acf-uppy/discussions) to see if it's already being discussed. You can help us by [submitting an issue on GitHub](https://github.com/frugan-dev/acf-uppy/issues). Before you create an issue, make sure to search the issue archive -- your issue may have already been addressed!
You've found a bug in the source code, a mistake in the documentation or maybe you'd like a new feature? Take a look at [GitHub Discussions](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/discussions) to see if it's already being discussed. You can help us by [submitting an issue on GitHub](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/issues). Before you create an issue, make sure to search the issue archive -- your issue may have already been addressed!

Please try to create bug reports that are:

Expand All @@ -32,10 +32,10 @@ Please try to create bug reports that are:
### How to submit a Pull Request

1. Search our repository for open or closed
[Pull Requests](https://github.com/frugan-dev/acf-uppy/pulls)
[Pull Requests](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/pulls)
that relate to your submission. You don't want to duplicate effort.
2. Fork the project
3. Create your feature branch (`git checkout -b feat/amazing_feature`)
4. Commit your changes (`git commit -m 'feat: add amazing_feature'`) uses [conventional commits](https://www.conventionalcommits.org), so please follow the specification in your commit messages.
5. Push to the branch (`git push origin feat/amazing_feature`)
6. [Open a Pull Request](https://github.com/frugan-dev/acf-uppy/compare?expand=1)
6. [Open a Pull Request](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/compare?expand=1)
2 changes: 1 addition & 1 deletion .github/SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Reporting a Vulnerability

If there are any vulnerabilities in **acf-uppy**, don't hesitate to _report them_.
If there are any vulnerabilities in **upload-field-with-uppy-for-acf**, don't hesitate to _report them_.

1. Use any of the [private contact addresses](https://github.com/frugan-dev).
2. Describe the vulnerability.
Expand Down
Binary file modified .wordpress-org/banner-1544x500.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified .wordpress-org/banner-772x250.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
22 changes: 11 additions & 11 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,25 +1,25 @@
## [Unreleased](https://github.com/frugan-dev/acf-uppy/compare/v0.1.0...HEAD)
## [Unreleased](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/compare/v0.1.0...HEAD)

### Merged

- Features/ci [`#1`](https://github.com/frugan-dev/acf-uppy/pull/1)
- Features/ci [`#1`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/pull/1)

### Commits

- insert phpstan path and require phpstan-wordpress [`93edc67`](https://github.com/frugan-dev/acf-uppy/commit/93edc679764912e2c3e4b5c4ae2cf1d0b49f07cc)
- static tests and release in ci [`43a51a3`](https://github.com/frugan-dev/acf-uppy/commit/43a51a3f69390baea9b4f4ff0c3829c36c8995ce)
- Fixed destPath in AcfUppy getDestFiles() and getDestPaths() methods Updated README [`f55480c`](https://github.com/frugan-dev/acf-uppy/commit/f55480c2f9f018c7c250727e1e11a3b55ee991e3)
- remove double composer cache [`0b3d251`](https://github.com/frugan-dev/acf-uppy/commit/0b3d251e8c13893c532432ac1ed0ca4b02859b1a)
- there's no really need to build in another step [`5a495f8`](https://github.com/frugan-dev/acf-uppy/commit/5a495f86674ca42c48dc3902770ad2a12beaf548)
- Applied hook filters to $hash in AcfUppyFieldV5.php [`9d3919e`](https://github.com/frugan-dev/acf-uppy/commit/9d3919e6c7ba5820c02b28de358c5caf5df42d6c)
- tests in all branches really [`26122a6`](https://github.com/frugan-dev/acf-uppy/commit/26122a6a654d0ab9ff775f14828b3a0a1beed57f)
- tests in all branches [`ff8c22f`](https://github.com/frugan-dev/acf-uppy/commit/ff8c22f04ea053b8a51e7a9443b45b531c9465cd)
- insert phpstan path and require phpstan-wordpress [`93edc67`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/93edc679764912e2c3e4b5c4ae2cf1d0b49f07cc)
- static tests and release in ci [`43a51a3`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/43a51a3f69390baea9b4f4ff0c3829c36c8995ce)
- Fixed dest_path in AcfUppy get_dest_files() and get_dest_paths() methods Updated README [`f55480c`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/f55480c2f9f018c7c250727e1e11a3b55ee991e3)
- remove double composer cache [`0b3d251`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/0b3d251e8c13893c532432ac1ed0ca4b02859b1a)
- there's no really need to build in another step [`5a495f8`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/5a495f86674ca42c48dc3902770ad2a12beaf548)
- Applied hook filters to $hash in AcfUppyFieldV5.php [`9d3919e`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/9d3919e6c7ba5820c02b28de358c5caf5df42d6c)
- tests in all branches really [`26122a6`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/26122a6a654d0ab9ff775f14828b3a0a1beed57f)
- tests in all branches [`ff8c22f`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/ff8c22f04ea053b8a51e7a9443b45b531c9465cd)

## v0.1.0 - 2021-01-03

### Commits

- Initial commit [`e62cdd5`](https://github.com/frugan-dev/acf-uppy/commit/e62cdd555efe2fca843d1f746a11f45d698098ef)
- Initial commit [`e62cdd5`](https://github.com/frugan-dev/upload-field-with-uppy-for-acf/commit/e62cdd555efe2fca843d1f746a11f45d698098ef)

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
Expand Down
5 changes: 5 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,8 @@ PHPSTAN_PRO_WEB_PORT ?=

GITHUB_TOKEN ?=

FRUGAN_UFWUFACF_CACHE_BUSTING_ENABLED ?= false

MODE ?= develop

DOCKER_COMPOSE=docker compose
Expand Down Expand Up @@ -180,6 +182,9 @@ endif
@echo "[wordpress] Creating symbolic links ($(MODE))"
@$(DOCKER_COMPOSE) exec -u$(WORDPRESS_CONTAINER_USER) $(WORDPRESS_CONTAINER_NAME) sh -c 'ln -sfn /tmp/$(PLUGIN_NAME)-plugin $${WORDPRESS_BASE_DIR:-/bitnami/wordpress}/wp-content/plugins/$(PLUGIN_NAME)'
@$(DOCKER_COMPOSE) exec -u$(WORDPRESS_CONTAINER_USER) $(WORDPRESS_CONTAINER_NAME) sh -c 'ln -sfn /tmp/$(PLUGIN_NAME)-plugin/tests/data/wp-cfm $${WORDPRESS_BASE_DIR:-/bitnami/wordpress}/wp-content/config'

@echo "[wordpress] Updating wp-config.php ($(MODE))"
@$(DOCKER_COMPOSE) exec -u$(WORDPRESS_CONTAINER_USER) $(WORDPRESS_CONTAINER_NAME) sh -c "sed -i '/define('\''FRUGAN_UFWUFACF_CACHE_BUSTING_ENABLED'\'',/d' $${WORDPRESS_BASE_DIR:-/bitnami/wordpress}/wp-config.php && sed -i '1a define('\''FRUGAN_UFWUFACF_CACHE_BUSTING_ENABLED'\'', ${FRUGAN_UFWUFACF_CACHE_BUSTING_ENABLED});' $${WORDPRESS_BASE_DIR:-/bitnami/wordpress}/wp-config.php"

@echo "[wordpress] Installing dependencies ($(MODE))"
# PHP 7.x and 8.x interpret composer.json's `extra.installer-paths` differently, perhaps due to different versions of Composer.
Expand Down
Loading

0 comments on commit ad5d66b

Please sign in to comment.