1. Home
2. WP DSGVO Tools (GDPR)
3. 3.1.10

WP DSGVO Tools (GDPR) 3.1.10

Does WP DSGVO Tools (GDPR) work with WordPress 5.5.1 and PHP 7.4.8? A smoke test was performed on 2020-09-02 01:05:11 UTC.

Summary

Pages 14

Plugins ‹ Test site — WordPress

WP DSGVO Tools

WP DSGVO Tools → Cookie Notice / Popup

WP DSGVO Tools → Operator

WP DSGVO Tools → Page Basics

WP DSGVO Tools → Tagmanager

WP DSGVO Tools → Statistics

WP DSGVO Tools → Targeting

WP DSGVO Tools → Embeddings

WP DSGVO Tools → Subject Access Request

WP DSGVO Tools → Delete request

WP DSGVO Tools → Free Webinars

WP DSGVO Tools → V3 must read

Test site – Just another WordPress site

Benchmark

URL	Load time			Memory usage
	Inactive	Active	Change	Inactive	Active	Change
/wp-admin/index.php	0.444 s	1.023 s	+0.579 s	2.75 MiB	4.44 MiB	+ 1.69 MiB
/wp-admin/edit.php	0.231 s	1.709 s	+1.478 s	2.8 MiB	4.44 MiB	+ 1.65 MiB
/wp-admin/post-new.php	1.631 s	3.506 s	+1.875 s	4.54 MiB	5.79 MiB	+ 1.24 MiB
/wp-admin/upload.php	0.731 s	2.076 s	+1.345 s	2.63 MiB	4.44 MiB	+ 1.81 MiB
/wp-admin/options-writing.php	0.191 s	1.088 s	+0.897 s	2.64 MiB	4.44 MiB	+ 1.8 MiB
/wp-admin/media-new.php	0.223 s	0.726 s	+0.503 s	2.6 MiB	4.44 MiB	+ 1.84 MiB
/wp-admin/edit-tags.php?taxonomy=category	0.198 s	0.736 s	+0.538 s	2.64 MiB	4.44 MiB	+ 1.8 MiB
/wp-admin/post-new.php?post_type=page	1.451 s	2.788 s	+1.337 s	4.53 MiB	5.77 MiB	+ 1.24 MiB
/wp-admin/options-discussion.php	0.406 s	1.879 s	+1.473 s	2.61 MiB	4.44 MiB	+ 1.83 MiB
/wp-admin/edit-comments.php	0.243 s	0.721 s	+0.478 s	2.65 MiB	4.44 MiB	+ 1.79 MiB
/	0.431 s	1.019 s	+0.588 s	2.56 MiB	4.78 MiB	+ 2.22 MiB
Average	0.562 s	1.570 s	+1.008 s	3 MiB	4.72 MiB	+ 1.72 MiB

Additions

Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.

Options wp_options 7

• sp_dsgvo_legal_web_texts
• sp_dsgvo_legal_web_texts_lang
• sp_dsgvo_legal_web_texts_last_check
• sp_dsgvo_legal_web_texts_last_update
• sp_dsgvo_legal_web_texts_remote_version
• sp_dsgvo_legal_web_texts_version
• sp_dsgvo_show_notice_privacy_policy_texts_outdated

Custom Post Types 1

ID	Name
subjectaccessrequest	Posts

PHP Error Log 17 lines

[02-Sep-2020 01:06:13 UTC] PHP Fatal error:  Uncaught Error: Cannot use object of type WP_Error as array in /wp-content/plugins/shapepress-dsgvo/admin/tabs/v3/webinars/page.php:72
Stack trace:
#0 /wp-content/plugins/shapepress-dsgvo/admin/tabs/v3/webinars/class-sp-dsgvo-webinars-tab.php(15): include()
#1 /wp-content/plugins/shapepress-dsgvo/admin/base.php(31): SPDSGVOWebinarsTab->page()
#2 /wp-content/plugins/shapepress-dsgvo/admin/class-sp-dsgvo-admin.php(121): include('/opt/bitnami/ap...')
#3 /wp-includes/class-wp-hook.php(287): SPDSGVOAdmin->adminPage()
#4 /wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#5 /wp-includes/plugin.php(478): WP_Hook->do_action()
#6 /wp-admin/admin.php(259): do_action()
#7 {main}
  thrown in /wp-content/plugins/shapepress-dsgvo/admin/tabs/v3/webinars/page.php on line 72
[02-Sep-2020 01:06:25 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[02-Sep-2020 01:06:27 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[02-Sep-2020 01:06:27 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[02-Sep-2020 01:06:34 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[02-Sep-2020 01:06:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225
[02-Sep-2020 01:06:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. The REST API route definition for <code>legalweb/v1/lwTextEndpoint</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.5.0.) in /wp-includes/functions.php on line 5225

---