craftcms / console Goto Github PK

It would be nice to be able to add notes to invoices like we can with licenses.

Currently we receive emails for license renewals but not the monthly subscription invoice. We use these emails for bookkeeping.

Bonus: being able to set a billing contact for these emails would be 💯 but I saw there's already an open feature request for that.

It would be great to be able to quickly get to the invoice for a license much like you can currently get to by going the other way around. You could simply link the invoice number in the history section from the license detail view.

Basically we send regular emails to clients saying - it's time to update Craft and plugins.
At the moment we're having to manually filter from the CMS license list by copying the data out and importing it into a spreadsheet (API dashboard connection is planned but not anytime soon...).

It would be great if there was a way to filter by expired/expiring/active states and/or a date selection.

For example I could filter by licenses that are expiring next month.

Allowing devs to add a webhook (or a few) to do something when a plugin sale comes in would be great. E.g., Zapier, Slack, IFFT type stuff.

Description

It would be very nice if the license details for a plugin included a link to the Plugin Store page for that plugin, as shown (very crudely with an arrow) in the below screencap:

This would be helpful for clients where we may have old plugins installed, because sometimes we go to check whether we need to renew licenses and we're like "are we still using this? what even is it?"

Hi,

Could you be so kind to add kiwicloud.nl and redkiwi.cloud to the list of developer domains?
Thank you very much in advance,

Rik

If you are broke and you try to buy a craft licence with your credit card, in the checkout screen the loading spinner will come but no error message is shown.

https://api.craftcms.com/v1/payments?v=
Status Code: 400 Bad Request
message: "Your card has insufficient funds."

Craft 3.4.14 if it matters.

Don't judge me please ;)

In the Udemy marketplace, you as an instructor can add the Google Analytics Tracking ID. It would be great to have this feature in the Plugin Store and allow us to track our plugins at least from https://plugins.craftcms.com/ not sure if that could be possible from the CP.

this tool will provide you with a better understanding of your visitors so you can execute your marketing efforts in an effective manner. By doing so, you are able to strategize and optimize your conversion rates and drive sales.

Info about how Udemy handles this feature

There is nowhere that I can find on the current Craft or Plugin license pages which shows how much I will be charged, now or in the future.

1. When enabling auto-renew, the toggle simply turns on, but I'm given no indication of how much I will be charged when that renewal happens, either before or after I toggle the switch.
2. If auto-renew is already enabled, I can't see how much I am scheduled to be charged when that auto-renew happens.
3. When I manually renew a license, I only see how much that renewal will cost when I get to the third screen (my cart).

Ideally I'd see how much I was going to be charged before initiating any action at all from an individual license screen. Right now it's akin to an e-commerce site having "Add to Cart" buttons with no associated prices.

Description

If you try to add a note to a license, pasting text in the field will leave the Save button inactive.

Typing in the same field works.

Steps to reproduce

1. Add a note to a license by pasting text in (no typing).

For those of us who are incapable of using a consistent email for buying Craft licenses, bulk license uploading would be super useful!

Hey Guys

With the announcement of Craft Console and the new Organization Accounts, it would awesome if there were an API where we can query the CMS and Plugin licenses we've purchased as a customer. The use case is that we operate a lot of Craft sites and we'd like to aggregate the Craft license info into our internal management systems so we can be proactive with renewals and upgrades.

One further enhancement which would also be great would be if there was an API for Craft and plugins where we can get the changelog / latest version information so we can remotely check that we have the latest versions of everything across our estate of sites

If I currently search for "Sprout" or "Sprout Forms" our wonderful competitor Solspace appears in the results before our plugins as they appear to be ordered alphabetically:
http://share.barrelstrength.co/635c3668caa5

While, as a user, I think it's nice that related plugins come up in search results, I have no issues with firms in the store using creative keywords to appear in the results they hope to appear in, but it would be nice to have search give a higher priority to the weight of certain fields in the results when a search involves words specific to a brand, company, or plugin name.

I'm seeing the circle spinner for an unusually long time loading the plugin store, then loading the current page of the plugin store, and finally loading the cart.

Ransom noted:

Seems like there are a few requests to the Craftnet API that are just really slow for some reason. In particular,
https://api.craftcms.com/v1/countries took almost 16 seconds for TTFB

In an Incognito Chrome browser, it took 31 seconds to go from clicking on the Plugin Store nav to having a loading plugin store page.

I've noted this performance issue over several days, from several different machines.

I have a video recording of this, but I can't upload it to Github apparently. Available upon request.

