Forum Replies Created

Viewing 15 replies - 46 through 60 (of 127 total)
  • Thread Starter Joan Morci

    (@joanmor)

    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.

    Thread Starter Joan Morci

    (@joanmor)

    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 7 years, 9 months ago by Joan Morci.
    Thread Starter Joan Morci

    (@joanmor)

    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 7 years, 9 months ago by Joan Morci.
    • This reply was modified 7 years, 9 months ago by Joan Morci.
    Thread Starter Joan Morci

    (@joanmor)

    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 7 years, 9 months ago by Joan Morci.

    I was willing to ask the same. My main interest is in the subscription form (although I support my colleagues with Jetpack comments as well).

    You have to take this issue as something mandatory because in Europe if this rule is not met, they will fine and there is no money to pay fines. People will remove Jetpack and look for other options…

    Greetings from Spain!

    Thread Starter Joan Morci

    (@joanmor)

    Hi @mndpsingh287!

    If you don´t allow me access to watch the video, it is impossible to see it.

    Greetings.
    PS: It’s easier to upload it to YouTube and put it in hidden mode.

    Thread Starter Joan Morci

    (@joanmor)

    Hi @supsysticcom!

    Fortunately, that code works perfectly, despite knowing it almost 2 months later.

    I was really close to changing the plugin for me and the students of my course at Udemy. Thanks for the code, although late.

    Next time, go directly to your contact form. How long does it take to answer a user …
    a) PRO?
    b) Registered?
    c) Unregistered?

    Being version 1.8.9, the most stable without needing that code. Can not check that you did well in that version and what is the problem in the following ones?

    It’s a shame this situation, because I think your products are very good but the response time is very bad (and that can lower the grade of the product).

    Greetings.

    Thread Starter Joan Morci

    (@joanmor)

    Hi @supsysticcom!

    The WordPress team with respect to this issue, They explain me that recommended to the authors of plugins do not have old versions, as a good habit to always have the best plugin and most updated security level.

    They never mentioned anything to force a maximum of plugins in repository. And speak several emails with them.

    An alternative that you could consider is: balance this so that everyone (plugins) has a minimum of stable previous versions.

    Because you are aware, through your own forum, that there have been problems with the Social Share Buttons plugin, in its vertical visualization on the sides. At least you could show version 1.8.9, to go back to it, since it worked perfectly (it’s the one I use in my Udemy course).

    Greetings!

    Thread Starter Joan Morci

    (@joanmor)

    Hi @supsysticcom!

    At the moment I have no problems with this plugin, but as follows the same pattern of not saving other versions as in the case of another plugin: Social Share Buttons, with which I have had problems and I have not been able to return to an earlier version than it did not have them.

    That’s why I do not understand why you remove these previous versions, when in other plugins you have about 10 previous versions. Can not you balance this so that everyone (plugins) has a minimum of stable previous versions?

    Your Newsletter plugin is a wonder in its design and flexibility of changes. It’s just that I do not want to find future problems where I can not go back to a more stable version. More when I recommend it in my course at Udemy (currently very well rated).

    Greetings!

    Thread Starter Joan Morci

    (@joanmor)

    Hi @mndpsingh287!

    Resolved?

    I did not say it’s resolved. I simply have not been able to respond before. Your team has to do more tests.

    With 60 MB o 80 MB (compressed) files, there is no problem. But with files (compressed) of 145 MB there is a problem, it is also the one that I upload in the example of the video.

    With the ‘Coming soon’ plugin active… the 145 MB upload does not work. Disabling that plugin, yes upload.

    I invite you to do the test, before saying that the matter has been resolved.

    Greetings!

    • This reply was modified 8 years, 4 months ago by Joan Morci. Reason: or 80 MB
    • This reply was modified 8 years, 4 months ago by Joan Morci. Reason: Greetings
    Thread Starter Joan Morci

    (@joanmor)

    You do not have the possibility of going back to an earlier version that surely does go well. If you do not have a team of people to test your plugins, at least, let download previous versions that go well until you can fix the new one.

    Things like that are those that do not allow you to trust your product and less to go to a paid version.

    Thread Starter Joan Morci

    (@joanmor)

    You update plugin without testing enough new functions (you do not say there is new), and you also point out in your forum that it may be the fault of another plugin or theme.
    29-01-2018. Orientation – from horizontal to vertical
    https://supsystic.com/topic/orientation-from-horizontal-to-vertical/

    Well, it’s not like that. Before updating your plugin, the previous version was perfect. It is the fault of the new version of the plugin: 1.9.1. Try to disable all the plugins and the problem persists. And of course, I do not want to turn off the theme because it takes a lot of time to put it as I wanted.

    Also, you do not have the possibility of going back to an earlier version that surely does go well. If you do not have a team of people to test your plugins, at least, let download previous versions that go well until you can fix the new one.

    Things like that are those that do not allow you to trust your product and less to go to a paid version.

    • This reply was modified 8 years, 5 months ago by Joan Morci. Reason: article date
    • This reply was modified 8 years, 5 months ago by Joan Morci. Reason: let download

    Hello!

    I was testing the new update and although it is a little more responsive, it isn´t on all screens.

    However, I decided to choose other words in Spanish that were not so long (title), and separate words (text) when I used slashes, to divide the same group.

    I don´t know why this happens to you, but if you try in English with a big word in the title (12 letters) you will find that it doesn´t work the same on all screens.

    Anyway, thanks for trying.

    Greetings!

    Hi @otto42

    Seen what happened, I think the WordPress repository team should reinforce its security, alerting the user of the change of ownership of a plugin. The most convenient way is your choice, perhaps notifying the security plugins of this new change or forcing the original owners to notify their team (WordPress repository).

    I wrote an article, in Spanish, talking about this topic and some link to this thread.

    Greetings and thanks for everything!

    • This reply was modified 8 years, 8 months ago by Joan Morci. Reason: Add Spanish article

    Hello @otto42

    Ok, I understand. It will also be the main news of the plugin.

    Wordfence is the only one that monitors possible insecurities, plugin or themes? And then… does the WordPress.org team put a solution?

    I ask this because I want to transfer this information to my students of the Udemy course, and also for my own safety to know. And more actively recommend the Wordfence plugin as the right one for WordPress.org

    Greetings!

Viewing 15 replies - 46 through 60 (of 127 total)