[$500] Client Manager - no navigation when embedded

[jmgasper]

@atelomycterus - When embedded through the mfe embed, the Client Manager role should be restricted:

1. No ability to start a new thread or post. They can only respond to posts created by members. They can add attachments in a response.
2. No ability to announce
3. No ability to click a handle to navigate to the user's profile
4. No ability to navigate outside of the group page in the embed
5. No Delete capability for messages
6. No ability to unwatch
7. No ability to navigate to the challenge via the challenge link.

[jmgasper]

Challenge https://www.topcoder.com/challenges/4f9fcc94-a37b-4981-861b-2117fa51be5e has been created for this ticket.

This is an automated message for ghostar via Topcoder X

[jmgasper]

Challenge https://www.topcoder.com/challenges/4f9fcc94-a37b-4981-861b-2117fa51be5e has been assigned to obog.

This is an automated message for ghostar via Topcoder X

[atelomycterus]

@jmgasper I've implemented almost all requirements but I have a few questions.

1.No ability to start a new thread or post. They can only respond to posts created by members. They can add attachments in a response.

• 'No ability to start a new thread or post' - Fixed.
• 'Topcoder Member'/ 'Vanilla Member' can't upload any files from Editor. All Topcoder roles are synchronized when users are added in a group by challenge forum processor or user are logging in Vanilla. So we need to configure 'Client Manager' with the 'upload files' ( the "CHALLENGES FORUM" category, check "Upload files" for comments ) in Vanilla.
  'Client Manager' roles:
  

2.No ability to announce - Fixed.

3.No ability to click a handle to navigate to the user's profile - Fixed.

4.No ability to navigate outside of the group page in the embed
What about any links within body of a thread/comment? Should they be disabled?

5.No Delete capability for messages - Fixed.

6.No ability to unwatch - Fixed.

7.No ability to navigate to the challenge via the challenge link.
Did you mean this link?.

What about voting buttons for threads/comments?

PRs

Please apply PRs:

#653
topcoder-platform/forums-groups-plugin#98
topcoder-platform/forums-plugins#108

topcoder-platform/forums-topcoder-editor-plugin#28 - Fixed a minor issue (an image icon was displayed instead of an upload icon, this issue due to upgrading to EasyMde 2.15 ):

Thanks!

Testing

Client Manager : the main site vs embedded

[jmgasper]

4 - No, we can leave normal links as-is for now, thanks

7 - Yes, and we also have this link, but not sure if that shows in the embed:

[atelomycterus]

@jmgasper I did some tweaks for a group page (don't duplicate Group name/Category name in a breadcrumb when embedded, etc). Please apply PRs:
topcoder-platform/forums-groups-plugin#99
#654

Thanks!

7. The group description field is stored in Markdown format.
   

The body of discussions/comments are also stored in Markdown format. It's formatted to html before sending to a client. We can fix it different ways:

• on client side using css + js
• on backend side:
  -- Format from markdown to plain text but text formatting will be lost.
  -- Format text from markdown to html, replace urls with href='' and send the view to a response.

User can add any links, use @topcoderHandler (which is clickable) in any post and can navigate outside of the group page/thread page.

How strictly do you want to control user behavior and prevent navigating outside of a group page/thread page? If it's fixed on the client side, user can open the console and see a link, copy it and navigate outside.

[jmgasper]

@atelomycterus - I'm not quite sure how fine-grained we want to go. Let's deploy this and get it QA'd and we'll see what further tweaks Topcoder wants to make, thanks.

[atelomycterus]

@jmgasper Agree, let's deploy and get a feedback from Topcoder. Thanks!

[jmgasper]

@atelomycterus - This is deployed now:

https://platform.topcoder-dev.com/self-service/work-items/85dfab33-5e0d-4abb-b479-e1b93b032b78

I'm still working on testing with a Client Manager role. Hope to have that done by tomorrow, thanks.

[atelomycterus]

@jmgasper 1. Now one Vanilla access token is used for all Vanilla REST API calls. This is incorrect. I generated it for nursoltan-s to help testing MFE. The access tokens’ permissions are reflective of the permissions of the user who generated the token.
This token should be revoked for security reasons.

VANILLA_ACCESS_TOKEN is public and hard-codded on all config files (PROD, DEV):
https://github.com/topcoder-platform/micro-frontends-self-service-app/blob/develop/config/dev.js,
https://github.com/topcoder-platform/micro-frontends-self-service-app/blob/develop/config/prod.js.

We don't allow Vanilla members to generate Vanilla access tokens and remove this link from User profile in Vanilla Forums.
We need to support calls Vanilla Rest API (/api/v2) with Topcoder access token.
Now Vanilla REST API works only with Vanilla access_token. Before that, we used it only with a challenge forum processor.

Let me know if you have any questions.

2. Which account with 'Client Manager' role can I use for testing?

Thanks!

[jmgasper]

@atelomycterus - I added TCConnCopilot as Client Manager to dev challenge 85dfab33-5e0d-4abb-b479-e1b93b032b78