extensions-directory issueshttps://lab.civicrm.org/extensions/extensions-directory/-/issues2020-07-01T16:51:30Zhttps://lab.civicrm.org/extensions/extensions-directory/-/issues/41Add additional people to add extension repos2020-07-01T16:51:30ZhomotechsualAdd additional people to add extension reposIt would be good to reduce load on @mlutfy by allowing additional community members to handle extension repo creation on GitLab under Extensions.It would be good to reduce load on @mlutfy by allowing additional community members to handle extension repo creation on GitLab under Extensions.https://lab.civicrm.org/extensions/extensions-directory/-/issues/37TEST, IGNORE Request review for [FIXME_COM.FIXME_VENDOR.FIXME_NAME]2019-06-14T19:02:05ZAllenShawTestReviewerTEST, IGNORE Request review for [FIXME_COM.FIXME_VENDOR.FIXME_NAME]TESTTESThttps://lab.civicrm.org/extensions/extensions-directory/-/issues/36Request review for com.physicianhealth.sms.ringcentral2019-06-25T19:12:56ZDaveDRequest review for com.physicianhealth.sms.ringcentralhttps://civicrm.org/extensions/sms-provider-for-ringcentral-telus
~"Extension Review Request"https://civicrm.org/extensions/sms-provider-for-ringcentral-telus
~"Extension Review Request"https://lab.civicrm.org/extensions/extensions-directory/-/issues/35Request review for org.wikimedia.thethe2019-06-25T19:15:30ZeileenRequest review for org.wikimedia.thetheAllenShawAllenShawhttps://lab.civicrm.org/extensions/extensions-directory/-/issues/34Request review for com.aghstrategies.tsys2019-07-15T20:07:44ZalicefruminRequest review for com.aghstrategies.tsysGithub Link: https://github.com/aghstrategies/com.aghstrategies.tsys
Extensions Page on CiviCRM.org: https://civicrm.org/extensions/tsys
Documentation: https://docs.civicrm.org/tsys/en/latest/
Best Contact: alice@aghstrategies.com Github Link: https://github.com/aghstrategies/com.aghstrategies.tsys
Extensions Page on CiviCRM.org: https://civicrm.org/extensions/tsys
Documentation: https://docs.civicrm.org/tsys/en/latest/
Best Contact: alice@aghstrategies.com https://lab.civicrm.org/extensions/extensions-directory/-/issues/33test, ignore2019-05-31T16:02:44ZAllenShawtest, ignorehttps://lab.civicrm.org/extensions/extensions-directory/-/issues/32test, ignore2019-05-31T15:51:22ZAllenShawtest, ignorehttps://lab.civicrm.org/extensions/extensions-directory/-/issues/31test, ignore2019-05-31T15:50:50ZAllenShawtest, ignorehttps://lab.civicrm.org/extensions/extensions-directory/-/issues/30ignore, test issue2019-05-31T15:50:39ZAllenShawignore, test issue/label fdsa/label fdsahttps://lab.civicrm.org/extensions/extensions-directory/-/issues/29Meta-Level Question: GSOC Projects - include them on GitLab or GitHub/make th...2023-03-08T13:49:45ZCM ToolanMeta-Level Question: GSOC Projects - include them on GitLab or GitHub/make them more accessible?Wasn't sure where to put this! It's basically a meta-level question about GSoC projects.
There's been some neat work done on old GSoC projects, but I don't seem to see those extensions pulled into the CiviCRM ecosystem somewhere, for f...Wasn't sure where to put this! It's basically a meta-level question about GSoC projects.
There's been some neat work done on old GSoC projects, but I don't seem to see those extensions pulled into the CiviCRM ecosystem somewhere, for further development. Even assuming the extensions might need more work/polishing before being officially released on https://civicrm.org/extensions , right now it seems like they're sort of 'floating' in the informal institutional memory in Mattermost chat channels, rather than being put somewhere were a developer not on the GSoC original project might naturally come across them and continue to develop them.
https://github.com/siddharthg/org.civicrm.civisocial
https://gitlab.com/asludds/civicrm-turfcutter
Is there some way to bring these into the CiviCRM gitlab/github ecosystem? I'm particularly looking at these two, because I'm volunteering with a political advocacy group, and even just some development on these areas would be of interest on us (and I only found these by stumbling across the channels in Mattermost). I don't know if there are other GSoC projects floating out there, but I'd love to know! :)https://lab.civicrm.org/extensions/extensions-directory/-/issues/28Request review for "uk.artfulrobot.civicrm.gocardless"2019-06-25T19:15:57ZRichRequest review for "uk.artfulrobot.civicrm.gocardless"On the <https://docs.civicrm.org/dev/en/latest/extensions/publish/> page it tells you to:
> One of the extension's maintainers must [request an extension review](https://issues.civicrm.org/jira/secure/CreateIssue!default.jspa?selectedPr...On the <https://docs.civicrm.org/dev/en/latest/extensions/publish/> page it tells you to:
> One of the extension's maintainers must [request an extension review](https://issues.civicrm.org/jira/secure/CreateIssue!default.jspa?selectedProjectId=10400&issuetype=10000).
But following that link (after having logged in a jira) gives:
> Proxy Error
>
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET /jira/secure/CreateIssue!default.jspa.
>
> Reason: Error reading from remote server
I'm trying to request a review of <https://civicrm.org/extensions/gocardless-direct-debit-payment-processor-for-civicrm>https://lab.civicrm.org/extensions/extensions-directory/-/issues/27Please list the eWAY Recurring Payment Processor by Agileware in the CiviCRM'...2019-06-25T19:16:17Zjustinfreeman (Agileware)Please list the eWAY Recurring Payment Processor by Agileware in the CiviCRM's internal Extensions DirectoryPlease list the eWAY Recurring Payment Processor by Agileware in the CiviCRM's internal Extensions Directory.
https://civicrm.org/extensions/eway-recurring-payment-processor-agileware
I posted this request in the old Jira over 12 month...Please list the eWAY Recurring Payment Processor by Agileware in the CiviCRM's internal Extensions Directory.
https://civicrm.org/extensions/eway-recurring-payment-processor-agileware
I posted this request in the old Jira over 12 months ago too, https://issues.civicrm.org/jira/browse/EXT-57
Have been trying to get this actioned for 4 years now...https://lab.civicrm.org/extensions/extensions-directory/-/issues/26Extension auto-release recently started sending a lot of emails for mismatchi...2018-06-19T14:10:25ZbgmExtension auto-release recently started sending a lot of emails for mismatching tagsSince ~ 2018-06-05, the extdir nightly job for extension auto-release has started sending out a lot of emails about mismatching tags.
Example from `cividiscount`:
```
Unfortunately we have found a few errors while processing your relea...Since ~ 2018-06-05, the extdir nightly job for extension auto-release has started sending out a lot of emails about mismatching tags.
Example from `cividiscount`:
```
Unfortunately we have found a few errors while processing your release:
- The version numbers in the info.xml ("2.0") and in the git tag ("v2.0")
do not match.
```
ref: https://chat.civicrm.org/civicrm/pl/kxr4xdmh37bafqwk6yekhs5xhobgmbgmhttps://lab.civicrm.org/extensions/extensions-directory/-/issues/25Extension auto-release does not populate the 'zip' field for extensions on la...2018-05-28T13:55:42ZbgmExtension auto-release does not populate the 'zip' field for extensions on lab.civicrm.orgc.f. https://chat.civicrm.org/civicrm/pl/rcox8zncrffzjdaiqk6pjrwera
cc @jaapjansmac.f. https://chat.civicrm.org/civicrm/pl/rcox8zncrffzjdaiqk6pjrwera
cc @jaapjansmahttps://lab.civicrm.org/extensions/extensions-directory/-/issues/24Auto-releaser: Allow hosting extensions on lab.civicrm.org2018-03-29T14:31:04ZbgmAuto-releaser: Allow hosting extensions on lab.civicrm.orgCurrently the extension directory only allows hosting extensions on Github.com. Now that we have https://lab.civicrm.org/extensions/, we would like to allow/encourage to host extensions there as well.
Reported by @jaapjansmaCurrently the extension directory only allows hosting extensions on Github.com. Now that we have https://lab.civicrm.org/extensions/, we would like to allow/encourage to host extensions there as well.
Reported by @jaapjansmabgmbgmhttps://lab.civicrm.org/extensions/extensions-directory/-/issues/23Allow in-app messages from extension authors2019-07-19T19:49:31ZbgmAllow in-app messages from extension authorsProposal discussed at CiviCamp Brussels, for consideration by the Ext WG and Core Team:
Context: Extensions do not have a way to communicate with their users. This may be to communicate:
* that the extension is being deprecated (possibl...Proposal discussed at CiviCamp Brussels, for consideration by the Ext WG and Core Team:
Context: Extensions do not have a way to communicate with their users. This may be to communicate:
* that the extension is being deprecated (possibly in favour of another one),
* fundraising request,
* promote trainings/workshops, or other services.
Implementation:
* Partner benefit (as a way to validate that the extension author's message is compatible with CiviCRM values/branding/community).
* Currently in-app messages are fed from a google-doc. In the short term, we could open up write permissions to the google-doc to a few people/partners, who could handle the requests. The requests could be done on Mattermost or Gitlab (transparency).
* In-app messages for extensions, for now, would only be shown to administrators (in-app messages currently have options to show that message only to admins, all users, etc)
* and of course, an in-app message would only be shown if the extension is enabled.
Technically, this requires small changes to civicrm core, as well as the in-app messaging app. As the community grows, eventually, we may want to have a forms for this on civicrm.org, but that's more work, which we can address when it becomes necessary.
cc @xavier @totten @ginkgofjg @AllenShaw @joshhttps://lab.civicrm.org/extensions/extensions-directory/-/issues/22In-app extensions manager does not notify about new release of com.elisseck.c...2020-04-22T17:24:53ZginkgofjgIn-app extensions manager does not notify about new release of com.elisseck.civihoneypotTo reproduce, install v 1.0.3 of the extension. Visit the extensions manager, hit refresh. Despite the publication of a [release node](https://civicrm.org/extensions/civihoneypot/105) for v 1.0.5, note that you are not prompted to upgrad...To reproduce, install v 1.0.3 of the extension. Visit the extensions manager, hit refresh. Despite the publication of a [release node](https://civicrm.org/extensions/civihoneypot/105) for v 1.0.5, note that you are not prompted to upgrade. Note that the same is not true for other out-of-date extensions. (On the system where this behavior was discovered, CiviRules was also out of date but showed that an upgrade was available.)
Created as an issue here (rather than in the extension's issue tracker) because -- with the information we have now, anyway -- this seems more like an infrastructure problem than something the maintainer needs to change.
Note that this extension, despite submitting a request, has not yet been flagged for automated distribution. Could it be that extensions which are not whitelisted are treated differently?ginkgofjgginkgofjghttps://lab.civicrm.org/extensions/extensions-directory/-/issues/21"The Fully Qualified Name did not match parent extension" validation failure2021-03-16T21:33:06Zxurizaemon"The Fully Qualified Name did not match parent extension" validation failureSee also #12 #20
I am getting this error but I don't understand what it actually means.
> From: info@civicrm.org
> Subject: Your extension release on civicrm.org
> Date: 19 November 2017 at 16:11
>
> This is a message from the automa...See also #12 #20
I am getting this error but I don't understand what it actually means.
> From: info@civicrm.org
> Subject: Your extension release on civicrm.org
> Date: 19 November 2017 at 16:11
>
> This is a message from the automated release system on civicrm.org. Congratulations on releasing version v1.0 of extension 'Environment Indicator Integration'.
>
> Unfortunately we have found a few errors while processing your release:
> - The Fully Qualified Name did not match parent extension: contrib.environmentindicator
>
> You will need to correct these errors before we can accept this release.
>
> Further help is available in the developer guide at https://docs.civicrm.org/dev/en/latest/extensions/publish/.
>
> You can also request help on Mattermost at https://chat.civicrm.org/civicrm/channels/extensions.
>
> If you no longer wish to publish this release, deleting the v1.0 tag from your extension's repository will stop these notices.
>
> Thank you so much for being an active contributor to CiviCRM and our community.
* Is it saying that the extension name ("Environment Indicator Integration") and the extension key (contrib.environmentindicator) do not match? (The docs say it's OK if the extension "basename" matched the file tag?)
* Is it reporting to me that it's detected the historic change of this extension key from contrib.environmentindicator to nz.co.fuzion.environmentindicator?
* Should it be reporting invalid info.xml in unpublished releases? (I published v1.2 of this ext in order to fix the mismatch in info.xml, why validate unsupported / unpublished releases?)
* Daily emails feels a bit on the heavy side!
I know this is a repeat of #12 but I can't tell what the actual invalidity is from that ticket, only that removing a git tag will somehow fix it. Hoping that by asking I can help document the solution for the next person ...https://lab.civicrm.org/extensions/extensions-directory/-/issues/20Automated release system email warning about older release2023-03-08T13:05:12ZxurizaemonAutomated release system email warning about older releaseI have this email from the automated release system:
> This is a message from the automated release system on civicrm.org. Congratulations on releasing version v1.1 of extension 'Environment Indicator Integration'.
>
> Unfortunately we...I have this email from the automated release system:
> This is a message from the automated release system on civicrm.org. Congratulations on releasing version v1.1 of extension 'Environment Indicator Integration'.
>
> Unfortunately we have found a few errors while processing your release:
> - The version numbers in the info.xml ("1.0") and in the git tag ("1.1") do not match.
>
> You will need to correct these errors before we can accept this release.
The current release of that extension is 1.2 at https://civicrm.org/extensions/environment-indicator-integration
Is there a way to prevent these notifications for releases other than the current release of an extension?
* Download URL: https://github.com/fuzionnz/nz.co.fuzion.environmentindicator/archive/v1.2.zip
* Version in release: 1.2
* Repo: https://github.com/fuzionnz/nz.co.fuzion.environmentindicator
* Uploaded info.xml: https://civicrm.org/sites/civicrm.org/files/extensions/info_315.xml
* CiviCRM extension node: https://civicrm.org/extensions/environment-indicator-integration
AFAICT there isn't a node on CiviCRM.org for v1.0 or v1.1https://lab.civicrm.org/extensions/extensions-directory/-/issues/18word change to heading USAGE2020-10-20T20:26:50ZAnneDruword change to heading USAGELooking at this boilerplate from a non-technical 'user' point of view, the term 'USAGE' is unfamiliar. I suggest we keep USAGE, but add /Getting Started.
eg . Usage/Getting started
etc
This is related to issue #13Looking at this boilerplate from a non-technical 'user' point of view, the term 'USAGE' is unfamiliar. I suggest we keep USAGE, but add /Getting Started.
eg . Usage/Getting started
etc
This is related to issue #13