It'd be very useful to have a sort URL param that we can use to specify the sorting order of the plugin licenses, by passing in the field name to sort by, and also an order param to choose between ASC and DESC

This would allow for a much more flexible display of the data.

It'd be nice if CraftNet had an API endpoint to query a plugin data the way it has one for licenses.

I'm interested in it primarily so I can get all plugins, get information about them, etc. But it also could potentially be used to set information as well, which could come in handy.

This seems sad and lonely, and is annoying that it takes up like 15% of page width space. I imagine there's a better place for this, perhaps the top right corner of page or under the Information area would be a quick improvement? :)

Being larger might also make it much easier for customers to notice it and possible use the docs. 😆

Some plugin types have an "interface" of sorts where certain features are supported or not. It would be great to start collecting and organizing this data for people browsing the plugin store via a faceted search.

For example, Craft Commerce payment gateways have some attributes such as:

• Webhooks
• Refunds
• Preauthorization
• Payment voiding
• Item bags
• Subscriptions

More generically, plugins might have:

• Automated tests
• Works with Craft CMS Webhooks
• Extensible (via Events)
• Works with Craft Commerce
• Requires third-party subscription
• Granular permissions
• Supports Content Exporting
• Supports Content Importing
• Supports multi-site / localization
• Supports GraphQL

Discussed in https://github.com/orgs/craftcms/discussions/69

Right now, Craft ID shows the license sales for a plugin, however, if we made a sale outside of the Craft and import a license I believe the only way to see that license is to view it via querying the API.

It would be nice to have an additional Licenses tab in the Developer section of our Craft ID account where all licenses associated with our plugins would display. It would also be nice to be able to filter them by plugin and search by email or the private notes field.

I would love to receive an email notification when a refund is processed and the plugin handle

How about adding some sort of "features list" on the Plugin overview page to display if the Plugin is "Multi-site ready/compatible". I've noticed some Plugins doesn't support multi-site full out and it would be ideal to show this to the user beforehand.

I want to unsubscribe from "Important license info" emails. Buying a commercial plugin shouldn't subject one to a lifetime of email remainders, or put the burden on the user to make an email filter to keep these out of an inbox. I imagine these could become a nuisance after a few years of buying commercial plugins.

I think unsubscribing from these is a legitimate request because the email isn't critical, as we can get this same info in other places (logging into Craft ID site, viewing CP of a site where an outdated plugin is installed).

Currently, we have the ability to create new plugin licenses but it would be nice to be able to delete or update license information through the Craftnet API

I think this would be interesting info for some developers. For example, it’d be interesting to see how many installs might be affected by a security vulnerability (and see if a more aggressive push to upgrade needs to be made), or after a large release it’d be nice to know when you’re “out of the woods” 😆 (enough people have installed/updated to that version without their sites being blown up).

I would like to propose adding support for using BitBucket repositories in the same way as a github repo to back a plugin.

Currently, all category listings are sorted by "Active Installs", which, as I understand it, isn't actually active install, more like total installs since the plugin was published. As time goes by, that number gets less and less relevant as plugins that might have been popular before, now is abandoned and/or replaced.

A better indicator to a plugin's current popularity would be installs over the last, say, 3 months. I propose to replace the default sort with something like that, and still keep the active installs as a sort option.

Taking a page out of the WordPress ecosystem, it'd be useful for people using plugins to cast an affirmational vote that a plugin does work on various major versions of Craft CMS.

The display could be something like:

Known compatible with Craft CMS: 3.0, 3.1, 3.2, 3.3, 3.4

This would be a "crowd sourced" voting mechanism. The only issue I foresee could be lack of incentive for people to bother voting.

So you might need to have them listed as working by default, but allow people to vote NO if it's not working.

Whenever the author releases a new version of the plugin, this information is reset.

Description

I'm currently using a fork of a plugin for my site, and using a "dev-[branch-name]" version specification in the composer "require" block, with a "vcs" repository definition for the fork location on github - basically looks like:
This worked fine for several months, but I'm suddenly now seeing a prompt to update to the latest version of the plugin on the author's "master" branch when running Craft update. Has something changed with the requirements for the composer file version declarations for Craft to respect the "dev-" branch version as the preferred plugin version?

https://craftcms.stackexchange.com/questions/36558/dev-branch-plugin-forks-being-prompted-for-update/36560#36560

Steps to reproduce

1. Use a forked version of a plugin

"repositories": [
  {
    "type": "vcs",
    "url": "https://github.com/[forked-account/plugin-name]"
  }
],
"require": {
  "[original-account/plugin-name]": "dev-branch-name"
  ...
}
...

