Navigation
Archive / Cornerstone 1.0.9. & X-theme 4.2.2. update problems and some solutions (Page 3)
This is archived content. Visit our new forum.
1 2 3
  • Author
    Posts
  • December 9, 2015 at 2:05 am #698693

    Rad
    Moderator
    This reply has been marked as private.
    December 9, 2015 at 5:05 am #698886

    Misho
    Participant
    This reply has been marked as private.
    December 9, 2015 at 6:15 am #698958

    Thai
    Moderator

    Let us know how it goes!

    December 11, 2015 at 6:50 am #702602

    Misho
    Participant

    1. I can confirm that Cornerstone 1.0.11. has sorted out the layout issues. Could be those missing ID’s you are talking about in the changelog. Anyway, it is ok now.

    2. Also, raw content has min height now, so it does not disappear anymore.

    3. Some responsive text settings were lost, but I have restored them manually.

    4. Cornerstone is more responsive and elements previews are not disappearing anymore when changing to mobile view.

    5. CS builder still flickers and jumps up and down when I try to drag and drop an element to some position above ore below the other element. I would like to see it standing still, like Visual composer does. I hope this will be fixed at some time. 🙂

    6. My staging site still cannot load Cornerstone on the homepage, but this is something local and I can live with that.

    All in all, great job guys!

    December 11, 2015 at 12:27 pm #703025

    Jade
    Moderator

    You’re much welcome Misho. Glad we’re able to help. 🙂

    December 11, 2015 at 2:39 pm #703222

    Misho
    Participant

    Hi,

    One question:

    I have increased the php memory, as you have suggested. Cornerstone feels much more responsive.

    However, I have found this error in debug log:

    [11-Dec-2015 20:21:27 UTC] PHP Notice:  Constant WP_MEMORY_LIMIT already defined in /home/progreso/public_html/wp-config.php on line 103
[11-Dec-2015 20:21:27 UTC] PHP Notice:  Constant WP_MAX_MEMORY_LIMIT already defined in /home/progreso/public_html/wp-config.php on line 104

    Does this mean that memory limit is set on some other place too? Is this a conflict?

    I was looking in the debug mode because PHP 7 won’t let me to login. So I have reverted to PHP 5.6 until I find out why.

    December 11, 2015 at 7:43 pm #703547

    Rad
    Moderator

    Hi Misho,

    Glad to hear that it’s more responsive now. And about your question, yes, even your hosting can impose some limit that you can’t override.

    Thanks for sharing 🙂

    December 15, 2015 at 2:11 pm #708033

    Misho
    Participant

    Hi,

    I have just realized that the Widget area element has the same problem that Raw element had before the last update. It has height 0px in Cornerstone, so it cannot be accessed. At least in my case (www.progreso.hr) . Is it just me?

    Thanks!

    December 15, 2015 at 11:18 pm #708521

    Zeshan
    Member

    Hi Misho,

    By default when no sidebar is selected, Widget Area should appear like this: http://prntscr.com/9eqggc. If you select a sidebar, it will show the widgets and thus easily editable by clicking inside it (see: http://prntscr.com/9eqgkf). Though, it may not appear if you don’t have any widget in your sidebar. So it would be best if you add widgets to the sidebar first before selecting it under Widget Area element.

    Thank you!

    December 16, 2015 at 2:07 am #708659

    Misho
    Participant

    I have just discovered that “Swifty bar” plugin has a conflict with Cornerstone.

    https://wordpress.org/plugins/swifty-bar/

    This is the reason why the “Widget area” element is disappearing.

    I have notified the author about it.

    Thanks!

    December 16, 2015 at 2:11 am #708664

    Christopher
    Moderator

    You’re welcome.

    Let us know if you need further assist.

  • Author
    Posts
1 2 3