Perfect version 2.8.2. But… 2.9.0 and 2.9.1 unstable?

Hi Joan

Thanks for reaching out.

Just as a general note, there were several update issues recently that were resolved by clearing both caching and optimisation plugins. If this hasn’t been done, please do so.

Let’s start with the Hero issue. I’ll take a look shortly and get back to you. Thanks.

• This reply was modified 6 years, 4 months ago by Andrew Misplon.

Please, try editing the Hero on your homepage. Edit the first frame and click the Text tab. Each line has a style tag added with font-size set to zero:

style="font-size: 0px;"

The inline style tag is the reason the Hero text isn’t visible.

LiveMesh
For the LiveMesh issue, should I check the quien-soy/ page? Can you confirm a page and the exact part on the page I should check? Where are the CSS changes not being respected being stored?

Hi Andrew!

Thank you for worrying about responding soon.

I explain everything in detail in this other link of Imgur, with images and text in English.
However I transcribe you here too.

…

Página INICIO (HOME)

Title widget ‘Livemesh Services’ does not respect my CSS changes made from ‘Additional CSS’ (I do it from there because the plugin allows it and loads before the styles of the website).

However, it is respected on the CONTACT page (página CONTACTO).

…

Página QUIéN SOY

Title widget ‘Livemesh Services’ does not respect my CSS changes made from ‘Additional CSS’ (I do it from there because the plugin allows it and loads before the styles of the website).

However, it is respected on the CONTACT page (página CONTACTO).

…

Página PROYECTOS

Title widget ‘Livemesh Services’ does not respect my CSS changes made from ‘Additional CSS’ (I do it from there because the plugin allows it and loads before the styles of the website).

However, it is respected on the CONTACT page (página CONTACTO).

…

Página BLOG

Widget ‘Livemesh Posts Grid’ now respect my CSS changes made from ‘Additional CSS’ (I do it from there because the plugin allows it and loads before the styles of the website).

But the first time I updated to version 2.9.0 and later 2.9.1 it did not respect my CSS changes. It is something that after a few hours was seen correctly.
That is why I say that the plugin seems unstable and alternates errors.

…

Página BLOG

Plugin: Newsletter by Supsystic (By supsystic.com)
– Widget:
.- Subscribe Form
At the beginning it showed link from the plugin’s own widget. But after a few hours … Don′t link to the form I need. And so I had to remove this widget to put the ‘SiteOrigin Editor’, and incorporate form through a shortcode that allows this newsletter.

…

Página INICIO

SiteOrigin Hero is displayed in the same way as on the CONTACT page.

In fact just like in the rest of the page where I use SiteOrigin Hero. But the funny thing is that in CONTACT page (for now) everything comes out correctly.

This is displayed in the backend. No font style label appears. I’m in HTML tab (before called Text, as you say).

…

Página CONTACTO

SiteOrigin Hero is displayed in the same way as on the HOME page (página INICIO). Where everything is shown correctly.

This is displayed in the backend. No font style label appears. I’m in HTML tab (before called Text, as you say).

…

Página CONTACTO

It is the only page where everything is shown correctly. And it uses the same parameters as the rest of the pages.

That’s why I say that the versions of 2.9.0 and 2.9.1 are unstable. And I’ll have to go back to 2.8.2.

Next I put screenshot of my order when updating plugins. I always leave Page Builder the last one to update. And I don′t use cache plugins or optimization yet.

…

UPDATE PLUGINS WP

1. All In One SEO Pack / Tienes la versión 2.8. Actualiza a la 2.9. / Compatibilidad con WordPress 4.9.8: 100% (según su autor)

2. Livemesh SiteOrigin Widgets / Tienes la versión 2.5. Actualiza a la 2.5.1. / Compatibilidad con WordPress 4.9.8: 100% (según su autor)

3. Simple Author Box / Tienes la versión 2.1.0. Actualiza a la 2.1.1. / Compatibilidad con WordPress 4.9.8: 100% (según su autor) DESACTIVADO NORMALMENTE

4. Widget Options / Tienes la versión 3.7.1. Actualiza a la 3.7.2. / Compatibilidad con WordPress 4.9.8: 100% (según su autor) DESACTIVADO NORMALMENTE

5. WP File Manager / Tienes la versión 3.1. Actualiza a la 3.2. / Compatibilidad con WordPress 4.9.8: 100% (según su autor) DESACTIVADO NORMALMENTE

6. Widgets for SiteOrigin / Tienes la versión 1.3.8. Actualiza a la 1.4.1. / Compatibilidad con WordPress 4.9.8: 100% (según su autor)

