This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Page Builder Issues

Resolved 10 replies themetheme-vantage
11 years ago · Last reply by Andrew Misplon 11 years ago

Hi, for some reason I’ve started having trouble with Page Builder.

I’ve deactivated all plugins and only reactivated Page Builder and it seems to work for a little bit but then breaks again.

The way it’s breaking is by detaching itself from the main editor and showing as a window below the editor and not actually functioning.

URL: http://www.sculptcoach.com

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

10
  1. Andrew Misplon Staff 11 years, 4 months ago

    Hi Tara

    Please check that Page Builder is running version 1.5.3 and that WordPress is on version 4.0. If this continues then it’s almost always a plugin conflict. It’s unusual for it to occur with only Page Builder activated. Did you re-activate your plugins after de-activating them?

  2. Tara 11 years, 4 months ago

    Hey Andrew, all plugins deactivated, cleared my browsing data, re-logged in, activated only Page Builder plugin, checked that I’m running versions 1.5.3 and 4.0. Still not working :/

    Anything else it could be?

  3. Greg Priday Staff 11 years, 4 months ago
  4. Tara 11 years, 4 months ago

    Hi Greg, I tried it with Chrome, and this is what came up:

    7Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=626&action=edit:22
    Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: only screen and (-webkit-min-device-pixel-ratio: 2), only screen and (min-resolution: 144dpi) post.php?post=626&action=edit:33
    Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=626&action=edit:261
    Uncaught SyntaxError: Unexpected identifier load-scripts.php:88
    Uncaught TypeError: undefined is not a function panels.admin.min.js:1
    Consider using ‘dppx’ units, as in CSS ‘dpi’ means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual ‘dpi’ of a screen. In media query expression: print, not all, (-webkit-min-device-pixel-ratio: 1.25), (min-resolution: 120dpi) post.php?post=626&action=edit:1
    Error in event handler for (unknown): Unexpected token u
    Stack trace: SyntaxError: Unexpected token u
    at Object.parse (native)
    at chrome-extension://boamfheepdiallipiieadpmnklbhadhc/hotkeyListener.js:1:80
    at messageListener (extensions::messaging:340:9)
    at EventImpl.dispatchToListener (extensions::event_bindings:397:22)
    at Event.publicClass.(anonymous function) [as dispatchToListener] (extensions::utils:93:26)
    at EventImpl.dispatch_ (extensions::event_bindings:379:35)
    at EventImpl.dispatch (extensions::event_bindings:403:17)
    at Event.publicClass.(anonymous function) [as dispatch] (extensions::utils:93:26)
    at dispatchOnMessage (extensions::messaging:304:22)

  5. Greg Priday Staff 11 years, 4 months ago

    I have seen an error like that come up before. I can’t remember what we did to fix it though. I think it had something to do with the theme registering its own version of Jquery.

    Can you try temporarily switching to a default WordPress theme and see if that fixes the issue?

  6. Tara 11 years, 4 months ago

    So I switched to Twenty Fourteen and Page Builder was working again, but the home page was blank and the menu was showing all pages.

  7. Greg Priday Staff 11 years, 4 months ago

    I can’t be sure, but this probably means your theme is probably enqueueing its own version of jQuery. This is generally considered bad practice because it can break other plugins. Which theme are you using? Can you contact your theme developer to ask them to look into this.

  8. Tara 11 years, 4 months ago

    I’m using Vantage Pro, Greg.

  9. Greg Priday Staff 11 years, 4 months ago

    Oh, oops. Then I take back what I say ;)

    Do you think you could create a temporary admin account for us so we can take a look at what’s going on? Just send the details over to [email protected] – be sure to reference this ticket so we can keep track.

  10. Andrew Misplon Staff 11 years, 4 months ago

    Hi Tara

    I’ll grab this on email shortly.

    Thanks

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread