Pirat I want to replace the original extension with my github branch, but it does not work, because the path is different from the original. I tried to understand the installer-paths but it does not work. https://getcomposer.org/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md
clarkwinkelmann Pirat I suppose you're trying to put your own package in place if a core one ? Your package doesn't need to have the same name or path as the core one you're replacing. Just uninstall the core extension and install your own instead. It can have a completely different package name in both composer and Flarum.
Pirat clarkwinkelmann For example, this extension does not work if I make a fork. ๐ https://github.com/flagrow/telegram I need to change the path in the code under my github repository otherwise the extension settings do not work.
luceos Pirat please stop making forks. Just fork them on github and use the repository vcs method, it was created for that specific reason. You're creating a lot of noise and possible future confusion about which package is actually under active development.
luceos Pirat but for some reason it does not work for me Then get that resolved please. Create a new discussion and explain the errors or issues you face then move towards a solution step by step.
datitisev Pirat As @luceos said, that seems to be an issue on your side. Packagist does not allow forks on their website, so I recommend trying to fix your problem instead of publishing 50 forks. You can also try using a workbench directory, see https://discuss.flarum.org/d/1608-extension-development-using-composer-repositories-path. Do not submit forks of existing packages. If you need to test changes to a package that you forked to patch, use VCS Repositories instead. https://packagist.org/packages/submit
Pirat datitisev I tried but my packages do not change. Can you set an example of how you do it? Otherwise, I'll have to copy the whole engine because I donโt know why itโs not working for me ๐
datitisev Pirat I don't understand. What do you mean, your packages do not change? Make sure you are running composer update after adding the packages via VCS repo or workbench directory, or remove the dependencies and add them once you have the VCS/workbench set up.
datitisev Pirat What folder? The workbench folder? If you call it "workbench", then what it says in the tutorial. If not, then something else...
datitisev Pirat In the workbench folder would be dependencies for composer (package.json deps), i.e. workbench/core for flarum/core. This is to be able to develop your own extensions locally. Please use this method or the VCS Repositories for modifying existing extensions instead of publishing them on Packagist.
datitisev Pirat No. If you need more help, please join Flarum's Discord server to receive real-time responses, so it's easier to give & receive help.