Hello, I am trying to clean up the interface on the settings page and remove a div using an extension. When I try the code via the chrome dev console it works but as soon as i try to execute it via an extension running on the page nothing happens. document.querySelector("#nonBatchView > div:nth-ch…

Don’t use javascript to remove UI elements. Your code will break sooner or later. Extensions are in obsolete features.

Thanks @lubos I am aware that this is a deprecated and obsolete feature that could break on system upgrades, but I am running it on the server edition and planning to use it to control the information displayed to end users on certain pages so they dont get confused. Is there any other way to achie…

Ok I seem to have narrowed down that running the command in an extension: document.querySelector("*some_id*").remove(); does not work on the following pages but works on all others: / /summary-view /settings /businesses /users /login Is there anything that was coded differently or prevents …

First of all @E_G , your use case seems strange to me! Why not use User Permissions instead to control what Settings users can access? Also, there’s an idea to lock certain fields from users: [image] Option to Lock the Reference field ideas I request that Manager be give…

Trying to basically dumb down the interface as i want to use it mainly to generate invoices for users. I know the JS method is a hack that will break if the DOM changes in future versions but am happy to stick to a current version to make it work as it is mainly to get users to generate invoices the…

[image] E_G: [Screenshot 2025-01-13 210001] This is a strong use case for form defaults to lock and hide fields: a :lock: button besides each field could set the disabled attribute an :eye: button besides each field could set the display:none property Having thought of this, I believe tha…

[image] Ealfardan: This is a strong use case for form defaults to lock and hide fields: a :lock: button besides each field could set the disabled attribute an :eye: button besides each field could set the display:none property Having thought of this, I believe that Form defaults should be cal…

[image] E_G: I still have no idea why my JS only works on certain pages and not others? It’s mostly one of two things: Not all pages share the same skeleton Some elements might be generated by JS code after loading, this is why you should delay running your JS code until everything else has…

[image] E_G: I only want the users to enter invoices and nothing else. So as suggested just set this as the only permission for those users (see screenshot): [Screenshot 2025-01-13 at 23.49.58]

Yes this is what I have been using to control access but doesn’t quite have the granularity I am after. It does nevertheless do most of the legwork in terms of giving the right access.

Remove Div settings block not working

eko January 15, 2025, 10:50am 14

See:

Topic		Replies	Views
Extensions not working in Summary View	9	545	May 3, 2022
Add custom buttons to sales invoice form	7	650	May 4, 2024
Extension wishlist	0	381	March 10, 2022
Script Extensions are not working	2	76	September 30, 2025
Extentions no longer work in Cloud Version	10	322	December 26, 2023

Remove Div settings block not working

Related topics