Connector per Mobilizon ti permette di visualizzare i prossimi eventi di Mobilizon sul tuo sito WordPress.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Daniel Waxweiler 51ae9b9616 update dependencies 1 month ago
.github/workflows add qodana 4 months ago
.husky add eslint and prettier to pre-commit hook 2 years ago
assets release version 0.10.0 12 months ago
source release version 0.11.1 1 month ago
.eslintrc.json add Gutenberg events list block 1 year ago
.gitignore ignore .idea folder 2 years ago
.gulp.json update dev dependencies ava, eslint, eslint-plugin-ava and migrate to ES modules 1 year ago
.prettierignore add prettier 2 years ago
.prettierrc.json add prettier 2 years ago create 2 years ago add note to release procedure about adding new files in SVN 12 months ago
babel.config.json Merge branch 'main' into block 2 years ago
composer.json remove bartlett/php-compatinfo 2 years ago
composer.lock remove bartlett/php-compatinfo 2 years ago
gulpfile.cjs Merge branch 'main' into block 1 year ago
icon.afdesign add plugin icon 2 years ago
package-lock.json update dependencies 1 month ago
package.json update dependencies 1 month ago
qodana.yaml remove bootstrap from qodana.yaml 2 months ago
webpack.config.cjs add Gutenberg events list block 1 year ago

Connector for Mobilizon

Connector for Mobilizon allows you to display the upcoming events of Mobilizon, which is a federated event listing platform, on your WordPress website.

More details can be found in the WordPress Plugin Directory.

The current changelog can be found under source/changelog.txt.



  1. Make sure npm and composer are installed.
  2. Run: npm install
  3. Run: composer install

Development build

  1. Build: npm run build-dev
  2. Make sure to keep changelog.txt up-to-date.

Release procedure

  1. Make sure changelog.txt is up-to-date.
  2. Use a new version number and copy over the new section into readme.txt.
  3. Update package.json with the same version number.
  4. Update the package-lock.json: npm i --package-lock-only
  5. Build: npm run build-prod
  6. Make sure screenshots are up-to-date.
  7. Copy the built plugin into /trunk of SVN.
  8. Create a new tag of the new version: svn cp trunk tags/<version>
  9. Check the version number occurrences in both folders.
  10. Commit everything together to the release SVN: svn ci -m "release version <version>" Make sure to add new files beforehand.
  11. Commit the new version in git with the same message.
  12. Tag the new version: git tag v<version>
  13. Push the new tag to the repository: git push --tags

Other commands

  • Run ESLint: npm run eslint
  • Run JavaScript code coverage with tests: npm run coverage
  • Run tests: npm test
  • Delete build folder: npm run clean
  • Update PHP dependencies: composer update
  • Check for direct PHP dependency updates: composer outdated --direct
  • Format code with prettier: npm run format