7. Page Builder by SiteOrigin / Tienes la versión 2.8.2. Actualiza a la 2.9.1. / Compatibilidad con WordPress 4.9.8: 100% (según su autor) VERSIóN 2.8.2 VA BIEN, PERO NO LA 2.9.0 O 2.9.1, HAY FALLOS EN TEXTO HERO Y COLOR CSS COMPLEMENTOS

…

Greetings! ??

• This reply was modified 6 years, 4 months ago by Joan Morci.

Home Page First Hero
Thanks for checking the Hero widget on the home page. You can see the issue in the code view. https://imgur.com/a/sQEmZiU. Most likely the issue is that the Hero FitText feature is being run while the text isn’t visible. This isn’t the normal result, something is causing this.

Please, test the Hero with only SiteOrigin plugins activated. Temporarily deactivate all other plugins. Does the issue resolve? If not, switch to a default theme, leave all non-SiteOrigin plugins deactivated and re-test, does the issue resolve?

Home Page Services Section Additional CSS
The Livemesh Services CSS change isn’t taking effect due to equal specificity and precedence. Please, see https://imgur.com/a/Qlok6Iw. You can see how your rule is crossed out. This is because both rules have the same specificity but the Livemesh stylesheet is loaded much later giving it the priority. You should either increase the specificity of your rule or just add !important. This isn’t a technical plugin issue but a custom development challenge.

Let’s just work these two specific issues for the moment.

• This reply was modified 6 years, 4 months ago by Andrew Misplon.

Hi Andrew!

I have to clarify that the CONTACT page (página CONTACTO) perfectly shows the text of the ‘SiteOrigin Hero’ widget and the ‘Livemesh Services’ widget (it has the same parameters as the rest of the pages). But the same does not happen with the other pages of the website.

That is why I say that these versions of SiteOrigin are unstable and the errors also alternate with different plugins or add-ons. So I will have to return to version 2.8.2 more stable.

Also, I don′t have any CSS rules applied to headlines/headings. I don′t understand where that rule comes from where the font is at 0px.

Important! for ‘Livemesh Services’… I’ve already used it with other plugins for other occasions, but I don′t understand why on the CONTACT page (página CONTACTO) it does take me well the styles of ‘Additional CSS’ and it does not do it on the rest of the pages.

I still think there is something wrong in versions 2.9.0 and 2.9.1 with respect to 2.8.2 (which goes perfectly… all).

Greetings!
Pd.: Normally ‘Additional CSS’ has priority before the stylesheet of a theme or plugin.

• This reply was modified 6 years, 4 months ago by Joan Morci.
• This reply was modified 6 years, 4 months ago by Joan Morci.

Without a specific error code provided in either PHP or JS, there isn’t one explanation we can offer. All we can do is try to assist you with each item if you would like us to do so.

Hero
We don’t yet know why this is happening on the home page. That’s what the test is for. Please, run the test as described and try to establish a working baseline.

Additional CSS
The last rule wins. https://css-tricks.com/precedence-css-order-css-matters/. Additional CSS is loaded before LiveMesh CSS. Unfortunately, under free support we can’t dive too deep into this. Please, inspect the page using your developer tool. The issue is a custom development one. If you inspect the rule you can see yours isn’t winning. If you inspect the page source, you can see Additional CSS is loaded first, LiveMesh last.

Either make your rule more specific:

.so-widget-lsow-services .lsow-services.lsow-style2 .lsow-service .lsow-service-text .lsow-title {
    color: #ffffff;
}

or use !important:

.lsow-services.lsow-style2 .lsow-service .lsow-service-text .lsow-title {
  color: #ffffff !important;
}

Additional CSS Home vs Contact
On your home page, the Livemesh Services CSS is loaded on line 864, after Additional CSS. On your Contact page, Livemesh Services CSS is loaded on line 57, before your Additional CSS. I don’t know why this is. You’d need to run tests. Is it because of preloading on the home page? If you want to solve this, run the same tests I suggested for the home Hero but leave Livemesh activated. Test with all plugins deactivated except for SiteOrigin and Livemesh. If there is no change, test with all plugins deactivated except for SiteOrigin and Livemesh and a default theme. Try to establish a working baseline and go from there.

• This reply was modified 6 years, 4 months ago by Andrew Misplon.

Hey Joan ?? My last reply was modified at the end with information explaining the home page vs contact page differences. Just thought I’d mention that in case you were following on email only. Thanks ??

Hi Andrew,

Honestly I’m getting dizzy. Starting from the base that I am a designer and not a programmer.

‘Additional CSS’ always has preferences
I think I have not explained well. I have always understood that ‘Additional CSS’ (the native WordPress option: Appearance > Customize > ‘Additional CSS’)… always has preference. After the original CSS styles of the plugin or theme are loaded, except those modified in ‘Additional CSS’.

