-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to add attribute: users and team names are not recognized #63
Comments
I just installed the Custom Attributes plugin on our server and we experience the same issue. Neither user nor team search return any results. `Request Redirect Response Request Response The get request contains the following request data (which I think looks fine) and no mime-type is set. When I compare this request to the request data which is sent for a successful user search request, I see that there a mime-type is set for the request: "application/json". The server log shows the following entry when entering text in the respective text boxes: |
If it can help, I personally figured that after managing to migrate to a subdomain URL instead of subpath installation, the plugin worked: |
@gabrielctn thanks for your suggestion, this is highly appreciated. We are already using a subdomain installation for our server but apparently combined with a subpath 🧐 I will test your suggestion. |
You are most welcome ! |
@gabrielctn I am flabbergasted! Removing the subpath in the SiteURL did indeed resolve the issue for me as well! Again thank you! I hope your tip also helps the Mattermost team to fix the issue :) |
This issue is there on v1.3.1, could a fix be considered? Multiple organizations I work with tend to run proof of concept or small deployments using subpaths, some of which remain under a subpath for the long term, some moving to a subdomain over time |
Hi,
I am unable to add a custom attribute.
I want to set the team name, but it is not recognized (it is registered as DSIMB in mattermost), neither are usernames (I tried with and without "@").
Here are versions infos (I installed mattermost via docker-compose):
(I have Mattermost EE, without license key, the edition is not activated)
The text was updated successfully, but these errors were encountered: