This is searchable archive of our old support forums, which operated from 2012 - 2016. To find out how to get support for your current theme, please visit our support page.

Tagged: 

Builder Issue w/Jump Start — Can't include page slugs w/non-english characters

  • Creator
    Topic
  • #6862
    royeyal
    Participant

    Builder layout won’t load if it’s calling to an external page with a non-English slug.

    I’ve checked it on several sites, including on my local setup:
    If any page slug is not in Latin characters, and is used by any of builder layouts, the builder will throw:
    Uncaught Error: Syntax error, unrecognized expression: option[value=%d7%93%d7%a3-%d7%94%d7%91%d7%99%d7%aa-%d7%a9%d7%9c-%d7%90%d7%a1%d7%98%d7%a8%d7%95]
    on load-scripts.php:2
    It seems to be confilcted with jQuery v1.8.3.
    Changing the external page slug from all those %xx’s to English characters fixes this bug.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Author
    Replies
  • #6865
    Jason Bobich
    Keymaster

    Apologies, I don’t think I’m quite following.

    Builder layout won’t load if it’s calling to an external page with a non-English slug.

    Can you lay this out for me a little more clearly so I can understand exactly what you’re doing? In what context of a layout are you pulling an external page? Do you mean including an external page like in a columns or content element?

    And was this issue not occurring before you updated to Jump Start 1.0.1 (I noticed you put this in the title)?

    #6866
    Jason Bobich
    Keymaster

    … But if this is jQuery issue with passing the text through, I think I’m going to be stumped on that one.

    #6867
    royeyal
    Participant

    Yeah, if an element is calling an external page with a slug of, let’s say %d7, then you won’t be able to access that layout. Try changing the page slug to something like שלום and see what happens when you try to load a layout with that external page.

    Since WordPress doesn’t load by default the latest jQuery, maybe the current build fixes that issue.

    #6869
    Jason Bobich
    Keymaster

    I am able to replicate the issue as you’re describing.

    Did you see somewhere that is a issues others have documented with jQuery?

    #6871
    royeyal
    Participant

    No. I just followed the Webkit debugger output :\

    #6880
    Jason Bobich
    Keymaster

    I got it! Make sure to clear your browser cache completely after you update to Jump Start 1.0.2. I’m working on getting this posted today.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.