https://scaleyourapp.com/ here is the website url.
Okay, thanks. I’ll try.
It’s gone.
Thanks
Yes, re-tested it. Works fine for Chrome. For some reason, it’s not displaying changes for the logged in session. I tested in a private incognito session. Works fine.
Thanks
I don’t think it’s the hummingbird cache. Reason being, the changes done in styling immediately reflect in firefox & are consistent.
The only issue I am facing is with chrome browser.
Even if you check right now, I see the desired font styling in firefox but not in chrome.
Nope, it doesn’t work in chrome. I’ve tested right now. The font is again “light”
Definitely some issue with chrome.
I’ve removed the right click disable plugin.
I re-tested, several times clearing the cache. It’s working in chrome right now.
Changes appear a little inconsistent. I see the regular font within the article but not on the website home page. Could you please confirm it from your end.
I’ve disabled the right click.
For some reason I see the changes in Firefox but not in chrome. I cleared the cache & re-tested. Cleared the cookies from the browser too. Doesn’t work in chrome. Screenshots of firefox & chrome attached.
I picked the font style to “regular” & it’s comparatively thicker in firefox. I want just like it looks in Firefox.
Did you check in chrome by any chance?
Thanks
Shivang
Sure, I’ve added the details in the private section.
I tried changing from Appearance -> Theme Settings -> Styling. Doesn’t work from there too.
Hi,
Thanks for the reply. I see the changes in the customize UI panel. But for some reason, the changes don’t reflect on the live website.
Here is the url https://8bitmen.com/what-is-a-bit-a-byte-a-deep-dive/
Please have a look. Screenshots attached.
Regards
Shivang
It worked. Awesome 🙂
Thanks
Can you tell me where in the theme settings shall I change to limit the number of articles loading up on the home page?
I tried changing Blog Posts Per Page under Blog Setting but it doesn’t seem to work. The default value is 12 I guess.
Alright, thanks & what about the first issue?
Never mind, please ignore it. It got fixed;