2. Navigate to Utilities > Updates - all releases of the "original" plugin should be listed there as available updates.

Additional info

• Craft version: 3.5.15.1
• PHP version: 7.4.11
• Database driver & version: MySQL 5.5.5
• Plugins & versions: a forked version Feed Me

Hi, I would love to be able to like/star/fav plugins in the plugin store and display them in a list only I have access to.

This would speed up setting up a new site with plugins I tend to use in a lot of projects.

I've long wanted to make all of the nystudio107.com plugins available for free for people who are running free Solo edition Craft CMS installs.

The rationale is that if it's a Solo edition site, it's usually either a freelancer or agency's own website, or it's a smaller client site with little budget.

Currently, there's no way I'm aware of that a license can be tied to a particular edition of Craft, so I'd like to propose that just as Craft CMS has different pricing models for different editions of Craft CMS, that plugin developers can also choose different pricing tier depending on the Craft CMS edition.

This would be opt-in, so all existing plugins would still work as they do now. But you could add a plugin edition and tie it to a specific Craft CMS edition.

That way developers like me who'd like their plugins to be free for Solo edition Craft CMS sites (or discounted perhaps) could do that.

Adding an actual link would allow users to open each plugin in a new tab for comparison.

I tried adding a few "features" to one of my plugins to see how that would look and when I leave the description empty, the info icon appear but the content (which I left empty) is undefined.

Maybe the label could be hidden if the description is empty?

Currently, there isn't a way to view how many sales of a plugin in Craftnet, you can only see active installs. As a tweak to https://id.craftcms.com/developer/sales you could show top level information (see screenshot). Clicking number of sales (or possibly plugin title or other CTA) would take you to the current page, but filtered by the plugin selected.

Currently when seeing our plugins, we can only see how many time's it's been installed. It would be good if there was more information to this. E.g. How many are on a dev environment, domain installed on (If not breaking any privacy issues!) etc.

I have around 140ish plugin installs for paid plugins, yet only received 18 payments.

I know people are using them also as I get support requests regularly on Discord, but I am unsure if these are in development, or not.

If installed as a trial also, it should be protected a bit more when on a production environment, to stop people getting away using premium plugins for free.

I'm still finding it difficult to write instructions for clients on how to renew their licenses. Taking this use case as an example:

• Craft is licensed
• Some plugins have valid licenses for another 10 months
• Some plugins expired a week ago

The simplest way I'm aware of is to tell them to:

1. Login to id.craftcms.com
2. Click the blue part of their Craft license key
3. Click Renew License

That way, the modal popups up with "renew all", saving them the hassle of renewing individual plugins. But if I do that, it tries to renew them all until 2023, which is 2 years rather than 1.

