You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If one wants to evaluate the post or category viewed most often, this is quite difficult with today's database scheme as the information is not given in the database. Therefore one cannot easily differentiate between posts, categories, other archive pages and the home page.
This support request reminded me of thoughts I had when trying to implement further extensions for Statify - Extended Evaluation. At least for real-time analytics it lasts too long to calculate that on run time if the Statify table contains thousands of rows.
The text was updated successfully, but these errors were encountered:
If one wants to evaluate the post or category viewed most often, this is quite difficult with today's database scheme as the information is not given in the database. Therefore one cannot easily differentiate between posts, categories, other archive pages and the home page.
This support request reminded me of thoughts I had when trying to implement further extensions for Statify - Extended Evaluation. At least for real-time analytics it lasts too long to calculate that on run time if the Statify table contains thousands of rows.
The text was updated successfully, but these errors were encountered: