Ben Sibley
Forum Replies Created
-
Hi there,
Thanks for getting in touch about this.
When a page is loaded, Independent Analytics makes one REST API request to your site to record the view. The query that writes the view to the database only takes a few milliseconds. The 1.2 second delay is how long it’s taking for WordPress to load. Anything you can do to speed up your site, such as removing uneeded plugins will help with this.
It’s also important to note that this request is deferred until the page is fully loaded. For this reason, it does not impact the loading experience for visitors, nor does it impact your Core Web Vitals. You can still achieve a perfect 100/100 Google PageSpeed score.
Thanks for letting me know that the issue has been resolved. We will be addressing the deprecation notices in version 2.15.
If you experience any further issues, please let me know and I’ll be happy to help.
Hi there,
Thanks for getting in touch. I’m sorry to hear about this error.
We are aware of the deprecation notices and will be addressing them soon in an update. Can you search your debug log for the Fatal or E_Error that occurred? That will point directly to the source of the error that occurred when you were in the post editor.
I am not able to recreate this same error when using Independent Analytics with PHP 8.4.21, so it would be good to see the relevant error message here so we can find out what’s happening.
Thank you!
No worries! Thank you for sharing your solution with others here, and for leaving an awesome review!
If anything else comes up, feel free to post here and I’ll be happy to help.
Got it. Thanks for letting me know.
I’m not sure how the request would take that long. It is essentially just loading WP and then writing a few rows to the DB. Those DB write operations should complete in a millisecond or two, whereas loading WP might add anywhere from 300-600ms to the total request time. For it to take 90s, it seems like the site would have to be unresponsive to any requests at that time.
Hi Noelle,
I’m sorry to hear about this performance issue. I can help you get to the bottom of this.
The iawp/search request is for the REST API endpoint that Independent Analytics uses to record page views. On the request, it writes new data to the database to record the view. Writing to the DB is extremely fast, so the majority of the time this request takes is primarily waiting for WP to load.
I visited your site, and when I checked the REST API request in the waterfall, it appears to be taking a reasonable length of time: https://share.iawp.io/cRBNVns8
What kind of performance test did you run that returned a 90 second delay for the iawp/search request?
Great, I’m glad to hear that resolved the error, and thank you for sharing that link for other users with this issue.
If the site is missing the PDO extension, then that is definitely an issue. That will prevent the Analytics from working at all. You should see an error message about this when you view the Analytics menu.
With that said, it should be a quick fix via cPanel. You just need to enable the PDO extension for PHP version you’re currently using. We have a tutorial on how to do that with screenshots here: https://independentwp.com/knowledgebase/common-questions/pdo-error/
Hi there,
Thanks for using Independent Analytics.
When using the WP Crontrol plugin, you should see a line like this in the Action column:
Closure in wp-content/plugins/independent-analytics-pro/IAWP/Cron_Job.php at line 16. The “Closure” is an anonymous function that gets called.
I don’t think it should be saying, “None.” I’m going to recommend that you deactivate and then reactivate Independent Analytics, and check if that resolves the message you’re seeing in WP Crontrol. Reactivating the plugin like this won’t have any impact on your data or settings.Forum: Reviews
In reply to: [Couprix] языковые файлыYou should probably post a support thread and give the developer a chance to respond before leaving a one-star rating. It only has one other review, so this pretty much killed its chances of gaining new users.
Got it. It sounds like they are most likely blocking the tracking, but if you want to share a link to your site, I can take a quick look to make sure the tracking script is firing everywhere.
Hi there,
Thanks for using Independent Analytics! I have a few ideas for this.
First, are any of these visitors logging in? If so, their activity might not be getting tracked (this is configurable).
Next, make sure you are looking at the main Pages report without any filters applied. Also, check to make sure the forms aren’t included in any popups/slide-ins that might show on another page.
Lastly, if none of this addresses the issue, then it’s possible they are blocking Independent Analytics with a browser extension like uBlock Origin. uBlock is the only one we know of that is currently blocking Independent Analytics.
Forum: Themes and Templates
In reply to: [Tracks] Author Box: Change Written By to Something Else?Nice! So what you’re going to do is copy the
/content/author-meta.phpfile from Tracks into your child theme. You can create thecontentfolder in the child theme, download a copy of Tracks, and then copy theauthor-meta.phpfile into the child theme’scontentfolder. Then, locate the “Written by:” text on line 11 and make your change.To upload it, you can create the zip file from the child theme and then upload and activate it via the Appearance menu.
If you lose any Customizer settings, then install this plugin: https://ww.wp.xz.cn/plugins/customizer-export-import/. You can reactivate Tracks to restore the Customizer settings, export them, switch to the child theme, and then import the settings.
Once the child theme is setup, it will be easier to make any changes like this in the future.
Forum: Themes and Templates
In reply to: [Tracks] Author Box: Change Written By to Something Else?Hi Joel,
It’s possible, but it is a more complex change to make. You’ll need to create a child theme and modify one of the PHP files to change the text. I can walk you through the steps if you’d like.
I’m marking this thread as resolved since we haven’t heard back in 24 hours, but please feel free to post here if you are having any further issues.