Although sometimes, it is true, problems can arise and it is necessary to add !important; to reaffirm change. What happens is that I understand that we should not abuse this addition, because it is not good.

If there is something written that is CSS Additional, it has to load before. There is a CSS rule that is a class for ‘Livemesh Services’. It must be the same for that element, throughout the website. I do not have a rule that identifies (ID) a single element.

That’s why I don′t understand these strange differences. They should not occur, in fact they were not in version 2.8.2 or earlier.

Make the rule more specific.
I understand that this is a change that you have added since version 2.9.0. or 2.9.1. Because they are changes that I have seen in other plugins (in the past). But it has not been until now that you have mentioned it as something important to value. In version 2.8.2 it was not necessary.

.so-widget-lsow-services .lsow-services.lsow-style2 .lsow-service .lsow-service-text .lsow-title {
    color: #ffffff;
}

Instead of using !important; I can use a plugin that I already use to change the CSS of pages or entries, something very specific and at my whim: WP Add Custom CSS (by Daniele De Santis)

…

I will do the test that you tell me to disable plugins and theme, but I anticipate that before updating to version 2.9.0 and 2.9.1, I had updated all the plugins and theme, without any problem in the sections that I mentioned (SiteOrigin Hero, Livemesh Services, Livesmesh Testimonial Slider… and the others errors).

That’s why I don′t understand why the bug has to be from my other plugins and current theme? And… can not you see that they have changed from version 2.8.2 to 2.9.0 or 2.9.1? Because I see more people coming back for other errors to version 2.8.2

Greetings!

• This reply was modified 6 years, 4 months ago by Joan Morci.

Please, run the test. It’s really quick and will give us a baseline to work from.

Additional CSS doesn’t always take priority. If you copy a rule and don’t change the selectors, it’ll only win if it loads last. Something is causing the Livemesh and other assets to load late on the home page. Therefore the original CSS rule wins and your Additional CSS rule doesn’t. This is not, to my knowledge, as a result of a change we made in 2.9. Livemesh is a separate plugin with separate developers. If you’d like me to explain CSS precedence further, please let me know.

Developers shouldn’t abuse !important but for the Custom CSS work you’re doing, you can.

If you skim the forums, it might seem like there were a lot of 2.9 update issues. All issues were resolved. We don’t have any open issues from 2.9 that are major or that would cause what you’re seeing.

When the cause of a problem is unknown, we run tests, the understanding will follow. I can’t explain why your assets are loading late on the home page until you start testing. If you want us to run those tests, please, open a support thread on our forum at https://siteorigin.com/thread/ where we can exchange login details.

Thanks ??

Hi Andrew!

I have made a video that I hope will give you subtitles in English, so that you understand that I have done your test:

Please, test the Hero with only SiteOrigin plugins activated. Temporarily deactivate all other plugins. Does the issue resolve? If not, switch to a default theme, leave all non-SiteOrigin plugins deactivated and re-test, does the issue resolve?

Result? Well, you will not like it. Minus to my losing 2 days. Although I appreciate the attention given. It is clear in the video that SiteOrigin Page Builder (2.9.1 version) is a problem. It’s not my plugins problem (all disabled, except SiteOrigin). This is not a problem with my theme (Primer, by GoDaddy), I previewed one of the best recommended themes in the WP repository (Appointment By webriti), and it has the same effect.

When I have the video I will leave a link in a next comment in this forum because if I have to go to another I would have a bigger headache.

Greetings.
Pd.: I made the video (as on other occasions) so you can see that I appreciate your time and it seems something serious to solve.

Super, thanks for trying that. Please, could we have a look? If so, please open a support topic on the forum: https://siteorigin.com/thread/ or email us on support [at] siteorigin.com. We’ll send a quick email for login details and take a look at the issue directly. Thanks.

Ah! I have another website with a loader on the Home page, and with SiteOrigin Hero, and there is no viewing problem (PageBuilder SiteOrigin version 2.9.1).

Thanks for checking.

Please, could we take look? Two options above for reaching out.

Hi Andrew!

Sent to your email, with the subject:
– Perfect version 2.8.2. But … 2.9.0 and 2.9.1 unstable? (video with English subtitles)

Greetings!
Pd.: I can not invest more time in this matter, I hope that everything is well understood in the video.

Hi guys!

I have applied the changes that Alex and Andrew recommended to me by email. Those changes are:
– !important; for some widgets of ‘Livemesh’ see in CSS color that I wanted (from ‘Aditional CSS’).
– Disable FitText in SiteOrigin Hero, to show texts again.

The result is that my website looks good again.

However, I will continue trying to help them as far as I know through email.

Greetings!