Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Ackee
  3. Ackee - tracking.js missing

Ackee - tracking.js missing

Scheduled Pinned Locked Moved Solved Ackee
12 Posts 5 Posters 2.4k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    JLX89
    wrote on last edited by
    #1

    Hello,
    It seems that the logs are showing the following error for Ackee:

    Feb 15 20:36:34 [Ackee] › ⚠ warning /tracking.js?ver=1.0.0 not found

    I attempted to take a look inside /home/yellowtent/appsdata/{app-id}/data but didn't see anything listed aside from the standard files.

    Any help with this would be greatly appreciated!

    Thank you

    girishG 2 Replies Last reply
    0
    • J JLX89

      Hello,
      It seems that the logs are showing the following error for Ackee:

      Feb 15 20:36:34 [Ackee] › ⚠ warning /tracking.js?ver=1.0.0 not found

      I attempted to take a look inside /home/yellowtent/appsdata/{app-id}/data but didn't see anything listed aside from the standard files.

      Any help with this would be greatly appreciated!

      Thank you

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @jlx89 Where are you seeing this log? In my logs, all I see is

      Feb 16 00:32:24 ==> Changing ownership
      Feb 16 00:32:24 ==> Starting Ackee
      Feb 16 00:32:25
      Feb 16 00:32:25 > ackee@3.0.2 server /app/code
      Feb 16 00:32:25 > node src/index.js
      Feb 16 00:32:25
      Feb 16 00:32:28 [Ackee] › … awaiting Connecting to mongodb://mongodb:27017/0eee7d7a9e98ddef
      Feb 16 00:32:29 [Ackee] › ✔ success Connected to mongodb://mongodb:27017/0eee7d7a9e98ddef
      Feb 16 00:32:29 [Ackee] › ▶ start Starting the server
      Feb 16 00:32:29 [Ackee] › … watching Listening on http://localhost:3000
      
      1 Reply Last reply
      0
      • J JLX89

        Hello,
        It seems that the logs are showing the following error for Ackee:

        Feb 15 20:36:34 [Ackee] › ⚠ warning /tracking.js?ver=1.0.0 not found

        I attempted to take a look inside /home/yellowtent/appsdata/{app-id}/data but didn't see anything listed aside from the standard files.

        Any help with this would be greatly appreciated!

        Thank you

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #3

        @jlx89 said in Ackee - tracking.js missing:

        Feb 15 20:36:34 [Ackee] › warning /tracking.js?ver=1.0.0 not found

        Also, the file name is tracker.js and not tracking.js . It's located in /app/code/dist/tracker.js which you can see using the Web Terminal

        J 1 Reply Last reply
        0
        • girishG girish

          @jlx89 said in Ackee - tracking.js missing:

          Feb 15 20:36:34 [Ackee] › warning /tracking.js?ver=1.0.0 not found

          Also, the file name is tracker.js and not tracking.js . It's located in /app/code/dist/tracker.js which you can see using the Web Terminal

          J Offline
          J Offline
          JLX89
          wrote on last edited by
          #4

          @girish Thanks for following up on this. So I found part of the issue, which was related to an outside system. I've gone ahead and fixed that and this issue has fixed itself.

          I'm working to see why information isn't flowing in from the trackers. Do you know if there is a way to see if Ackee is actually receiving traffic from the tracking codes? I have updated the CORS information per the documentation and the code seems to be loading fine on the sites.

          Thank you!

          marcusquinnM 1 Reply Last reply
          0
          • J JLX89

            @girish Thanks for following up on this. So I found part of the issue, which was related to an outside system. I've gone ahead and fixed that and this issue has fixed itself.

            I'm working to see why information isn't flowing in from the trackers. Do you know if there is a way to see if Ackee is actually receiving traffic from the tracking codes? I have updated the CORS information per the documentation and the code seems to be loading fine on the sites.

            Thank you!

            marcusquinnM Offline
            marcusquinnM Offline
            marcusquinn
            wrote on last edited by
            #5

            @jlx89 Does your browser have privacy tracker blocking or submit donotfollow preferences?

            Web Design https://www.evergreen.je
            Development https://brandlight.org
            Life https://marcusquinn.com

            J 1 Reply Last reply
            0
            • marcusquinnM marcusquinn

              @jlx89 Does your browser have privacy tracker blocking or submit donotfollow preferences?

              J Offline
              J Offline
              JLX89
              wrote on last edited by
              #6

              @marcusquinn Thanks for replying. I actually disabled it, but it seems to have taken around 48 hours to actually start pulling data in. I think I'm good to go now, thanks again!

              1 Reply Last reply
              1
              • MelodyKH3M Offline
                MelodyKH3M Offline
                MelodyKH3
                wrote on last edited by
                #7

                For anyone else who is trying to add Ackee to a Wordpress install. "SoapBerry" defaults to "tracker.js" but it should be 'tracking.js'

                Adding this here because its the first result on google and it seems that's originally the problem this OP had.

                girishG J 2 Replies Last reply
                0
                • MelodyKH3M MelodyKH3

                  For anyone else who is trying to add Ackee to a Wordpress install. "SoapBerry" defaults to "tracker.js" but it should be 'tracking.js'

                  Adding this here because its the first result on google and it seems that's originally the problem this OP had.

                  girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by girish
                  #8

                  @melodykh3 you mean the other way around ? I do see that https://wordpress.org/plugins/soapberry/#description has a screenshot that defaults to tracking.js . I reported it here - https://wordpress.org/support/topic/ackee-tracker-file-should-be-tracker-js/

                  1 Reply Last reply
                  0
                  • MelodyKH3M MelodyKH3

                    For anyone else who is trying to add Ackee to a Wordpress install. "SoapBerry" defaults to "tracker.js" but it should be 'tracking.js'

                    Adding this here because its the first result on google and it seems that's originally the problem this OP had.

                    J Offline
                    J Offline
                    JLX89
                    wrote on last edited by JLX89
                    #9

                    @melodykh3 Yes, this was a portion of the issue -- an outside hosted WordPress website using SoapBerry was hitting the server with the default tracking.js. I went into the plugin and changed the file name.

                    The other issues seems to have resolved over time with updating the CORS Headers in the env file. It ended up taking a good 72 hours for everything to work out.

                    humptydumptyH 1 Reply Last reply
                    0
                    • J JLX89

                      @melodykh3 Yes, this was a portion of the issue -- an outside hosted WordPress website using SoapBerry was hitting the server with the default tracking.js. I went into the plugin and changed the file name.

                      The other issues seems to have resolved over time with updating the CORS Headers in the env file. It ended up taking a good 72 hours for everything to work out.

                      humptydumptyH Offline
                      humptydumptyH Offline
                      humptydumpty
                      wrote on last edited by
                      #10

                      Ackee & Soapberry work fine if you set it to use tracker.js, add the CORS headers in the env file and restart the app. The tracking worked immediately for me on multiple WP installs except one. There's some kind of conflict with the caching plugin (WP-Rocket) and I haven't looked into it yet.

                      J 1 Reply Last reply
                      0
                      • humptydumptyH humptydumpty

                        Ackee & Soapberry work fine if you set it to use tracker.js, add the CORS headers in the env file and restart the app. The tracking worked immediately for me on multiple WP installs except one. There's some kind of conflict with the caching plugin (WP-Rocket) and I haven't looked into it yet.

                        J Offline
                        J Offline
                        JLX89
                        wrote on last edited by
                        #11

                        @humptydumpty Yeah, I ended up figuring it out but it took some time. So I did also notice, if you're using bunny.net CDN, you need to include the tracker.js to be excluded from the CDN.

                        humptydumptyH 1 Reply Last reply
                        1
                        • J JLX89

                          @humptydumpty Yeah, I ended up figuring it out but it took some time. So I did also notice, if you're using bunny.net CDN, you need to include the tracker.js to be excluded from the CDN.

                          humptydumptyH Offline
                          humptydumptyH Offline
                          humptydumpty
                          wrote on last edited by
                          #12

                          @jlx89 Thanks for the tip. That's the CDN that I'm using and it's with the site that I'm having trouble with 👌

                          1 Reply Last reply
                          1
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Bookmarks
                          • Search