Tagged: ThriveThemes Toggle Comment Threads | Keyboard Shortcuts

  • mischone 3:07 pm on September 6, 2016 Permalink | Flag unresolved

      Tags: , ThriveThemes   

      Baylys verursacht Probleme mit Thrive Content Builder 

      Hi zusammen,
      ich habe mir vor wenigen Tagen den Thrive Content Builder gekauft. Leider läuft er nicht störungsfrei mit dem Baylys-Theme, wie mir der Thrive-Support nach diversen Tests mitgeteilt hat (mit anderen Themes schon).
      Habt ihr eine Idee, wie ich mein Theme behalten kann und trotzdem problemfrei mit Thrive arbeiten?

      Vielen Dank vorab und viele Grüße
      Mischa

       
      • Marc (Support-Team) 2:20 pm on September 7, 2016 Permalink | Log in to Reply

        Hallo Mischa,

        wenn ich mich recht erinnere gab es einen ähnlichen Beitrag bereits im Forum. Ich glaube das JavaScript von Theme und Plugin kollidieren. Du müsstest dies genauer untersuchen und entsprechend deaktivieren bzw. anpassen.

        Bitte habe Verständnis dafür, dass wir für nicht-unterstützte Plugins keinen Support im Forum leisten können.

        Viele Grüße
        Marc

    • Riet 2:13 pm on August 15, 2016 Permalink | Unresolved
      • Riet marked this unresolved
        3:04 pm on August 15, 2016

      Tags: , ActiveCampaign, , ThriveThemes   

      Hi Ellen and Manuel recently I renewed my… 

      Hi Ellen and Manuel,
      recently I renewed my Dorayaki license to 1.0.3, after 2 years (appr.) I am still happy with this theme
      (bytheway, I did not receive a renewal email? Anyway, that’s not what this email is about).
      Unfortunately, there seems to be a conflict with ThriveThemes and/or ActiveCampaign, which I use for emailsubscriptions.
      After filling in Name and Emailaddress, then clicking Send: I get the either the 404-page (on my live site) or the page just renewnes (on a test site, different server).
      Switching to a WP or Genesis theme: subscribing works fine.
      Switching back to Dorayaki: no success (also tried with Dorayaki 1.0.2 activated).
      ThriveThemes advised me to contact you about this. So I hope you have an idea what could cause the problem? Maybe it’s just a minor thing, and it would save me tons of time because I would not have to look for a new theme.

       
      • Marc (Support-Team) 6:06 pm on August 15, 2016 Permalink | Log in to Reply

        Hi @riet,

        unfortunately Dorayaki wasn’t prepared for those plugins. Please understand that we cannot provide help for unsupported plugins in the forum.

        If you’re willing to let me access your site, I’d take a look and maybe can find out what’s going wrong. A link to the live site would allow a first look.

        Best,
        Marc

      • Riet 10:21 pm on August 15, 2016 Permalink | Log in to Reply

        Hi Marc,
        thanks for your quick reply.
        On this page http://website-coach.nl/succes-site-emailreeks you will find two signup forms.
        The first is set up through API connection, the second with HTML (they both connect to the same form).
        Thanks so far :-)

        • Marc (Support-Team) 11:04 am on August 17, 2016 Permalink | Log in to Reply

          Hi @riet,

          do your plugins use the theme at all? It seems, that they overwrite everything. Unfortunately the ID of your HTML tag is missing, it’d placed by the Dorayaki’s header.php. This causes an JavaScript error, which may be the first issue leading to your problem.

          Best,
          Marc

          • Riet 5:49 pm on August 18, 2016 Permalink | Log in to Reply

            Hi Marc, the Thrive Content Builder is for making landingpages, on those pages you don’t see the theme anymore.
            What do you mean by ‘the ID of your HTML tag is missing’?

            • Marc (Support-Team) 1:15 pm on August 23, 2016 Permalink | Log in to Reply

              Hi @riet,

              you can check the source code of your page with a right click on any element and choosing something like “View Source”. Now you’ll see the HTML structure of that specific page, which start with an HTML tag. Yours looks like this:

              <html lang="nl-NL" prefix="og: http://ogp.me/ns#">

              The id attribute is missing, which is used by JavaScript provided by the theme. I think the most elegant solution would be to prevent loading the theme’s Javascript file on that specific page (landing page).

              The general WordPress support can help you with defining an additional condition and function used in a child theme’s functions.php to prevent loading the custom.js file, which is initially added by the following code:

              wp_enqueue_script( 'dorayaki-custom', get_template_directory_uri() . '/js/custom.js', array( 'jquery' ), '1.0' );

              A prepared child theme directory is linked in the Dorayaki documentation.

              Best,
              Marc

              • Riet 12:37 pm on August 29, 2016 Permalink

                Hi Marc,
                does this mean I would have to prevent loading the theme’s Javascript file for every Thrive Themes landingpage I add?

              • Marc (Support-Team) 10:59 am on August 30, 2016 Permalink

                Hi @riet,

                that’s a possible approach. The authors of the plugin can help with a condition to check whether the page is a landing page and in combination with the wp_dequeue_script function you should be able to automate this prevention.

                Best,
                Marc

      • Riet 5:19 pm on September 15, 2016 Permalink | Log in to Reply

        Hi Marc,
        sorry for the late reply.
        This was becoming too complicated for me, so I decided to ditch the theme.
        I enjoyed Dorayaki very much though, but since using Thrive is becoming more and more important I don’t want to have too much technical issues on my mind.
        Thanks for your help!

    c
    compose new post
    j
    next post/next comment
    k
    previous post/previous comment
    r
    reply
    e
    edit
    o
    show/hide comments
    t
    go to top
    l
    go to login
    h
    show/hide help
    shift + esc
    cancel