- Priority: 0
- Status: Closed
- Theme: Alysum
-
Assigned To:
Fred
- Private: No
- Open Date: 08.09.22, 14:03
- Opened by: Lisa Keeling
- Closed by: Fred
- Closed on: 25.10.22, 16:55
- Reason: Closed
- Comment: Glad to help!
Ticket #23736 - Rev slider settings
Hi Fred, we are unable to add custom settings in the rev slider - the box is greyed and wont permit any changes. Save or cancel wont work - only using escape to exit the screen. Can you help why this is?
Comments
Hi, Lisa.
Open the file
/modules/pspagebuilder/views/css/admin/style.css
find and remove the line 739:
Thanks Fred - I have downloaded the /modules/pspagebuilder/views/css/admin/style.css file but there is no line 739 - it stops at line 700. So i’ve searched the text (z-index on its own has lots of results) so specifically * z-index:9999999!important; * this does not produce any results?
See image attached.
Attachments:
Hi, Lisa.
I assume you are using some external cloud cache service like cloudflare. Just disable it temporary to see the fix is working.
Hi Fred, we do as you know - for some reason (only with the dev site) it causes us problems with caching. I dont understand what you mean though - what fix? Did you see my response regarding there being no line 739 to follow your instructions? Nothing else has been done..
Try to open that file in browser https://dev.londoncopyright.com/modules/pspagebuilder/views/css/admin/style.css
if you do search you will find the code that I asked to remove .ui-widget-overlay… That means that code is not removed from the file OR it’s removed, but we are seeing cached version.
Hi Fred, I have switched off caching - but nothing changed. I have downloaded the style.css file again and searched * .ui-widget-overlay * this text is on line 641 (not sure of that matters or if its the correct text you are suggesting we remove). Attached file - are you suggested I remove everything inside the red box and that will solve the problem?
Is there ever a solution to the caching problem without removing cloudflare?
Attachments:
Also, I have checked the same file from our live site (where the above problem doesnt happen and on line 640 that text is there) so I am not sure about removing it for that reason..?
To fix the problem, you just need to remove that code
Thanks Fred - you can close this ticket too