Non-public directory, logout and error-message questions

  • Resolved albarosa

    (@albarosa)


    5 months ago

    Dear All In One WP Security Team,

    I recently installed your plugin and have three questions about it:

    1. Before installing your plugin, I tried another one that recommended keeping the security logs directory in a non-public directory. With your plugin, is this behavior not necessary, right? Or did I perhaps overlook something?
    2. Is it possible to extend the time before an administrator is automatically logged out? For example, to several hours?
    3. In my developer console, I am seeing three errors, with the same error message each time: Uncaught TypeError: e.computedStyleMap is not a function

    This error is located in the following js file: wp-content/plugins/woocommerce/assets/client/blocks/checkout-blocks/totals-frontend.js

    I am not sure if this has anything to do with your plugin function to change the database prefix, as on the same day I also updated WooCommerce. Could you please let me know if I should contact WooCommerce regarding this error, or if it has something to do with changing the database prefix?
    I had already deactivated your plugin, but the errors persist. Will the exchanged database prefixes go back to default upon deactivating the plugin?

    Here is a screenshot from the error message:
    https://pasteboard.co/jPz135HBqGz8.png

    Thank you very much for an answer and best regards,
    albarosa

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @albarosa,

    1. We have activity logs and debug logs stored in the database, not the file so it will not be the case for our pluign.
    2. If you have force logout set to 30 min and if you have logged in before 30 mins if you change config value to 5 hrs you will not be logged out till 5 hrs. When you login that time stored and checked if it has exceeded then only you get logout.
    3. If AIOS is disabled and still the issue of Uncaught TypeError: e.computedStyleMap is not a function it will be better to ask WooCommerce support please cross check browser compatibility https://developer.mozilla.org/en-US/docs/Web/API/Element/computedStyleMap for that function first.

    No, It should not be related to DB prefix change. If you deactivate the plugin it will not change the DB prefix back. It will keep changed DB prefix.

    Thread Starter albarosa

    (@albarosa)

    Hello @hjogiupdraftplus,

    To 1.
    Ok, thank you for the information.

    To 2.
    Ok, I had overlooked the setting yesterday despite searching. Today I found it.

    To 3.
    Thank you for the link. I actually use the Firefox browser, which does not support the computedStyleMap() method, so I have now tested with Google Chrome, where different errors are now displayed, one of which only appears with your plugin activated.

    Here are two screenshots. The first one shows the error message with your plugin deactivated:
    https://pasteboard.co/G0lwGjuSO7Pn.png

    The second one shows the error messages with your plugin activated. As you can see, there is an additional “POST” error (Internal Server Error).
    https://pasteboard.co/4YXdpUzm6lHn.png

    It is noticeable that both errors (with the plugin activated and deactivated) are related to a “json” issue and a 500 Internal Server Error.

    Do you know what needs to be done to fix this error?

    Thank you and best regards,
    albarosa

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @albarosa,

    The screenshot shows WooCommerce using REST API If you have the below feature enabled please disable it.

    1) WP Security > Firewall > WP REST API. Can you please cross-check the Disallow unauthorized REST requests:

    We are going to add a note that the WooCoomerce plugin will not work, if above feature enabled as we have added for the ContactForm7 plugin.

    Regards

    Thread Starter albarosa

    (@albarosa)

    Hello @hjogiupdraftplus,

    Thank you very much for the response. The third error has now been fixed. I also found your explanation very clear before, I just mistakenly thought that I did not need the REST API for the plugins i am using. But apparently that is not the case, which is why the first two errors probably are present.

    And a big compliment for this exceptionally well-made plugin.

    Kind regards

    Plugin Support hjogiupdraftplus

    (@hjogiupdraftplus)

    Hi @albarosa,

    You’re welcome,

    Thanks for 5 star rating.

    Regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.