I have Earl/ThreadChooser/_files/Earl/ThreadChooser/Image.jpg and Earl/ThreadChooser/_files/Earl/ThreadChooser/clTrigger.js files.
<xf:js src="Earl/ThreadChooser/clTrigger.js" addon="Earl/ThreadChooser"/>
but how do...
for developers who use docker,
I'm sharing this zsh function.
You can add this to .zshrc
if [[ ! -a composer.json ]]; then
<<EOF > composer.json
I was able to complete the importing process on @eva2000's centminmod without a single issue. It has a great community support. I recommend you to try that too.
ah yeah, makes sense. thanks for the heads up @Lukas W.
php cmd.php xf-addon:upgrade-step --id=Earl/PhoneTest --version=1000012 --step=1 returns Console Tool string in terminal.
And it doesn't do anything.
even php cmd.php xf-addon:upgrade-step --version doesn't show anything but that...
Hey @Chris D I hope it wouldn't do any harm If I ask a related question here, from you.
The user has installed the version 1000011
Then, the next release (1000012) adds a new installStep4()
So I executes that step from upgrade1000012Step1() too
lol, I thought I was alone. Then again, I used to think that they will change when executing the bump-version command (or they will get corrected when executing the build-release). but it only changes the add-on.json file right?
anyway it's still safe to continue to keep releasing updates but...