-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error after install #1
Comments
thanks, I will look into it this eveningif you have the zip extension the file should be extracted automatically on first runmake sure you go to plug-in settings and hit save, as sometimes the plugin does not get the settings if they are not saved onceif you go to tool and then logs you should have more info toonunoOn 1 Aug 2022 12:50, awrog ***@***.***> wrote:
I could not help noticing this typo
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi Franco, Thanks for you swift reply.
Log attached: |
there might be a typo, try adding |
Franco, adding The page-stats 404-error is still there. Advice: |
what is the URL that is giving you the 404? I've never got that beforeNunoOn 1 Aug 2022 14:24, awrog ***@***.***> wrote:
Franco, adding log_bots: false helped to prevent the errors in the log.
The page-stats 404-error is still there.
Advice:
I would store the data in .../user/data/page-data/page-data.sqlite
instead of
.../user/data/page-data.sqlite
That's more clear/manageable :-)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
@awrog what version of grav and admin plugin are you using ? I'm on Grav v1.7.34 - Admin v1.10.34 |
Franco, both the latest. (1.7.34, 1.10.34)
Hosting is on a shared server.
The url is: [domain]/[adminaccount]/page-stats (I only have ftp-access to
this environment tomorrow morning (eu timezone)).
…On Mon, Aug 1, 2022, 17:48 Nuno Costa ***@***.***> wrote:
@awrog <https://github.com/awrog> what version of grav and admin plugin
are you using ?
I'm on Grav v1.7.34 - Admin v1.10.34
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4XGQ3VGHKRYZFYD2YT53LVW7WU7ANCNFSM55HGFW7Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
is the admin route not |
Franco,
No, due to security-reasons it is advised to change it to something
different then /admin !
This can be changed in the admin plugin.
I appreciate the help!
…On Mon, Aug 1, 2022, 22:07 Nuno Costa ***@***.***> wrote:
is the admin route not /admin ?
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4XGQY3JQ5HRXY3MONGUG3VXAU7XANCNFSM55HGFW7Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
That's the problem! I'm working on a fix now |
Great!
|
@awrog can you try out https://github.com/francodacosta/grav-plugin-page-stats/releases/tag/0.1.2 should be fixed |
Great many thanks.
I'll install it asap and I will let you know!
…On Mon, Aug 1, 2022, 23:08 Nuno Costa ***@***.***> wrote:
@awrog <https://github.com/awrog> can you try out
https://github.com/francodacosta/grav-plugin-page-stats/releases/tag/0.1.2
should be fixed
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4XGQ364A5CIVGXS53XEVTVXA4EVANCNFSM55HGFW7Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The 'Page Stats' menu-entry works! |
This plugin looks promising!!
After installing the plugin the menu item 'Page Stats' displays
..../public_html/user/plugins/page-stats/data contains a zip-file: geolocation.sqlite.zip, no sqlite db-file
To investigate I manually extracted 'geolocation.sqlite'
Still no page when I click the menu item.
The plugin is collecting data in user/data/page-data.sqlite
Turning the plugin 'off' and 'on' again does not solve the problem.
The text was updated successfully, but these errors were encountered: