---
w̶i̶e̶l̶d̶l̶i̶n̶u̶x̶.̶c̶o̶m̶
Previously I wrote about:
To-Do List for Mzzstat WordPress Plugin
http://w̶i̶e̶l̶d̶l̶i̶n̶u̶x̶.̶c̶o̶m̶/2015.php?2015-08-14#2015-08-14 http://w̶i̶e̶l̶d̶l̶i̶n̶u̶x̶.̶c̶o̶m̶/?p=1147
Here’s the link to the current revision at the time of this blog post writing: https://github.com/mjassen/mzz-stat/t...2745
Since then, I’ve done this::
– Added a changelog file and started writing the changes there as I do them.
– Removed hard-coded PHP MySQL database calls, replaced them instead with native WordPress database calls.
– Added plugin install logic and plugin removal logic, including code to install and remove the database table and data.
Here’s my updated to-do list. It has changed to become more focused. Some items taken out and new added. (Re-prioritized next-steps for the development of the plugin)
1. Remove front-end shortcode feature; instead move it to a dashboard area where an admin can view the stat(s). The reason is that the user of this plugin is envisioned to be the WordPress site admin and not a site visitor.
2. More clearly define the purpose of the plugin and how to use it. Write these clearly into the readme of the plugin. start to get the plugin ready for submission to the WordPress plugin repository. (Use this codex article (and the pages it links to) as a starting point guide: “Plugin Submission and Promotion” ( https://codex.wordpress.org..._and_Promotion )
3. Submit the plugin to the WordPress.org plugins repository.
4. In addition to the total site visitors that now can be displayed, while it’s moved to the admin area, let’s also display a per-month and per-day visit count breakdown.
5. In the proposed admin stats area, let’s display a list of which URIs the visitor visited. (this is already captured, now let’s display it to the admin)
That’s what I’ve done and what I will do, to further develop the mzz-stat plugin.
tags: #wordpress
[2019 edit: Moved to: https://i̶n̶v̶e̶s̶t̶o̶r̶w̶o̶r̶k̶e̶r̶.̶c̶o̶m̶/2016/... .html.]