Forum Replies Created

Viewing 15 replies - 1 through 15 (of 21 total)
  • Thread Starter Ben

    (@cyberliciousben)

    Ok, thanks. Just trying to make sure we’re not going to duplicate data.

    Thread Starter Ben

    (@cyberliciousben)

    I found this: https://www.ads-software.com/support/topic/should-i-connect-sitekit-to-google-tag-manager-and-analytics-in-the-same-time/.

    Ok, so, Site Kit is only inserting this code:

    gtag(“config”, “G-XXXXXX”);

    …because GTM’s container is not configured for GA4 Configuration yet. When we configure GTM’s container for the GA4 configuration tag, Site Kit should remove that line for Google Analytics, correct? We will soon find out.

    Disclaimer: This support submission has now turned into my thinking out loud. LOL

    Ben

    (@cyberliciousben)

    Ok, will do. Thank you, Michael.

    Ben

    (@cyberliciousben)

    @constantcontact, did you receive an email? That’s the issue. Since you don’t hit the list, you don’t receive an email. We have no idea who is signing up for our seminar. We use the plugin because we can attach thank-you pages to inline forms.

    It’s form 8006 so when I go look at the associated list attached to it, you are not there. The plugin shows:

    Contact Count: 0

    We have to make a decision pronto because this seminar is coming up. We also have clients that are using this, but I have not checked them. I am going to ask their project managers how their lists look, and if they see any drop off.

    Ben

    (@cyberliciousben)

    sorry, @spyderbytemedia, I did not mean to hijack this as your issue was extremely similar to ours. We’re just not receiving any debugging information.

    Ben

    (@cyberliciousben)

    The form we’ve been testing is over here.

    Ben

    (@cyberliciousben)

    My apologies. I haven’t done this implementation in awhile. That’s the Universal Code used for the Exit Intent form which works. I removed it to troubleshoot the plugin.

    I rolled the plugin back to 1.12 and 1.13, and the form submission still doesn’t hit CC. I receive the thank-you page, but my email doesn’t hit the list so I do not receive any emails.

    It’s back to 1.14.

    • This reply was modified 1 year, 7 months ago by Ben. Reason: clarification
    • This reply was modified 1 year, 7 months ago by Ben.
    Ben

    (@cyberliciousben)

    P.S.S. Please reference case #30901036. I’ve taken over for our side since that case has gone nowhere on your side. Let’s play!

    Ben

    (@cyberliciousben)

    P.S. Debug Logs are blank even though it’s turned on within the Settings > Support tab.

    Ben

    (@cyberliciousben)

    Hello, did anything get resolved? Would 2.0.0 fix this and if so, can I have it?

    Everything seems to work on the user’s end, but nothing is going to Lists on Constant Contact’s end.

    signup-form-widget.min.js defintiely belongs to CC, and it seems it can’t be reached on its CDN. This is what I’m getting:

    jquery-migrate.min.js?ver=3.3.2:2 JQMIGRATE: Migrate is installed, version 3.3.2
    DevTools failed to load source map: Could not load content for https://static.ctctcdn.com/js/signup-form-widget/current/signup-form-widget.min.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE
    signup-form-widget.min.js:30 Div for inline form "-----" is missing. Was inline code installed?
    e @ signup-form-widget.min.js:30
    f @ signup-form-widget.min.js:31
    (anonymous) @ signup-form-widget.min.js:31
    each @ jquery.min.js?ver=3.6.1:2
    (anonymous) @ signup-form-widget.min.js:31
    c @ jquery.min.js?ver=3.6.1:2
    fireWith @ jquery.min.js?ver=3.6.1:2
    s.<computed> @ jquery.min.js?ver=3.6.1:2
    (anonymous) @ signup-form-widget.min.js:30
    c @ jquery.min.js?ver=3.6.1:2
    fireWith @ jquery.min.js?ver=3.6.1:2
    l @ jquery.min.js?ver=3.6.1:2
    (anonymous) @ jquery.min.js?ver=3.6.1:2
    load (async)
    send @ jquery.min.js?ver=3.6.1:2
    ajax @ jquery.min.js?ver=3.6.1:2
    s.ajax.s.ajax @ jquery-migrate.min.js?ver=3.3.2:2
    loadConfig @ signup-form-widget.min.js:30
    i.main @ signup-form-widget.min.js:31
    (anonymous) @ signup-form-widget.min.js:31
    window.ctctOnLoadCallback @ signup-form-widget.min.js:1
    l @ signup-form-widget.min.js:1
    (anonymous) @ signup-form-widget.min.js:1
    c @ jquery.min.js?ver=3.6.1:2
    fireWith @ jquery.min.js?ver=3.6.1:2
    l @ jquery.min.js?ver=3.6.1:2
    i @ jquery.min.js?ver=3.6.1:2
    dispatch @ jquery.min.js?ver=3.6.1:2
    y.handle @ jquery.min.js?ver=3.6.1:2
    load (async)
    add @ jquery.min.js?ver=3.6.1:2
    s.event.add @ jquery-migrate.min.js?ver=3.3.2:2
    (anonymous) @ jquery.min.js?ver=3.6.1:2
    each @ jquery.min.js?ver=3.6.1:2
    each @ jquery.min.js?ver=3.6.1:2
    Ee @ jquery.min.js?ver=3.6.1:2
    on @ jquery.min.js?ver=3.6.1:2
    send @ jquery.min.js?ver=3.6.1:2
    ajax @ jquery.min.js?ver=3.6.1:2
    s.ajax.s.ajax @ jquery-migrate.min.js?ver=3.3.2:2
    m @ signup-form-widget.min.js:1
    (anonymous) @ signup-form-widget.min.js:1
    (anonymous) @ signup-form-widget.min.js:1
    signup-form-widget.min.js:30 Div for inline form "-----" is missing. Was inline code installed?
    e @ signup-form-widget.min.js:30
    f @ signup-form-widget.min.js:31
    (anonymous) @ signup-form-widget.min.js:31
    each @ jquery.min.js?ver=3.6.1:2
    (anonymous) @ signup-form-widget.min.js:31
    c @ jquery.min.js?ver=3.6.1:2
    fireWith @ jquery.min.js?ver=3.6.1:2
    s.<computed> @ jquery.min.js?ver=3.6.1:2
    (anonymous) @ signup-form-widget.min.js:30
    c @ jquery.min.js?ver=3.6.1:2
    fireWith @ jquery.min.js?ver=3.6.1:2
    l @ jquery.min.js?ver=3.6.1:2
    (anonymous) @ jquery.min.js?ver=3.6.1:2
    load (async)
    send @ jquery.min.js?ver=3.6.1:2
    ajax @ jquery.min.js?ver=3.6.1:2
    s.ajax.s.ajax @ jquery-migrate.min.js?ver=3.3.2:2
    loadConfig @ signup-form-widget.min.js:30
    i.main @ signup-form-widget.min.js:31
    (anonymous) @ signup-form-widget.min.js:31
    window.ctctOnLoadCallback @ signup-form-widget.min.js:1
    l @ signup-form-widget.min.js:1
    (anonymous) @ signup-form-widget.min.js:1
    c @ jquery.min.js?ver=3.6.1:2
    fireWith @ jquery.min.js?ver=3.6.1:2
    l @ jquery.min.js?ver=3.6.1:2
    i @ jquery.min.js?ver=3.6.1:2
    dispatch @ jquery.min.js?ver=3.6.1:2
    y.handle @ jquery.min.js?ver=3.6.1:2
    load (async)
    add @ jquery.min.js?ver=3.6.1:2
    s.event.add @ jquery-migrate.min.js?ver=3.3.2:2
    (anonymous) @ jquery.min.js?ver=3.6.1:2
    each @ jquery.min.js?ver=3.6.1:2
    each @ jquery.min.js?ver=3.6.1:2
    Ee @ jquery.min.js?ver=3.6.1:2
    on @ jquery.min.js?ver=3.6.1:2
    send @ jquery.min.js?ver=3.6.1:2
    ajax @ jquery.min.js?ver=3.6.1:2
    s.ajax.s.ajax @ jquery-migrate.min.js?ver=3.3.2:2
    m @ signup-form-widget.min.js:1
    (anonymous) @ signup-form-widget.min.js:1
    (anonymous) @ signup-form-widget.min.js:1
    Ben

    (@cyberliciousben)

    Hi Lainey, did you just update WordPress from 5.9?

    I just rolled Maps back, and it gives a different error now:

    WP Google Maps: Build failed. Dumping unresolved dependencies

    wpgmza-google-pointlabel (in /var/www/html/svdpsp.org/wp-content/plugins/wp-google-maps/js/v8/google-maps/google-pointlabel.js)
    Requires:
    wpgmza-pro-pointlabel
    wpgmza-ol-pointlabel (in /var/www/html/svdpsp.org/wp-content/plugins/wp-google-maps/js/v8/open-layers/ol-pointlabel.js)
    Requires:
    wpgmza-pro-pointlabel
    Are you debugging or developing WP Google Maps? If not, please disable developer mode in Maps → Settings → Advanced to remove this notice.

    WP Google Maps v8.1.22
    WP Google Maps – Pro Add-on v8.1.20
    WP Google Maps – Gold Add-on v5.1.9

    It seems WordPress 6.0 is a common culprit, but don’t want to try rolling that back on production. I could create a staging to test around but would like some input from WP Go Maps team.

    Ben

    (@cyberliciousben)

    BTW, we’re currently on these versions:

    WP Go Maps (formerly WP Google Maps) v9.0.4
    WP Google Maps – Pro Add-on v8.1.20
    WP Go Maps – Gold Add-on v5.2.1

    Ben

    (@cyberliciousben)

    Ditto. Thought it had something to do with WP-Rocket, but we have a site that doesn’t have it. It seems to happen after updating to WordPress 6.0. It is happening to 2 websites now so we’re having to disable the WP Go Maps plugins – we have Gold. I tried disabling developer mode, but that just removes the map entirely.

    Even reverting the site back to its older state version doesn’t seem to help either:

    WP Go Maps: Build failed. Dumping unresolved dependencies

    wpgmza-circle (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/circle.js)
    Requires:
    wpgmza-shape
    wpgmza-pro-shape
    wpgmza-rectangle (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/rectangle.js)
    Requires:
    wpgmza-shape
    wpgmza-pro-shape
    wpgmza-google-circle (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/google-maps/google-circle.js)
    Requires:
    wpgmza-circle
    wpgmza-google-pointlabel (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/google-maps/google-pointlabel.js)
    Requires:
    wpgmza-pro-pointlabel
    wpgmza-google-rectangle (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/google-maps/google-rectangle.js)
    Requires:
    wpgmza-rectangle
    wpgmza-ol-circle (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/open-layers/ol-circle.js)
    Requires:
    wpgmza-circle
    wpgmza-ol-pointlabel (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/open-layers/ol-pointlabel.js)
    Requires:
    wpgmza-pro-pointlabel
    wpgmza-ol-rectangle (in /var/www/html/risingtidephysicaltherapy.com/wp-content/plugins/wp-google-maps/js/v8/open-layers/ol-rectangle.js)
    Requires:
    wpgmza-rectangle
    Are you debugging or developing WP Go Maps? If not, please disable developer mode in Maps → Settings → Advanced to remove this notice.

    Thread Starter Ben

    (@cyberliciousben)

    RESOLVED! The plugin had issues reading the file space on the EFS using the ‘File’ import. We had to drop the file in from the bastion server into the web server’s /wp-content/ai1wm-backups/ directory then use the ‘Restore’ from the Backup option.

    Thread Starter Ben

    (@cyberliciousben)

    Ok great! Yeah, WordPress codex isn’t that complicated but I do appreciate you judging my expertise. /s

Viewing 15 replies - 1 through 15 (of 21 total)