I followed the Ckan-2.9 theming guide to customize CSS. I followed the process adding a static file (not using webassets). Everything works fine except that the css modification isn't taken into account. I checked several times and can't see where this is coming from. In parallel, I found inspiration on a custom ckan close to what I want to get, but that didn't solve my problem either.
Had someone similar difficulties when customizing ckan's css? What can be the reasons ?
Finally, I found that the modifications made by the extension were active but constrained by the main CSS. For example, the hero image has a max-size constraint that hides the image added with our extention.
Related
I’m trying to fix google maps that work with Pro version of Plugin WP Go Maps.
I see that some classes and styles are not being applied to the map. For example class wpgmza-initialized.
How NOT working html code are look https://ibb.co/QnMZJPf
How normal map are looking on my another project on my localhost https://ibb.co/42NFjZR
It seems that some javascript errors may affect the display of the map. But I can’t understand what exactly needs to be fixed.
How it looks on site
I have fixed jquery error. And it's working
I am new to Mediawiki.
I am not installing it in a server, I only need to run some pages that show CSS content to other people without a wiki account, for example: https://www.mediawiki.org/wiki/User:Xtech2020/Nested_Lists
The problem is: when I log out, CSS stops working, i tried to edit Custom CSS in Global Preferences without results.
I have researched the issue and cannot find a solution, please help.
I noticed that my images weren't crisp, and in the inspector found the piece of code that is making them blurry. But, now I don't know where to look within the actual code to remove this. It's not assigned in CSS. This is a portfolio page. I am using the Avada theme. Any ideas?
Link: http://www.madpeagames.com/gacha-sets/
enter image description here
Looking at your theme's demo I see sharp images and the image code is different. So, the problem is not caused by your theme.
My guess is that you use Jetpack's Photon on your site. Try to deactivate the module and see if this changes anything.
However, image compression is a good thing, especially when using lots of images. Perhaps, if deactivating the Photon module solves the issue, compare the speed of your website with and without Photon. If it makes a notable difference, look in the Photon settings, to see what you could change to solve the issue.
Also, JPEG files (.jpg) may not be the best choice for your thumbnails, because you lose a lot of quality when the image isn't shown at its original size. If changing the settings doesn't help, you could try to use PNG files instead.
If Photon causes the issue and you don't find a way to solve it, while still compressing your images, I would suggest to contact Jetpack support. Alternatively you could try to use a different WordPress plugin for image compression.
I hope that helps. GL!
I've been having some issues while using TTTAttributedLabel. Sometimes a given URL doesn't get coloured as a link nor does it react to touch. However, this is solved by scrolling down and up, so by making the Cell view re-draw. I've looking at the issues in the project's github, but the ones that seemed related were already closed.
Well, the fix was to move the
.enabledTextCheckingTypes = NSTextCheckingTypeLink;
to the awakeFromNib method the custom UITableViewCell.
I came across this thread a few days ago looking to get rid of the stark white background in the DevTools window. One thing led to another and I started in on adding rules for many more elements using the base CSS file (chrome-devtools://devtools/devTools.css) as a guide.
The file being modified can be found in the following locations:
Mac: ~/Library/Application Support/Google/Chrome/Default/User StyleSheets/Custom.css
PC: C:UsersYourUsernameAppDataLocalGoogleChromeUser DataDefaultUser StyleSheetsCustom.css
Ubuntu (Chromium): ~/.config/chromium/Default/User StyleSheets/Custom.css
Midway through, I started running into a problem when modifying rules with very common selectors. The first two I ran into were #main and #toolbar. When adding rules for the more common selectors, if a web page is also using these same selectors (ie. google search), then the rules are applying to those pages or sites as well.
I understand why this is happening. My question is...
Is there a way to only target the DevTools window in Chrome via this Custom.css file without affecting any other domain?
I've tried using the #moz-document domain () and #moz-document url-prefix ()declarations but can't figure it out...
I'm too far in to give up now, so I'm hoping someone can assist.
Here is a screenshot of my progress so far:
Ok, so after digging around, I noticed I actually missed the notice right smack dab at the top of the original article page:
Since publishing this article the Chrome Team have added a unique ID
to the container of the Chrome Dev Tools. The ID is #-webkit-web-inspector(Trac Reference)
So, the fix to my above post is to add body#-webkit-web-inspector to all of your selectors and it works perfect, thus only targeting chromes DevTools window. Also, very important... to those wanting to create a more complete theme, it’s HIGHLY RECOMMENDED to do it via "inspecting the inspector". More info on how to do this can be found here: How do you inspect the web inspector in chrome?
See screenshot below of "inspecting the inspector":