• Resolved Triplus

    (@triplus)


    Dear

    I have been using Complianz for a few months now. While the functionality seems amazing I recently realized the ‘proof of consent’ functionality is not working. I see no files on that page.
    Clicking ‘Generate now’ shows me a HTTP ERROR 500 making it not possible for me to use this – to my understanding important – feature.

    Any clue what could be going wrong?

    Thanks and kind regards
    Joren

    • This topic was modified 4 years, 10 months ago by Triplus.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @triplus,

    Because 500 error is such a broad server response, it’s hard to say in this instance.

    You can try checking the permissions on the uploads folder. Change to 755 if not already set: https://www.siteground.com/tutorials/ftp/change-permissions/

    Or maybe it runs out of memory when generating the file; you can add:

    define( 'WP_MEMORY_LIMIT' , '256M' ); to your wp-config.php to check if this helps.

    If it doesn’t help, we will need to debug the issue; https://complianz.io/debugging-issues-with-complianz/

    If there are no errors, other than a server error, you need to ask your hosting company to seee if they can see what’s going on.

    Let me know if I can help,

    regards Aert

    Thread Starter Triplus

    (@triplus)

    Hey

    Thanks for your quick reply!

    I did the debug and I indeed think I’m running out of memory:

    [28-May-2020 07:10:05 UTC] PHP Notice:  Undefined variable: temp_dir in /home/triplustutorials/public_html/wp-content/plugins/complianz-gdpr/class-document.php on line 2592
    [28-May-2020 07:10:05 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/triplustutorials/public_html/wp-content/plugins/complianz-gdpr/assets/vendor/mpdf/mpdf/src/Cache.php on line 27
    [28-May-2020 07:10:05 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0
    [28-May-2020 07:10:05 UTC] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in Unknown on line 0

    However I find it weird that I would need more as 256Mb of memory to run an addon? I have tried changing to define(‘WP_MEMORY_LIMIT’, '512M'); but result seems to be the same…

    I’m not sure if my host would allow me to use much more memory as it’s a shared host…

    EDIT: memory limit of the host seems to be indeed at 256, I could ask to increase this but I’m hoping to resolve this without having to do that…

    Thanks and kind regards

    • This reply was modified 4 years, 10 months ago by Triplus.
    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    The first error is coming from Complianz. It is an uncaught error which is probably caused by your site not having writing capabilities. I think the memory limit is caused by the missing directory, which seems the MPDF library to get into a loop.

    To resolve it, you can allow writing in the wp-content/uploads folder. To improve the feedback on this issue I’ll add a fix where this error is caught, and results in an understandable notice on the front-end.

    Thread Starter Triplus

    (@triplus)

    Dear

    thanks!

    I got it to work based on your message.
    About 2 months ago I moved hosts – and apparently the upload directory of media in my WP settings was still pointing to a directory structure that was a bit different as my current one.
    Issue was fully on my end. Thanks a lot for the support in figuring this out! Great plugin!

    KR
    Joren

    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    Thanks for the update!

    Plugin Contributor Mathieu Paapst

    (@paapst)

    Hi @triplus , Great to hear that your issue is resolved! Could you tell us what you think of the plugin or the support by casting your Review here? We’d love to hear your feedback!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘No ‘proof of consent’ being generated or HTTP 500 error’ is closed to new replies.