There seems to be no way to submit a bug report unless you pay a lot for your account, so I'll post here in hopes of getting dev eyeballs.
I was just starting to poke around, having been given admin access by the account manager. I dismissed a help screen or wizard of some kind... and the screen stayed grayed out. I can interact with the search bar and the options on the left, but the main, white part of the screen remains grayed out and inaccessible.
Things I've tried:
Refreshing the page
hard cache reset
Launching every wizard and help system I can find then dismissing them
Logging out and in
Clearing all cookies and local storage
Using a different browser
The only thing that has worked is to go in and temporary remove the '.active-wizard' class on the main div.app-layout-content using Chrome's debugging tools, which lets me do work during the session, but reloading the page brings me right back to the grayed-out mode.
I'm guessing this condition is rare since I cant' find any mention online, but it's very annoying.
Yonatan from JFrog R&D here
The bug is caused due to an edge case, where one of the projects onboarding flags failed to submit.
This bug will be fixed on next minor release.
You can quickly win this by doing the following:
On your browser console paste the command below and refresh the page.
*no important data will be affected, so no worries
window.store.dispatch('onboardingProcess/RESET_USER_ONBOARDING')
Same issue here with version 7.38.10.
with window.store.dispatch('onboardingProcess/RESET_USER_ONBOARDING')
I get back an undefined as return value.
I removed the corresponding entry content and gave admin rights to another user.
The new user does not have the issue.
It works for the admin at least temporarily.
.app-layout-wrapper .app-layout-content[data-v-2db44934]:before {
content: "";
position: absolute;
width: 100%;
height: 100%;
background: #000;
transition: opacity .2s ease;
opacity: 0;
z-index: -1;
}
Related
Some things I've tried
This extension disables the address bar in "fullscreen mode" (their own implementation), but 1) you can no longer access it 2) you have to re-enable it on every page and page reload.
Adding #navigator-toolbox {visibility: collapse;} to userChrome.css disables the address bar, but this also disables most (all?) keybindings.
Question
Is there a solution that works everywhere, all the time, and still allows me to access the address bar when I want?
You can add the following CSS to your userChrome.css:
#namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
browser {
margin-top: -30px;
}
This simply "hides" the area where the location/address bar normally appears. You can still access it with control-l (or command-l).
However, you won't be able to see other menu items (e.g., addons overflow menu, profile menu, etc.). You can still access them via command-l tab (for page options), command-l tab tab (for addons overflow). This depends (how many tabs to hit) a bit on your personal setup, but the important thing is, they are still available.
My woocommerce checkout page is displaying incorrectly. The 'ship to a different address' is overlapping order details. Also when customers try to process an order, it says agree to terms and conditions, yet there is no checkbox on the page. Please help. The website is fdlamb.com
My reason to ask if you have made some changes or installed new plug-ins, is because in some ocasions plug-ins can change the properties of the template, causing some conflicts. So deactivating all plugs-ins and seeing if that fix the issue can help to know more to what cause the issue in first place.
Also you could just delete your theme and reinstalling, to return to the default CSS, as im seeing your theme doesn't have a lot of customization.
Anyway, i don't know a lot but I have move some CSS to the property of the button to see if it fix itself.
.checkbox {
position: inherit;
top: 7px;
right: 12px;
}
This is how it appears to me with that code. https://i.stack.imgur.com/lfebb.jpg
When my website was in development stage(i.e. when it's on localhost), I was easily able to change section background and effects used to reflect immediately. But when I made my site live on Windows Server 2012 and tried to update section backgrounds, background is not updating. Whenever I add new image to server, it's not displaying in section background. But when I try old uploaded images, all those images display.
I tried following possible solutions:
I changed absolute path's of images to relative path, but not worked,
I cleared wordpress' cache, it also not worked,
I cleared browser cache, it also not worked,
I changed "CSS Print Method option" to "Internal Embedding" from "External CSS" in elementor's settings option, it also not worked,
I'm not using another page builder
I tried templates that also not worked.
I checked this elementor's link also - My changes do not appear online, what can I do?
But above document didn't work for me. Is there anyone faced this issue and have solution for this problem?
For the second time i struggled with this issue for hours only to find the quick fix:
Elementor > Settings > Advanced > CSS Print Method > Internal Embedding
I tried many of your answers, but with no effect.
Style > Background and then select HOVER (Instead of NORMAL) finally did the trick!
This problem occurs just because of "User Permissions". I used Microsoft Windows Server 2012, So I followed following steps:
Go to Control Panel -> System and Security -> Administrative Tools
Search for Internet Information Services (IIS) Manager and double click on it
Then go to sites
Select your live site -> Right click on it -> Edit permisions
Go to Security tab
Click on edit -> Click on "Add..." button for adding new user.
Type Every -> click on Check Names -> Click on Ok
Now you can see "Permissions for Everyone" options below Add and Remove buttons.
Check full control check box and click on apply
And finally click on Ok.
Now elementor can read images. When you'll update image, you need to stay calm and wait to update. It'll take time to change.
Don't make Image Size option full, it'll take too much time to update. Instead of that use 1024x1024. It'll update fast and you can see change immediately.
Just don't forget to remove that user after complete updation of live site. It's bad practice to have full access to live site.
I had a similar problem. I couldn't get images or background colors to show up on my background. I found that the background overlay was set to white with an opacity of 100%. Once I set it to 0% opacity everything worked. I don't remember setting any overlay so it was probably on by default.
WooCommerce: Checkout Page
order_review div overlaps the customer_details div, so that you are unable to fill out your billing information. I've tried playing with the z-index but that doesn't seem to be working.
Here is a link to the product page: http://lifestylesconvention.com/shop/adult-couples-registration/
Please fill out the Form and then continue through to the Checkout page. There you will see what I mean. The div for order_review overlaps the div for customer_details on that particular page, so you are unable to fill out the information in the top section.
I'm pulling my hair out trying to figure this out, lol. I'm sure the answer is staring me right in the face, but I just don't see it. Any ideas would be GREATLY appreciated! :)
Thanks in advance!
I've managed to reproduce the problem in firefox.
I haven't found haven't found a solution yet. But I'm confident the issue is jQuery/javascript. Turn off javascript on the page and the problem goes away. You have about 20 scripts loading on the checkout page and I'm afraid I haven't been able to isolate the one responsible.
Not sure what your skill level is, but a few things I would try:
1. renaming the mecurial js directory (temporarily). About half of the scripts come from this directory. If you rename it, the browser wont be able to load them then you can isolate if any of them is causing the error.
2. The problem seems to occur during an AJAX request for /checkout/pay/. My guess woocommerce is disabling the form while it AJAXs some data but then for some reason doesn't re-enable access. Maybe because it can't find /checkout/pay/ (did you delete this page for some reason?)
Hope this helps...Sorry I couldn;t give a definitive solution - I've gotta to my own work.
Good Luck.
You can mimick the second WooCommerce column (perhaps delete that div from your checkout template as you don't use this for a shipping address?). The float: right clears the billing column. It looked differently in Chrome & Firefox btw, because in Chrome it would be 100% wide and float under the billing field, and in Firefox it sat to the right of that column (which I assume is what you want).
#order_review table.shop_table {
width: 48%;
float: right;
}
Is it ok to hide any thing temporarily or forever using display:none? in dynamic site where many component of page coming from different plugins etc and many time if client doesn't want any thing on page then i use dispaly:none to hide things from page . I do not remove thing from actual source because client can come back ask to enable that thing again.
so what are pros and cons to keep things hide from display:none if i keep any element hide using Display:none forever?
is there any cons in terms of SEO, Screen reader, Accessibility etc?
If the client wants it removed, then create a backup of the page, and post a page that actually has it removed. Don't substitute CSS for actually removing an item. If they decide they want it in the future, then go in and swap your backup for your live copy. If you're dealing with dynamic output (in the case of PHP or a comparable technology) you could stop that particular output with comments so they're never included in the response.
Pros: Very easy to do
Cons:
You are still loading the components on the server side and the client will download them. The browser will simply not "show" them.
Anyone using "view source" will be able to see the values that are "hidden". so never use it to hide sensitive information.
You can simply "comment" these section server side to save a lot of processing on the server, bandwidth, etc.
It's probably also worth mentioning here that some search engines (Google for example) do take stock of hidden content.
Hiding huge amounts of text using display:none; is one of the things many search engines pick up on as keyword spamming.
:)
It makes sense to hide/show stuff with 'display:none' when you do client-side Ajax. This way you can switch views/tabs without doing server round-trip.
It is needed to actually remove something from the page markup when there are security implications. If a user doesn't have the right to see some sensitive information, it shouldn't be there when they click "Display source".
display: none is good to hide things you want visible when people turn css off or use browsers that doesnt support css.
As far as accessibility goes, there is a strong chance that something hidden with "display: none;" will NOT be read by a screen-reader. This may be acceptable if you intend for it to be that way.
A possible alternative to hiding content for screen-readers/css-offers only is to use this class:
.offscreen {
position: absolute;
left: -9000px;
width: 0;
overflow: hidden;
}
And the following HTML:
<h3 class="offscreen">Site Navigation</h3>
For full information on hiding techniques:
http://www.access-matters.com/2005/04/23/screen-reader-test-results/