Did something changed on the payments side? I've noticed that I'm not subscribed anymore to one extension for months now.
Extiverse. Breaching the frontier in Flarum forum and community management
hrvoje_hr Stripe logs show the subscription was automatically cancelled when there was insufficient funds on the credit card in April-May. Stripe attempted to collect the funds 4 times unsuccessfully before cancelling the subscription.
I'm not sure what notifications are sent by Extiverse/Stripe, if any.
Feel free to reach out to me directly if you would like me to look into the Stripe logs in more details, but I don't think there is much more to it.
You will have to subscribe again. If you had a special plan that is no longer available you can contact me so I can restore it, but I don't think that was the case.
clarkwinkelmann thanks for clearing this out. I use some generic prepaid card for online subscriptions and at most times I'm unaware of the balance. However, all other subscriptions notifies me wherever there is an issue with payment. I will subscribe again, let me know how can I reimburse this few months, especially because the extension still works on my side all this time
@luceos it would be useful if you can implement some kind of email notifications
- Edited
hrvoje_hr it would be useful if you can implement some kind of email notifications
I will put this on my backlog immediately, it's frustrating that it caused so much confusion without there being a real reason for it. I am currently in the process of merging extiverse into the new flarum portal on next.flarum.org; so it won't be an immediate change.
2 months later
luceos How do we become an extension uploader on Extiverse?
We already have an account on Extiverse, our extension are available on Packagist, GitHub, and the Flarum forum
- Edited
BetterFlarum your extensions are synced without issue, the only thing that hampers them being shown is that your extension having a dependency on flarum/core as *. Extiverse is set up so that it provides an honest view on how compatible extensions are with the current Flarum core version. As such - to get your extensions listed - you will need to use a stricter dependency, for now 1.* would suffice. Once 2.x comes out, you can publish versions that are compatible with that.
2 months later
- Edited
Hi @luceos, first of all thank you for maintaining and operating Extiverse!
I have a question regarding syncing extensions; is it possible to create a GitHub Workflow which automatically syncs an extension with Extiverse if a new Tag is pushed to remote origin?
I tried something like this, but it I couldn't manage to get it working:
sync.yml
on:
push:
tags:
- '*'
name: Sync with Extiverse
jobs:
sync:
name: Sync Extiverse
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v2
- name: Sync with Extiverse
run: |
curl -X POST \
-H "Authorization: Bearer ${{ secrets.EXTIVERSE_API_TOKEN }}" \
https://extiverse.com/develop/premium-extensions/.../syncBasically, the workflow is "successful" but the Server returns 405 Method Not Allowed when viewing what happened in the step. For the secret I used a api:read token, but as the name already suggests, this might be the wrong token.
- Edited
davetodave178 that is not possible. Once the new website is up one of the first things I will add is creating a full GitHub integration, as an app, so that syncs are immediate.
In the meantime I could indeed look at an API endpoint that allows syncing 
GET https://extiverse.com/api/premium-extensions/<vendor/extension>/syncThis requires an API token, and a GET request. It will send a 201 back if successful. This is untested..
luceos I just tested it and normal Tags (e.g. 0.0.1) are working perfectly! 
I have noticed that alpha and beta tags (e.g. 0.0.2-alpha.1 or 0.0.3-beta.2) are not synced via the API endpoint (works when syncing manually).
The workflow is always initiated, but I have noticed that for some reason the doctype of the response gets "mixed up" with the curl progress meter in alpha and beta tags:
Workflow of beta tag (auto syncing currently not working)
Run curl -X GET \
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
<!DOCTYPE html>
100 438 0 438 0 0 589 0 --:--:-- --:--:-- --:--:-- 590
<html>
<head>
<meta charset="UTF-8" />
<meta http-equiv="refresh" content="0;url='https://extiverse.com/develop/premium-extensions'" />
<title>Redirecting to https://extiverse.com/develop/premium-extensions</title>
</head>
<body>
Redirecting to <a href="https://extiverse.com/develop/premium-extensions">https://extiverse.com/develop/premium-extensions</a>.
</body>
</html>Workflow of regular tag (auto syncing working):
Run curl -X GET \
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 438 0 438 0 0 783 0 --:--:-- --:--:-- --:--:-- 784
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8" />
<meta http-equiv="refresh" content="0;url='https://extiverse.com/develop/premium-extensions'" />
<title>Redirecting to https://extiverse.com/develop/premium-extensions</title>
</head>
<body>
Redirecting to <a href="https://extiverse.com/develop/premium-extensions">https://extiverse.com/develop/premium-extensions</a>.
</body>
</html>What might be the reason for this?
davetodave178 use a header to set content type to application/json
luceos Great it works now also in this case. Thank you so much for adding this endpoint this quickly! 
- Edited
@luceos If you want to use the workflow for Blomstra Premium Extensions, I think the following should work just by copy/pasting it (besides adding the Extiverse API token as a secret). Requirements for this particular workflow to work are:
- Owner/Vendor is the same on GitHub as it is on Extiverse
- Extensions on GitHub are prefixed with
flarum-ext-but not on Extiverse (for example blomstra/flarum-ext-gdpr and https://extiverse.com/extension/blomstra/gdpr
.github/workflows/sync.yml
name: Extiverse
on:
workflow_dispatch:
push:
tags:
- '*'
jobs:
sync:
name: Sync Extension
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Sync with Extiverse
run: |
REPO_NAME="${{ github.repository }}"
OWNER=${REPO_NAME%%/*}
REPO=${REPO_NAME##*/}
MODIFIED_REPO=${REPO#flarum-ext-}
SYNC_URL="https://extiverse.com/api/premium-extensions/$OWNER/$MODIFIED_REPO/sync"
curl -X GET \
-H "Authorization: Bearer ${{ secrets.EXTIVERSE_API_TOKEN }}" \
-H "Content-Type: application/json" \
$SYNC_URLdavetodave178 thanks for that, much appreciated to ping back with this solution.
I will share this in the extiverse premium discord channel, Dave let me know in DM if you want to hop into there for an occasional update as well.
- Edited
In case you want to make the workflow reusable and thus better maintainable, you can create a new dedicated repo and use a slightly adjusted version of the workflow above. Define that the job is triggered on workflow_call (trigger when a new tag is pushed will still be defined in each extension repository itself).
Please note that you must make the workflow repository accessible from other repositories in the same organization. See this GitHub Doc for more information.
your-organization/flarum-workflow-example/.github/workflows/sync.yml
on:
workflow_call:
jobs:
sync:
name: Sync Extension
...Now if you want to use this reusable workflow in a extension repository, you can include it like this:
your-organization/flarum-ext-example/.github/workflows/sync.yml
name: Extiverse
on:
push:
tags:
- '*'
jobs:
trigger-sync:
name: Invoke Workflow
uses: your-organization/flarum-workflow-example/.github/workflows/sync.yml@master
secrets: inheritAgain, please note that you have to set the secret either in each repository you want to use this workflow or at the organization level. AFAIK, you should be able to access either one with e.g.${{ secrets.EXTIVERSE_API_TOKEN }}.
The secret must be an API token (i.e. api:read) and not a composer token (e.g. composer:download).
davetodave178 please clearly state this has to be an API token. Not a composer one.
luceos Good point. I appended it to the post above.
21 days later
Hello, I wonder what Extiverse uses to determine that an extension is incompatible. One of my extension is marked as incompatible although it can work correctly on the latest flarum. (More info: wolfshards DaleZ)