Nigbey

Ok, I think that’s somewhat fine, tried it and it can pass! 😉

Thanks a Lot again, and when you have news on solution to “visual editor” in SO CSS, let me know here so we can close the topic finally :))

I’ll add some more tags on this topic to try to cover all that WE covered.

I’m afraid we didn’t understand each other.

Setting the mobile width, will just set the point to where menu collapses into 3 horizontal bars and where ALL pages on the site start arranging text under picture under text and so on….

My Mobile Width setting is currently set to 780px and I am happy with it since it does great job for all of my pages on the site, except one page:
http://centroprojekt.com/altro-zidovi/

If you’re on this page, and start reducing the width of the page slowly, you’ll see how all the text starts exceeding the height of the pictures near them, UNTIL it collapses nicely around 780px into one-beneath-one manner.

So, is there a way that I could set something so all pages continue to “collapse” at 780px, but this page (http://centroprojekt.com/altro-zidovi/) to start collapsing higher, at 1100-1200px for example?

Ok, sry, I didn’t see that you sent me another message when I sent my last message.

I deactivated ALL other plugins except SO CSS, and “visual editor” button still remains INactive.

Also, when I click on it with JS console opened, it gives me this red message:

Uncaught TypeError: Cannot read property ‘length’ of undefined css.js:428

Ok, man, until I found how to open console hehehe….

Here are 3 screaming lines that appeared:

Uncaught ReferenceError: module is not defined
jquery.spin.js:40 Uncaught ReferenceError: require is not defined
12css.js:428 Uncaught TypeError: Cannot read property ‘length’ of undefined

Ok Misplon,
EVERYTHING you said and directed me to – WORKS FLAWLESSLY.

I went on DiffMerge, uploaded original Styles.css and mine edited Styles.css, found all differences and pasted them carefully into SitOrigin’s Custom Css plugin, paying special attention to those “{” and “}” not to miss any, but it’s so hard to miss anything there cause this plugin actually speaks like a human if something is missing or wrong!!! :))

Then, when all is pasted, I went on Tablet and….
voila! – problem solved!!! and my sub-menus are NO longer expanded by default.
———————————————

Regarding Menu collapsing glitch (I measured it now, it happened on 750px screen width), I reduced horizontal padding to 21px as it is just a bit under the max value (22px) where problem STOPS showing:

.main-navigation ul li a {
padding: 18px 21px;
line-height: 2.35em;
}
——————————————————————-
So all in all, next thing I did is:
I went in Jetpack’s custom css sheet (since that’s the Custom Css plugin I used up to now just to edit my contact 7 forms) copied and pasted everything into SiteOrigin’s Custom Css sheet, and then deleted everything from Jetpack’s Custom Css plugin sheet. So I emptied everything that was unnecessary, so i don’t double stuff.

Then I went on Appearance > Editor > Styles.css,
and replaced edited (current) Styles.css with ORIGINAL one from
https://themes.svn.wordpress.org/vantage/1.4.2/style.css,
so NOW, I can be sure that:

1.I have SiteOrigin’s ORIGINAL Styles.css file running, as it should be done in the first place, and all additional coding is in SiteOrigin’s Custom Css plugin sheet.
2. Everything is now nice and organized, and
3. When SiteOrigin’s theme “Vantage” updates, I am sure that ALL my styling will remain as I want it to be, since now ALL my styling is now located in Plugin that is separate from Theme and it’s updates.

I am deeply grateful for your help.
And I’m even more grateful on education that you gave me throughout these threads!

Thanx a lot!

Well I already installed SO plugin, since it does the same job – but it’s SiteOrigin’s. Huge difference in my opinion!
Thanks man, I usually end up with NObody to reply on my threads by other Plugin/theme authors, but this is really awesome!

I’ll keep you updated about this submenu problems ASAP!

Yes, exactly that! – Luckily we’re here before the catastrophy! 🙂

One thing:

this thing for example: .main-navig…. uses “.” before – as a “class” mark, right? And I noticed that If Im going to make changes in Custom CSS using the plugin you suggested – I will need to use “#” instead – as you suggested #colophone….

Is that correct? I should use that for EVERY line (that starts with some class and I assume everything does start like that) that needs to be inserted into custom css?