1. Home
  2. Form Vibes – Database Manager for Forms
  3. 1.1.3

Form Vibes - Database Manager for Forms 1.1.3

Does "Form Vibes - Database Manager for Forms" work with WordPress 5.4.2 and PHP 7.2.16? A smoke test was performed on .

Summary

Errors
9PHP fatal errors
2PHP warnings
367PHP notices
1Database errors
6JavaScript exceptions
All test pages loaded successfully
No resource errors
Performance

Memory usage: 693.16 KiB
The average PHP memory usage increased by this amount after activating by the plugin.

Page speed impact: 0.043 seconds
The average page load time increased by this amount after activating the plugin.

Environment
WordPress version5.4.2
PHP version7.2.16
MySQL version8.0.15
PHP memory limit256M
Plugin Info
Last updated
Active installs 20,000+
WordPress.org page https://wordpress.org/plugins/form-vibes/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 7

Form Vibes Leads ‹ Test site — WordPress

Page screenshot: Form Vibes Leads ‹ Test site — WordPress
URL /wp-admin/admin.php?page=fv-leads
Requested URL /wp-admin/plugins.php?action=activate&plugin=form-vibes%2Fform-vibes.php&plugin_status=all&paged=1&s&_wpnonce=8295782d1a
Aspect after-activation
HTTP status 200
Load time 1.737 s
Memory usage 4.66 MiB
JS errors None
Resource errors None

Form Vibes

Page screenshot: Form Vibes
URL /wp-admin/admin.php?page=fv-leads
Aspect menu-item
HTTP status 200
Load time 0.555 s
Memory usage 4.22 MiB
JS errors 
[
    {
        "message": "SyntaxError: Unexpected end of JSON input\n    at /wp-content/plugins/form-vibes/assets/js/admin.js?ver=1.1.3:86:114293",
        "trace": null,
        "code": null
    },
    {
        "message": "TypeError: Cannot read property 'text' of undefined\n    at /wp-content/plugins/form-vibes/assets/js/admin.js?ver=1.1.3:86:110802",
        "trace": null,
        "code": null
    }
]
Resource errors None

Form Vibes → Analytics

Page screenshot: Form Vibes → Analytics
URL /wp-admin/admin.php?page=fv-analytics
Aspect menu-item
HTTP status 200
Load time 0.638 s
Memory usage 4.22 MiB
JS errors 
[
    {
        "message": "TypeError: Cannot convert undefined or null to object\n    at Function.keys (<anonymous>)\n    at /wp-content/plugins/form-vibes/assets/js/analytics.js?ver=1.1.3:79:420723",
        "trace": null,
        "code": null
    },
    {
        "message": "TypeError: Cannot read property 'text' of undefined\n    at /wp-content/plugins/form-vibes/assets/js/analytics.js?ver=1.1.3:79:418757",
        "trace": null,
        "code": null
    }
]
Resource errors None

Form Vibes → Settings

Page screenshot: Form Vibes → Settings
URL /wp-admin/admin.php?page=fv-db-settings
Aspect menu-item
HTTP status 200
Load time 0.366 s
Memory usage 4.22 MiB
JS errors 
[
    {
        "message": "SyntaxError: Unexpected token < in JSON at position 0",
        "trace": null,
        "code": null
    }
]
Resource errors None

Form Vibes → Event Logs

Page screenshot: Form Vibes → Event Logs
URL /wp-admin/admin.php?page=fv-logs
Aspect menu-item
HTTP status 200
Load time 0.499 s
Memory usage 4.22 MiB
JS errors None
Resource errors None

Test site – Just another WordPress site

Page screenshot: Test site – Just another WordPress site
URL /
Aspect front-page
HTTP status 200
Load time 0.218 s
Memory usage 3.94 MiB
JS errors None
Resource errors None

Dashboard ‹ Test site — WordPress

Page screenshot: Dashboard ‹ Test site — WordPress
URL /wp-admin/index.php
Aspect new-meta-boxes
HTTP status 200
Load time 0.441 s
Memory usage 4.32 MiB
JS errors 
[
    {
        "message": "SyntaxError: Unexpected token < in JSON at position 0",
        "trace": null,
        "code": null
    }
]
Resource errors None

Benchmark

URL Load time Memory usage
Inactive Active Change Inactive Active Change
/wp-admin/index.php0.293 s0.538 s+0.245 s3.64 MiB4.32 MiB+ 695.66 KiB
/wp-admin/edit.php0.192 s0.347 s+0.155 s3.67 MiB4.34 MiB+ 687.27 KiB
/wp-admin/post-new.php1.157 s1.448 s+0.291 s5.43 MiB6.15 MiB+ 740.37 KiB
/wp-admin/upload.php0.469 s0.381 s-0.088 s3.5 MiB4.23 MiB+ 745.05 KiB
/wp-admin/options-writing.php0.163 s0.156 s-0.007 s3.58 MiB4.22 MiB+ 651.98 KiB
/wp-admin/media-new.php0.203 s0.183 s-0.020 s3.48 MiB4.21 MiB+ 746.22 KiB
/wp-admin/edit-tags.php?taxonomy=category0.158 s0.176 s+0.018 s3.58 MiB4.25 MiB+ 682.48 KiB
/wp-admin/post-new.php?post_type=page0.962 s0.977 s+0.015 s5.42 MiB6.13 MiB+ 728.95 KiB
/wp-admin/options-discussion.php0.528 s0.468 s-0.060 s3.48 MiB4.21 MiB+ 746.53 KiB
/wp-admin/edit-comments.php0.187 s0.181 s-0.006 s3.59 MiB4.25 MiB+ 681.42 KiB
/0.269 s0.194 s-0.075 s3.43 MiB3.94 MiB+ 518.8 KiB
Average 0.416 s0.459 s+0.043 s3.89 MiB4.57 MiB+ 693.16 KiB

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.

