• Extensions

  • FriendsOfFlarum Analytics - tracking user visits

So odd. Everything is now displayed properly for both those two new extensions.

Things "normalized" and I have no idea why.
All I did is go in and out of the admin page, loaded it a new browser tab a few times.

As for the Flagrow analytics extension, my error in console is different:

Failed to load resource: net::ERR_CONNECTION_REFUSED

Even after performing following these instructions: https://piwik.org/faq/troubleshooting/faq_147/
My host uses apache servers so I couldn't follow the instructions here:
https://serverfault.com/questions/801651/nginx-x-frame-options-iframe-wordpress

    bikepost browser cache, just had the same thing.. tried everything ; only now I noticed my chrome dev screen wasn't open (which can be set to disable cache all together if open)..

    Sigh, I feel your pain ?

      ? Glad it worked.

      If only I could get the analytics going, I would be so happy!

        bikepost

        Im not that familiar with Apache.

        Try this maybe?

        https://piwik.org/faq/how-to-update/faq_159/

        Also, in my Analytics settings, my location is:
        https://{SITE}/analytics/piwik

        bikepost

        Check the following line in Apache Web Server’s httpd.conf file

        Header always append X-Frame-Options SAMEORIGIN
        Try deleting that line.
        Or, if is says,
        Header always append X-Frame-Options NONE
        try setting it to SAMEORIGIN.
        Restart Apache Web Server

        (someone correct me if thats a major security concern, just saying that I am unable to get Piwik analytics to show unless all references are removed)

        Reference: https://geekflare.com/secure-apache-from-clickjacking-with-x-frame-options/

              0E800 Thank you so much @0E800 Can't wait to try this tomorrow. Boarding in 10 mns.

              Keep an eye on this thread I posted on Piwik's forum.
              https://forum.piwik.org/t/connection-error-in-iframe/24906/1

              I will report back either way.

              Amazing we haven't ran into this issue more often on the board here if people have the Analytics up and running with BETA 6.

              Thank you again. I really appreciate it.

                @0E800 thanks for jumping on the support-train on our behalf ? Very much appreciated.

                I looked at the console error message closer and noticed the URL the extension was trying to reach had https:// twice so in the extension settings, I pasted the directory for the Piwik install without http:// (the extension adds it) and it worked!!!

                I feel so silly.

                The name of the extension in the left pane is still messed up and Piwik is showing 0 for every metric but at least now, the iFrame content loads.

                @luceos HTH, mostly I just like troubleshooting things. Thank you. ?

                @bikepost Glad you were able to solve the issue. Way to go.

                0E800 someone correct me if thats a major security concern, just saying that I am unable to get Piwik analytics to show unless all references are removed

                While not a big risk, I would advice against removing that header. SAMEORIGIN should be fine, depending on what you host on the same domain. If there's any place users or third-party might place custom HTML, in particular IFRAMES, I strongly suggest not disabling frame protection.

                Allowing inclusion of your analytics admin panel inside another website is dangerous, one could trick you into clicking various options by placing it in an iframe behind content on a webpage.

                You're probably a lot safer if your analytics server can only be accessed directly. That header has no impact on the correct working of the javascript tracking code.

                I'm not sure why that iframe thing was added to the extension in the first place ? It's not required for the tracking to work and users might downgrade their security to use it...

                By the way X-Frame-Options is now deprecated, the browser will use the frame setting provided via CSP if available.

                    bikepost could you please comment on why the extension name is all garbled in the left pane of the admin page?

                    I'm not sure what you mean ? I don't have a working install with that panel right now. Do you have a picture ?

                      @clarkwinkelmann Have a look at the screenshots I posted higher in this thread. In the left side of the screenshot, below Extensions, you will notice that instead of seeing "Analytics" the name shows "Flagrow-analytics.admin.page.nav.title"

                        bikepost That's the translations cache that is outdated. Disable and re-enable any extension or run php flarum cache:clear to refresh it ? That should normally do the trick.

                          I had used

                          php flarum cache:clear

                          many times and it didn't work.

                          I just disabled the English extension, re-enabled it and ran

                          php flarum cache:clear

                          again for good measure.

                          Didn't work and Piwik widgets are still now showing any visitors data. It's all 0 visitor.

                          @bikepost You need to also do a CTRL F5 on your browser. Your browser stores cache too ?

                          • QTM likes this.

                          Yep, sorry guys, I even closed the tab and launched a new one and then the browser and reopened.

                            luceos Remind me please, do we use Cloudfare for any of this? I don't recall signing up for it or seeing it.

                            Let me know how to please and I will do it. Google search results all instruct to log in but I don't think I have Cloudfare account.

                              Well, I have an update. Without doing anything further to Cloudfare (what is it @luceos anyway?) or anything else, the extension title now shows properly!

                              This resolved itself with time.
                              Would have love to "force" the refresh but I never found a way.

                              Glad it did.