options are showing differently in context menu of Modern script editor web part

[RamKalyugi]

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

I am using Modern Script Editor web part package file mentioned here.

Issue description

I have 2 sites: site A and site B.
I have deployed "Modern Script Editor Web Part" in both sites with the same package version "1.0.0.14" at the site collection level only.

URL to webpart - https://github.com/pnp/sp-dev-fx-webparts/blob/main/samples/react-script-editor/README.md

When I go to site B and click on 3 vertical dots from the site contents page in SharePoint online classic site, It shows "No Actions" as part of the context menu.

I want to see the same in site A.
Please note both sites share the same classic site template, the same package version, and the same permission level for the user, but still it shows "Details" as a context menu option in site A, but I want to see "No Actions".

I have attached the images.

Can you please help me on this? Thank you!

[Amey-MSFT]

Hello @RamKalyugi,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[Tanddant]

Do you by chance have custom NoScript enabled on one site and not the other?

The Modern Script Editor Requires Custom Scripting to be enabled

[RamKalyugi]

@Tanddant Yes, custom script is already enabled, and the code I injected is working fine already.

[Amey-MSFT]

Hello @RamKalyugi,
Can you check if the web part wasn't deployed at the site level in Site A in addition to site collection level.
Or have you used any custom actions to alter the context menu?

[RamKalyugi]

@Amey-MSFT web part is deployed at the site collection level in both sites. I feel the web part is corrupted in site B. The immediate fix I am thinking of is to redeploy the web part.

Thank you!