GitLab

log: removal of comments by page admins

See merge request riseuplabs/crabgrass!292

This might indicate spam and we should investigate the user who created the comment.

fix: check for page before testing page_policy

See merge request riseuplabs/crabgrass!291

Feature/block spam

See merge request riseuplabs/crabgrass!290

This way we can see how many false positives we get.

We have seen a lot of spam comments on public pages recently.
They insert links - probably to increase search engine ranking of the linked sites.

In order to prevent this we disallow comments with links on public pages
for users who have no other access to the page than it being public.

feature: allow page owners to remove spam comments

See merge request riseuplabs/crabgrass!289

changes: add 0.6.4 release

See merge request riseuplabs/crabgrass!288

rails: do not require active_storage and action_cable

See merge request riseuplabs/crabgrass!287

Need to require all railties separately so we can pick from them.
We are not using the two so better not require them either.

fixes #298.

Fix slow member removal

See merge request riseuplabs/crabgrass!286

Merge master

See merge request riseuplabs/crabgrass!285

The more verbose messages still make sense.
Letting users remove themselves from pages owned by groups aswell.

We used to build access_ids from all user participations
rather than only the ones granting access.

This lead to pages showing up in page lists that the user
did not have access to anymore.

Only take into account user_participations with access level set
for the access ids. The other user participation serve to
track page visits, watch the page or star it.

This reverts commit 17911b99.

Fix: no nil values in group list - improve queries

Closes #295

See merge request riseuplabs/crabgrass!283

fix: actually seed data in context controller

See merge request riseuplabs/crabgrass!284

method_defined? returned false. What we want is respond_to?

Fix: no nil values in group list

Closes #295

See merge request riseuplabs/crabgrass!282

fix: issues noticed on staging server

See merge request riseuplabs/crabgrass!281

Associations do not accept the reload flag anymore.
So in surveys controller
`@survey.responses(true)`
would become
`@survey.responses.reload`

But since we are not allowing updates to surveys anymore there is no need to reload anyway.

RankingPoll was missing a require for `borda_vote`.

Cleanup controller commons

See merge request riseuplabs/crabgrass!280

test: bring back transactional fixtures in js tests

See merge request riseuplabs/crabgrass!277

turn off transactional fixtures for that test for now.

With transactional fixtures we keep seeing Mysql Errors
without any error message in the test logs.
https://github.com/brianmario/mysql2/issues/1019 seems related.

They also broke group settings test occasionally.

fixtures :all in test_helper takes care of this for us.

fix: symlink fix - this time with a test

See merge request riseuplabs/crabgrass!279

fix: follow symlinks to find dir for theme

See merge request riseuplabs/crabgrass!278