The second option I can think of is to tell them which plugins to add to their cart individually, which is kind of a pain.
The third option is to give them super admin privileges in the CMS, which is less of a problem now that we use Project Config on everything (so they can't access Settings), but still not ideal. Clients should never need to be given full admin access just to renew their licenses.

The ideal solution to this is to simply give clients a button which extends all their expired licenses by 1 year. id.craftcms.com is useful for devs, but not particularly user friendly for non-web clients. They really just need a simple way to renew their licenses that doesn't involve me sending a detailed list of screenshots with what to click on.

For plugins which have multiple editions, the Plugin Store allows them to list all of the distinctions between the two editions. Makes perfect sense, since customers would like to know which one is right for them.

However, these details are not available for plugins with just a single edition. This creates a misleading perception for prospective customers, and leads to an unfair marketing advantage.

Here's an example comparing two popular form plugins...

Plugin with One Edition:

Plugin with Multiple Editions:

You tell me... From a marketing perspective, which one of those vendors is more likely to close the deal?

Would you mind making the feature list available to all plugins, regardless of whether the plugin has multiple editions? 🙏

Something that Apple has long done in the App Store is requiring you to log in on at least an annual basis to click on I Agree to their Terms Of Service (TOS) once per year.

If you don't, your app becomes de-listed in until you go in and re-publish them.

This does two things:

1 - It keeps you up to date from a legal POV with any TOS changes
2 - It forces the developer to have a minimum bar of interactivity to keep their plugins listed

I'd suggest doing this only for paid plugins, because I think it's reasonable to ask that if developers are being paid for a plugin, they should be available to at least click through the TOS agreement.

See craftcms/cms#10162.

Hi,

1. I would love to be able to "try" plugins when setting up a new site and register as "technical contact".
2. Then let my clients pay the plugins (they would become owner).

A technical contact would also receive emails about the license etc.

So the store would need to have the possibility that a license can have an owner and a technical contact and maybe a third contact that is responsible for the billing part.

small thing but... in the plugin licensing if there's leading whitespace (say you pasted in a license # and it copied some whitespace before or after), it fails with an "unknown error" -- probably should trim whitespace before validating

Description

With the advent of Craft 4, and dual versions of the plugin store, plugin developers need a way to have separate descriptions and screenshots for major versions of their plugins that correspond with major versions of Craft CMS.

Craft 3 will be around for some time, and as features are added to Craft 4 plugins that the developer may not backport to Craft 4, that means plugin developers can't accurately present the features of their plugins.

Different plugin versions are going to need different descriptions, images, etc. imo. Especially as they diverge more and more. Sites running Craft 3 are going to be around for some time I think.

This will reduce support, and reduce confusion for developers looking at plugins in the plugin store, and allow plugin developers to accurately represent and promote their plugins.

The situation only gets worse when we consider Craft 5 plugins, etc.

We collect invoices in a different email account than our primary login address.
Would be great if craftnet allowed to specify a different email to send invoices to

Right now it is impossible (afaik) to unpublish or delete a plugin from the plugin store.

Currently both the plugin store and the Craft UI site feels very slow, at least on initial load.

It has to load everything upfront, and while it's doing its thing, we're seeing the big fat spinner.

It also doesn't cache things locally, so if you re-load either of them, it has to load everything again.

It would be good if:

• Craft cached the request locally
• The requests actually were quicker (CDN? More caching? Split up requests?)
• The UI could maybe show something other than one big spinner.

Having a visual indication, on the Updates page, as to which updates involve a database migration and which don't. would be hugely helpful. For many sites, this probably isn't a big deal - but for live shops, migrations and when/how to update are a huge issue.

I think in general you would want folks to keep up to date & I think this would help keep folks updating more often/promptly.

Code only updates are much easier for live systems to deal with. DB ones need a lot more testing and, at least sometimes, a full site pause...which can be a lot more difficult to organise.

Description

Using only A-Z in your generated license key files would remove some potentially annoying issues. Yes, not even numbers, given the 0 vs O issue. Same thing for plugin licenses. For readability, you can also add the dash to the allowed list of characters (stripped before parsing, most likely).

In my case, I had to quote a license key in a .env variable because it contains special characters like / and $ that are interpreted differently by different .env reading mechanisms. And worse, they are treated differently by different versions of the same .env reading mechanisms.

However, until recently, Docker didn't even support quoting .env variables:

At some point (~v1.28), docker-compose switched to using dotenv to parse the environment files. Single and double-quoted strings are parsed specially. single-quoted strings can be multiline. Double-quoted strings can have escapes such as "\n" to produce multi-line values.

So I went without the license key in my local dev environment, and then changed it to be double-quoted when they updated the docker compose API to support it. That worked everywhere for a while...

But apparently, some change in the docker compose API caused it to break with really weird-looking errors:

❯ docker-compose -f docker-compose.yml config
WARN[0000] The "J20" variable is not set. Defaulting to a blank string.
WARN[0000] The "UPDON" variable is not set. Defaulting to a blank string.
WARN[0000] The "N4" variable is not set. Defaulting to a blank string.
WARN[0000] The "DAD5D2" variable is not set. Defaulting to a blank string.
Invalid template: "4SPJ1WIXXXXXXXXXXXX/O&*QZ!7+J$6=Z9QJJ4M=56ADQ6T5VHU$UPDON#7NP6GQ38AW/C%OS4NOV6O0/PV158LFTMR!%54IOL6SZ$N4%**E5I/8ZB&$&%XXXXXXXXX$DAD5D2/EZ^YK+IPCCMCGT8XY6B%"

So I had to switch the environment variable to be single-quoted, and now it works. However, this all stemmed from the license key having special characters in it to begin with.

We went through this at my software company; we ended up with a licensing system that generated only uppercase letters, no symbols or numbers after people running into transcription and other such errors.

In Craft's case, it's less about transcription, and more about issues with various things handling .env parsing of special characters differently. With just A-Z and - you are fine.

If it means the license key is a little longer, it's still worth it IMO

The same thing probably applies for things like the generated security key, passwords, etc. Again, the decrease in encoding information can be made up for by length. At least you know it'll work.

It would be helpful in managing licenses if we could sort by the columns in the license table (License Key | Edition | Domain).