Database Tables 3

Options wp_options 6

Meta Boxes 

{
    "dashboard": {
        "form_vibes_widget-0": {
            "title": "Form Vibes Analytics",
            "context": "normal"
        }
    }
}

PHP Error Log 458 lines

[12-Jun-2020 05:11:33 UTC] WordPress database error Can't DROP 'status'; check that column/key exists for query ALTER TABLE wp_fv_enteries DROP COLUMN status made by require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('plugins_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, WPV_FV\Classes\DbTables::fv_plugin_activated, WPV_FV\Classes\DbTables::create_db_table
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:35 UTC] PHP Fatal error:  Uncaught Error: Class '\WPV_FV\Integrations\' not found in /wp-content/plugins/form-vibes/inc/classes/api-endpoint.php:1236
Stack trace:
#0 /wp-includes/rest-api/class-wp-rest-server.php(1015): WPV_FV\Classes\ApiEndpoint::get_forms(Object(WP_REST_Request))
#1 /wp-includes/rest-api/class-wp-rest-server.php(342): WP_REST_Server->dispatch(Object(WP_REST_Request))
#2 /wp-includes/rest-api.php(312): WP_REST_Server->serve_request('/wts-fv/get_for...')
#3 /wp-includes/class-wp-hook.php(287): rest_api_loaded(Object(WP))
#4 /wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array)
#5 /wp-includes/plugin.php(544): WP_Hook->do_action(Array)
#6 /wp-includes/class-wp.php(388): do_action_ref_array('parse_request', Array)
#7 /opt/bitnami/apps/w in /wp-content/plugins/form-vibes/inc/classes/api-endpoint.php on line 1236
[12-Jun-2020 05:11:35 UTC] PHP Notice:  Undefined offset: 0 in /wp-content/plugins/form-vibes/inc/classes/api-endpoint.php on line 2110
[12-Jun-2020 05:11:35 UTC] PHP Fatal error:  Uncaught Error: Class '\WPV_FV\Integrations\' not found in /wp-content/plugins/form-vibes/inc/classes/api-endpoint.php:2112
Stack trace:
#0 /wp-includes/rest-api/class-wp-rest-server.php(1015): WPV_FV\Classes\ApiEndpoint::get_dbpanel_settings(Object(WP_REST_Request))
#1 /wp-includes/rest-api/class-wp-rest-server.php(342): WP_REST_Server->dispatch(Object(WP_REST_Request))
#2 /wp-includes/rest-api.php(312): WP_REST_Server->serve_request('/wts-fv/get_dbp...')
#3 /wp-includes/class-wp-hook.php(287): rest_api_loaded(Object(WP))
#4 /wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array)
#5 /wp-includes/plugin.php(544): WP_Hook->do_action(Array)
#6 /wp-includes/class-wp.php(388): do_action_ref_array('parse_request', Array)
#7 /opt/bit in /wp-content/plugins/form-vibes/inc/classes/api-endpoint.php on line 2112
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  register_rest_route was called <strong>incorrectly</strong>. Namespace must not start or end with a slash. 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.4.2.) in /wp-includes/functions.php on line 5167
[12-Jun-2020 05:11:36 UTC] PHP Notice:  Undefined offset: 0 in /wp-content/plugins/form-vibes/inc/classes/api-endpoint.php on line 2110
[12-Jun-2020 05:11:36 UTC] PHP Fatal error:  Uncaught Error: Class '\WPV_FV\Integrations\' not found in /wp-content/plugins/form-vibes/inc/classes/api-endpoint.php:2112
Stack trace:
#0 /wp-includes/rest-api/class-wp-rest-server.php(1015): WPV_FV\Classes\ApiEndpoint::get_dbpanel_settings(Object(WP_REST_Request))
#1 /wp-includes/rest-api/class-wp-rest-server.php(342): WP_REST_Server->dispatch(Object(WP_REST_Request))
#2 /wp-includes/rest-api.php(312): WP_REST_Server->serve_request('/wts-fv/get_dbp...')
#3 /wp-includes/class-wp-hook.php(287): rest_api_loaded(Object(WP))
#4 /wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array)
#5 /wp-includes/plugin.php(544): WP_Hook->do_action(Array)
#6 /wp-includes/class-wp.php(388): do_action_ref_array('parse_request', Array)

(+358 more lines)
See also: All tests for this plugin, How to Hide Form Vibes Admin Menus and Widgets