Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author eskapism

    (@eskapism)

    Does it always show that when activating plugins or only sometimes? For me it correctly shows the name of the activated plugin, so I wonder if there is some incompatibility with some other plugin.

    Here’s what I get, when calling SimpleHistoryLogQuery() on the frontend:

    2023-10-06 15:13:05 Deactivated plugin "{plugin_name}"
    2023-10-06 15:13:11 Deleted plugin "{plugin_name}"
    2023-10-06 15:19:07 Updated {post_type} "{post_title}"
    2023-10-06 15:20:19 Updated {post_type} "{post_title}"
    2023-10-06 15:21:28 Updated {post_type} "{post_title}"
    2023-10-06 15:22:18 Updated {post_type} "{post_title}"
    2023-10-06 15:22:57 Updated {post_type} "{post_title}"
    2023-10-06 15:23:40 Updated {post_type} "{post_title}"
    2023-10-06 15:23:41 Deleted {post_type} "{attachment_title}" ("{attachment_filename}")
    2023-10-06 15:49:09 Updated {post_type} "{post_title}"
    • This reply was modified 1 year, 1 month ago by VERYA Inc..

    Seems like on the frontend (using SimpleHistoryLogQuery()), I’m not getting a lot of information/settings. For instance, all the template info from above (between the curly brackets), but the timestamp is also incorrect (it’s in GMT, not using the WP setting)…

    Plugin Author eskapism

    (@eskapism)

    @veryaca I think your issue is different from the error that @clint6998 has, since you query the log manually. When using the API directly you need to “interpolate” the messages and the context yourself and you need to convert the timestamp to your local timezone. It needs some work, and that’s why I don’t “officially” have any solution to show the log at the frontend.

    @eskapism Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Activated plugin “{plugin_name}”’ is closed to new replies.