Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest update points to a new repo #7

KatieMFritz opened this issue Oct 30, 2019 · 2 comments

Latest update points to a new repo #7

KatieMFritz opened this issue Oct 30, 2019 · 2 comments


Copy link

@KatieMFritz KatieMFritz commented Oct 30, 2019

Mainly leaving this here for other people! If you see versions 2.0.0 and later in your Craft Updates, note that Composer will actually install this repo instead:

The setup is very different and you'll need to manually migrate your footnotes.


This comment has been minimized.

Copy link

@carlcs carlcs commented Nov 4, 2019

Sorry about the confusion. The update that showed up in your Craft CP is from a completely different plugin, that you should not apply if you want to keep using this plugin here.

The root of the issue is that both plugins are using the same plugin handle footnotes, which the Craft plugin store is using to match plugins to repos. This wasn’t a problem until now because both plugins weren’t registered with the store, and in this case Craft update service doesn’t care about the handle and shows the releases from the matching Composer package name.

This changed in the moment @dueddel submitted their plugin to the store. It became the one and only plugin with handle footnotes! 😎

I now went ahead and changed this plugin’s handle to footnote, so the plugin store accepts them as individual plugins. I also changed the package name to carlcs/craft-footnote and the repo name to craft-footnote to avoid further confusion.

To continue using the plugin and get on its “updates track” you need to update to 2.0.0 beta 5 by doing the following.

  1. Uninstall the plugin in CP > Settings > Plugins
  2. Install it again from the Plugin Store, or from the command line with the following commands.
    > composer require carlcs/craft-footnote:^2.0.0-beta.5
    > ./craft install/plugin footnote
  3. Update the plugin handle in your custom Redactor configs
    "plugins": ["footnote"]

This comment has been minimized.

Copy link

@dueddel dueddel commented Nov 4, 2019

Hi @carlcs, I'm sorry for any inconvenience being caused by my plugin! … Obviously you managed that issue professionally. 🤘 Great job!

My apologies also to you, @KatieMFritz.
Carl is absolutely right, I recently submitted my footnotes plugin to the Craft Plugin Store. Because of the same handle Craft is mixing things up a bit. Hope you didn't get into big trouble? 🖖

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.