• Resolved sparcle01

    (@sparcle01)


    Hello,
    I have installed the plugin and tried to do filescan. Everything works well (a great plugin indeed!) but I have a problem with scanning results. As I understand, if everything is OK – the results should be:
    – all files notified by first scan (everything is “new”),
    – no files notified by next scans (if they haven’t changed, of course).

    My problem is, that I have over 700 json files listed as “Added”. Since that’s OK – I cannot set them “Mark as read”. Every icon (se: “Mark as Read”, “Exclude file” or “Exclude diectory”) does nothing. Also when I select any file(s) and try to use “Bulk action” (“Mark as read” when the file is selected and then “Apply” button) – nothing happens.

    Am I making something wrong?

Viewing 12 replies - 1 through 12 (of 12 total)
  • We have the same problem but the plugin developer can’t replicate it.

    Plugin Author robertabela

    (@robert681)

    Hello @sparcle01 and @upstartdm

    Thank you for your message and sorry for the delayed response. Just before the Christmas holidays we released update 1.7.0 of this plugin, which addressed quite a good number of issues.

    Can you please install the latest version of the plugin and advise if the problem persists or not?

    Looking forward to hearing from you.

    P.S. sorry for the late response. The offices were closed during the festive season and we are now replying to all emails. Thank you for your patience.

    Hi, running 1.7.0 here – I’m not 100% sure but upgrading to 1.7.0 may be what triggered this behaviour, it feels like both things happened around the same time.

    Plugin Author robertabela

    (@robert681)

    Hello @upstartdm

    In update 1.7.0 we have introduced integrity checks of the WordPress core files against the official WordPress repository (more info: how does the plugin detect file changes on WordPress).

    However, this has created some issues on some users’ site, similar to the ones you are reporting. Right now we are working on update 1.7.1 which we will include a fix. It will be available next week. Please follow our blog for updates. Once we release the update please update the plugin and that should address the issue.

    Thank you very much for your patience and for using the plugin.

    Plugin Author robertabela

    (@robert681)

    Hello @upstartdm and @sparcle01

    We have just released update 1.7.1 which addresses these issues. Can you please update your copy of the plugin?

    Should you have any other questions do not hesitate to get in touch and thanks for using our plugin.

    Updating to 1.7.1 hasn’t fixed this for us. Can you look again at this issue please?

    Plugin Author robertabela

    (@robert681)

    I am sorry to read about your problem @upstartdm

    I think the best way to troubleshoot this is to “reset” everything. Can you please:

    1) Navigate to the plugin’s settings
    2) Enable the seteting Delete plugin data upon uninstall
    3) Deactivate and uninstall the plugin
    4) Install the latest version and start afresh.

    Does this solve the issue?

    I’ve tried that just now but I’m afraid the same issue persists.

    PS not sure if it’s relevant but on reinstallation I got a “We detected that a previous file integrity scan failed due to an unknown reason” error message on the first scan.

    Plugin Author robertabela

    (@robert681)

    Thank you for your response @upstartdm

    I am sorry to read that the issue persists. Can you please follow the below procedure so you can send us some screenshots:

    1) Navigate to the plugin page
    2) Open the browser tools (Chrome or Firefox)
    3) Click on the Console tab
    4) Reproduce the issue. Are there any errors in the console? If there are please send them to us via email at [email protected].

    Thank you very much for your cooperation.

    upstartdm

    (@upstartdm)

    Thanks, an error is reported:

    Uncaught (in promise) TypeError: NetworkError when attempting to fetch resource.

    I’ll send you further details by email.

    Can we have a reply to this please, either here or to our emails?

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Cannot “mark as read”’ is closed to new replies.