[Extension Developers] Flarum 1.0 QA Phase Update Period
When opening the composer I see this in the console. Also, maybe unrelated, the insert link button is missing.
TypeError: this.navigator.when((function(){return e.active})).onUp is not a function. (In 'this.navigator.when((function(){return e.active})).onUp((function(){return e.navigate(-1)}))', 'this.navigator.when((function(){return e.active})).onUp' is undefined)
010101 this has been fixed, run composer update
on this dev environment.
We've made a slight adjustment to make tagging new ext versions easier. If you have already followed the above steps, you'll need to change any instances of "0.1.x-dev" to "1.x.x-dev" in your composer.json version requirements for core and bundled extensions. Then, in your extensions, require flarum/core
as ^1.0.0
. Test that it works by running composer update
again.
askvortsov Also, if you're running into issues, don't forget to set minimum stability to dev
in composer.json
- Edited
askvortsov The user table in the admin... I know more work will be done on it. But, water.css is a minimal, clean, modern starter which has elements that look like Flarum. I think the table parts could be used for the admin. Maybe? Maybe not? Maybe not necessary.
What is the recommended version constraint to use in composer.json
?
^1.0.0
Justoverclock The extension using it would need to stop using $.tooltip
to remove the warning.
tankerkiller125 i have no extension that use tooltip in my dev
Justoverclock must be that new one we were talking about over Discord I noticed you were using tooltips for the words
Justoverclock if you click on the file/line number of expand the warning the backtrace might show which extension or part of the source code is responsible.
Did we really include that full GitHub URL inside of our 1.0 dist file? We're saving bytes there and there only to add long URLs in the source code?
Justoverclock the first line in the error is where the error was thrown, which actually shows the code in Flarum that's responsible for creating the error message. You might have to check out the other lines in the error backtrace to see where this was called from.
- Edited
clarkwinkelmann is the same, seems that is related to code, because its a fresh install of a 1.0 version with no extension, so this is not related to me i think
Justoverclock looks like these are coming from subscriptions. Try running composer update
in your local dev environment.
askvortsov this probably fix the error, i have only 2 dev extension installed that can't allow update, so i will try later, now i'm working on it.
p.s. u need to sleep man
Justoverclock He doesn't sleep, I have no idea how he does it but he basically never sleeps.