Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feature request: quickE should be disabled by default

See original GitHub issue

I’m submitting a … [x] feature request

…about [x] edit experience / UI [x] admin experience UI

Current behavior By default, the quickE menu is enabled so content editors and admins see these buttons.

Screen Shot 2021-06-13 at 5 07 39 PM

Expected behavior I think the quickE should not appear unless me, as a developer, add it to the site to include that functionality.

Instructions to Reproduce the Problem N/A

Why change the behavior? I always hide these via CSS. I’ve now recently discovered that they can be disabled on the page via the template, like so:

<div @Edit.Attribute(“quick-edit-config”, new { modules = new { enable = false }})>

However, this involves editing most of the templates to include this code. I wish that the quickE buttons were disabled by default because my content editors nor I ever use them.

Alternatively, instead of making it disabled by default, another option could be a simple toggle that turns it off for the entire portal. That way it could stay enabled but then we can turn it off from one place, rather than hide it via CSS overrides or update all the razor templates.

Your environment

  • 2sxc version(s): [all]
  • Browser: [all ]
  • DNN: [all ]
  • Language: [any/all ]

Anything you would like to add I’ve spoken with a few other developers who use 2sxc and everyone hides them because they result in accidental clicks. This seems like a feature that should be opt-in, not opt-out.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

iJungleboycommented, Oct 6, 2021

This is planned somewhere down the roadmap, but it’s quite complex to get the current state into the skin, so it’s not a priority yet (as there is a workaround, even if not ideal).

jeremy-farrancecommented, Oct 6, 2021

Given the amazing “Settings” additions in v12+ - I think this is a great candidate for getting fixed and making everyone happy via Default, Global, Site, etc. settings. Hopefully @iJungleboy reads this, agrees, and feels its is quick, logical, and maybe even easy addition?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Feature Request - Improvement to "Quick Migration"
1. Please add the ability to choose the network for the destination VM location. 2. The "Delete source VM" option should be DISABLED...
Read more >
Ability to disable single default features · Issue #3126 · rust ...
In that case wouldn't it be possible to disable a default - having the same behavior as if you explicitly listed all defaults,...
Read more >
I need to disable QuickInfo in C# (all all editors)
We did some research about this issue. We find that it is default that there have no option to disable the Quick Info...
Read more >
Customizing Feature Request and Feedback Attributes - Savio
The Importance attribute is enabled by default. To disable it: 1. Click into the “Importance” attribute. 2. Uncheck the “Enabled” checkbox.
Read more >
Add the ability to Disable Smart Query by default
Currently, using JIRA's quick search automatically defaults to use a Smart Query search:
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found