As suggested in #604 there might be some language unnecessary redundancy, for
instance between 'es' (Spanish) and 'es-ES' (Spain's Spanish), but we'll figure
that out during the release candidate phase.
I've just discovered that the reason NPM outputs a giant "npm ERR!" message
asking to contact the author of the library and suggesting that it’s most likely
“not a problem with npm itself” when I run "npm run lint" and I forgot a
semicolon is because the return code of an NPM script has to be 0. So this
commit adds "exit 0;" at the end of the NPM commands.
This was proposed in #604, and I now beleive it is actually good to provide
admin/maintainer scripts in the repository.
We still need to clean-up the language list, again as suggested in #604.
Meteor is moving fast these days! This version should make Wekan quicker to
start.
These packages were also updated:
accounts-password upgraded from 1.1.12 to 1.1.13
babel-compiler upgraded from 6.8.4 to 6.8.5
coffeescript upgraded from 1.1.3 to 1.1.4
ddp-server upgraded from 1.2.9 to 1.2.10
ecmascript upgraded from 0.4.7 to 0.4.8
email upgraded from 1.0.15 to 1.0.16
npm-bcrypt upgraded from 0.8.6_2 to 0.8.6_3
stylus upgraded from 2.512.4 to 2.512.5
templating upgraded from 1.1.13 to 1.1.14
tracker upgraded from 1.0.14 to 1.0.15
webapp upgraded from 1.2.10 to 1.2.11
In the Gecko JavaScript engine the Object prototype has a method
'watch()' and 'unwatch()'. This causes strange error messages displayed,
if 'watch' and 'unwatch' are not translated in the chosen localization.
The i18n module cannot handle, if it gets a function for the
translation.
This is a quick fix that removes the 'watch' and 'unwatch' properties
from the Object prototype.
See also: https://developer.mozilla.org/de/docs/Web/JavaScript/Reference/Global_Objects/Object/watch
Meteor was updated to 1.3.4.4, though we haven't modified the code base to
organize it around the new module system, we will still benefit from the
possibility of importing NPM packages dirrectly. From my tests, it also improves
the build time.
Also as https://github.com/meteor/meteor/pull/5841 was merged in Meteor 1.3.4.2,
\#385 is now fixed.
We updated the following packages in the process:
aldeed:collection2 upgraded from 2.8.0 to 2.9.1
aldeed:collection2-core upgraded from 1.0.0 to 1.1.1
alethes:pages upgraded from 1.8.4 to 1.8.6
arillo:flow-router-helpers upgraded from 0.4.7 to 0.5.2
blaze-html-templates removed from your project
cfs:http-methods upgraded from 0.0.30 to 0.0.32
cosmos:browserify removed from your project
cottz:publish-relations upgraded from 2.0.0 to 2.0.6
kadira:dochead upgraded from 1.4.0 to 1.5.0
kadira:flow-router upgraded from 2.10.1 to 2.12.1
kenton:accounts-sandstorm upgraded from 0.1.8 to 0.5.1
meteorhacks:fast-render upgraded from 2.11.0 to 2.14.0
meteorhacks:inject-data* upgraded from 1.4.1 to 2.0.0
meteorhacks:meteorx added, version 1.4.1
meteorhacks:subs-manager upgraded from 1.6.3 to 1.6.4
mquandalle:jade upgraded from 0.4.8 to 0.4.9
softwarerero:accounts-t9n upgraded from 1.1.7 to 1.3.4
tap:i18n upgraded from 1.7.0 to 1.8.2
templates:tabs upgraded from 2.2.0 to 2.2.2
useraccounts:core upgraded from 1.13.1 to 1.14.2
useraccounts:flow-routing upgraded from 1.13.1 to 1.14.2
useraccounts:unstyled upgraded from 1.13.1 to 1.14.2
The click event handler for links in the card display are overlapping:
The general event for opening the link in a new window matches on user
mentions, too. But user mentions cannot be opened in a new window.
We cannot rely on the automatic userId setting of the collection hooks.
If a user is created during invitation, the userId field will contain
the id of the inviting user.
This fix this, by mocking the CollectionHooks.getUserId function and
returning the userId of the new user for all new documents after
creating the user.
The duplicated logic was nessessary because the before.insert hook was
not called before validation, when inserting was initiated on the server.
Using autoValues fixed this problem.
The before.insert hooks have the problem, that they are executed in a
different order if called from the client or from the server. If called
from the client, the before.insert hook is called before validation of
the schema, but if called from the server, the validation is called
first and fails.
Even if a board is public and a user can view it, the user might want to
log in to be able to edit the board.
The button replaces the "public" permission indicator, because it is
obvious (if the user is not logged in and can view the board, it has to
be public).
The board options does not have valid use case (or even valid values) if
the board is not found (either because the user is not logged in or the
board really does not exists).
* UI: Fix title of button
The multi selection button should not get the filter description.
* UI: Add title for all buttons in the header bar
This is espectially important for the miniScreen view, because there
is only the icon and no text next to the button.
