E_COMPILE_ERROR

  • Resolved angiepunkt

    (@angiepunkt)


    4 years, 1 month ago

    Hello!

    Matomo produced a fatal Error on my WordPress Site. I couldn’t login, fortunately I could deactivate Matomo through my hosting admin panel. Now I can login again.

    Everytime I activate Matomo again, I lose access to the WordPress Dashboard.

    This is the Error Message I got (partially in German):

    ”
    Aktuelles Plugin: Matomo Analytics – Ethical Stats. Powerful Insights. (Version 1.3.1)
    PHP-Version 7.3.20-1+ubuntu16.04.1+deb.sury.org+1

    Fehler-Details
    ==============
    Ein Fehler vom Typ E_COMPILE_ERROR wurde in der Zeile 62 der Datei /home/wp/disk/wordpress/wp-content/plugins/matomo/classes/WpMatomo/Bootstrap.php verursacht. Fehlermeldung: require_once(): Failed opening required ‘/home/wp/disk/wordpress/wp-content/plugins/matomo/app/bootstrap.php’ (include_path=’.:/usr/share/php’)
    ”

    This is the System Report:
    ”
    # Matomo

    * Matomo Pluginversion: 1.3.1
    * Config existiert und ist beschreibbar.: Ja (“$ABSPATH/wp-content/uploads/matomo/config/config.ini.php” )
    * JS Tracker existiert und ist beschreibbar.: Ja (“$ABSPATH/wp-content/uploads/matomo/matomo.js” )
    * Plugin-Verzeichnisse: Yes ([{“pluginsPathAbsolute”:”$ABSPATH\/wp-content\/plugins\/matomo\/plugins”,”webrootDirRelativeToMatomo”:”..\/”}])
    * Tmp-Verzeichnis schreibbar: Yes ($ABSPATH/wp-content/cache/matomo)
    * Matomo Blog idSite: 1
    * Installierte Matomo-Version: No

    ## Endpoints

    * Matomo JavaScript Tracker URL: ($site_url/wp-content/uploads/matomo/matomo.js)
    * Matomo JavaScript Tracker – WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
    * Matomo HTTP Tracking API: ($site_url/wp-content/plugins/matomo/app/matomo.php)
    * Matomo HTTP Tracking API – WP Rest API: ($site_url/wp-json/matomo/v1/hit/)

    ## Crons

    * Server-Zeit: 2020-10-23 06:01:30
    * Blog-Zeit: 2020-10-23 08:01:30 (Die nachfolgenden Daten werden in der Blog-Zeitzone angezeigt)
    * Sync users & sites: Next run: 2020-10-23 10:31:26 ( Last started: 2020-10-22 11:05:50. Last ended: 2020-10-20 10:33:16. Interval: daily)
    * Archive: Next run: 2020-10-23 08:31:26 ( Last started: 2020-10-22 11:31:51. Last ended: 2020-10-21 09:32:28. Interval: hourly)
    * Update GeoIP DB: Next run: 2020-11-21 09:31:26 ( Last started: 2020-10-22 11:02:29. Last ended: 2020-09-22 10:38:34. Interval: matomo_monthly)

    ## Matomo Settings

    * Track mode: default
    * Track codeposition: footer
    * Track api endpoint: default
    * Track js endpoint: default
    * Last tracking settings update: 1590568342
    * Last settings update: 1590568342
    * Version history: 1.3.0, 1.2.0, 1.1.3, 1.1.2, 1.1.1
    * Core version: 3.14.0
    * Track content: visible
    * Track ecommerce: No
    * Limit cookies: Yes
    * Show get started page: 0

    ## Logs

    * Keine:

    # WordPress

    * Home URL: $site_url
    * Site URL: $site_url
    * WordPress Version: 5.5.1
    * Number of blogs: 1
    * Multisite Enabled: No
    * Network Enabled: No
    * WP_DEBUG: No
    * WP_DEBUG_DISPLAY: No
    * WP_DEBUG_LOG: Yes
    * DISABLE_WP_CRON: No
    * FORCE_SSL_ADMIN: Yes
    * WP_CACHE: No
    * CONCATENATE_SCRIPTS: –
    * COMPRESS_SCRIPTS: –
    * COMPRESS_CSS: –
    * ENFORCE_GZIP: –
    * WP_LOCAL_DEV: –
    * DIEONDBERROR: –
    * WPLANG: –
    * ALTERNATE_WP_CRON: –
    * WP_CRON_LOCK_TIMEOUT: 60
    * WP_DISABLE_FATAL_ERROR_HANDLER: –
    * Permalink Structure: /%postname%/
    * Possibly uses symlink: No
    * Compatible content directory: Yes

    # WordPress Plugins

    ## MU Plugins

    * assets-manager.php: 1.0.9
    * InfiniteWP – Client Loader:

    ## Plugins

    * 404page – your smart custom 404 error page: 11.2.6
    * Antispam Bee: 2.9.2
    * Avada Builder: 3.1.1
    * Avada Core: 5.1.1
    * Better Search Replace: 1.3.3 (Network enabled)
    * Contact Form 7: 5.3
    * InfiniteWP – Client: 1.9.4.7 (Network enabled)
    * Matomo Analytics – Ethical Stats. Powerful Insights.: 1.3.1
    * MC4WP: Mailchimp for WordPress: 4.8.1
    * Webcraftic Clearfy – WordPress optimization plugin: 1.7.4
    * Webcraftic Hide login page: 1.1.1
    * WP 2FA – Two-factor authentication for WordPress: 1.4.2 (Network enabled)
    * WP2Static: 6.6.7
    * WP DSGVO Tools (GDPR): 3.1.12
    * WP YouTube Lyte: 1.7.14
    * Yoast SEO: 15.1.1
    * Active Plugins: 16 (iwp-client 404page antispam-bee better-search-replace clearfy contact-form-7 fusion-builder fusion-core hide-login-page mailchimp-for-wp matomo shapepress-dsgvo static-html-output-plugin $DB_NAME-seo wp-2fa wp-youtube-lyte)

    # Server

    * Server Info: nginx/1.17.5
    * PHP OS: Linux
    * PHP Version: 7.3.20-1+ubuntu16.04.1+deb.sury.org+1
    * PHP SAPI: fpm-fcgi
    * PHP Binary Name: php-fpm7.3
    * Timezone: UTC
    * WP timezone: Europe/Vienna
    * Locale: de_DE
    * User Locale: de_DE
    * Memory Limit: 128M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
    * WP Memory Limit: 128M
    * WP Max Memory Limit: 128M
    * Time: 1603432890
    * Max Execution Time: 300
    * Max Post Size: 2000M
    * Max Upload Size: 2097152000
    * Max Input Vars: 10000
    * Disabled PHP functions: Yes (pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,php_uname,getmyuid,getmypid,passthru,leak,listen,diskfreespace,link,ignore_user_abord,shell_exec,dl,exec,system,highlight_file,source,show_source,fpaththru,virtual,posix_ctermid,posix_getcwd,posix_getegid,posix_geteuid,posix_getgid,posix_getgrgid,posix_getgrnam,posix_getgroups,posix_getlogin,posix_getpgid,posix_getpgrp,posix_getpid,posix,_getppid,posix_getpwnam,posix_getpwuid,posix_getrlimit,posix_getsid,posix_getuid,posix_isatty,posix_kill,posix_mkfifo,posix_setegid,posix_seteuid,posix_setgid,posix_setpgid,posix_setsid,posix_setuid,posix_times,posix_ttyname,posix_uname,proc_open,proc_close,proc_get_status,proc_nice,proc_terminate,popen)
    * zlib.output_compression is off: Yes
    * Curl Version: 7.47.0, OpenSSL/1.0.2g
    * Suhosin installed: No

    # Database

    * MySQL Version: 5.5.5
    * Mysqli Connect: Yes
    * Force MySQL over Mysqli: No
    * DB Prefix: wp_hhbqwtzbej_
    * DB CHARSET: utf8
    * DB COLLATE:
    * SHOW ERRORS: No
    * SUPPRESS ERRORS: No
    * Uses Socket: No
    * Uses IPv6: No
    * Matomo tables found: 159
    * Matomo users found: 3
    * Matomo sites found: 1
    * Erforderliche Berechtigungen: OK

    # Browser

    * Browser: (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0)

    ”

    Thanks for any help!
    Angie.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author Thomas

    (@tsteur)

    Hi @angiepunkt

    could you check if the file /home/wp/disk/wordpress/wp-content/plugins/matomo/app/bootstrap.php exists? Did you install the plugin through the WordPress plugins directory? I wonder if the file was somehow not copied/written correctly.

    Thread Starter angiepunkt

    (@angiepunkt)

    Hello Thomas,
    sorry for my late answer.

    I installed the plugin through the WordPress Backend, not manually.

    The file you mentioned doesn’t exist. What do you suggest?

    Thank you.
    Angie.

    • This reply was modified 4 years ago by angiepunkt.
    Plugin Author Thomas

    (@tsteur)

    Thanks @angiepunkt

    Any chance you could maybe try to re-install the plugin? I’m meaning not just re-activating but completely uninstalling it and then installing it again from scratch. This file should be included in our plugin and it seems like a file was not created that should have been created when WordPress was installing the plugin.

    Plugin Author Thomas

    (@tsteur)

    Hi @angiepunkt hope you’re well. Have you maybe had a chance to see if re-uploading the plugin solved this issue?

    Thread Starter angiepunkt

    (@angiepunkt)

    Thank you for being so persistent!
    I deactivated and deleting the Plugin. Now I installed it again. But it seems to be still in the troubleshooting mode.

    Thread Starter angiepunkt

    (@angiepunkt)

    But the file you asked for exists now.
    /home/wp/disk/wordpress/wp-content/plugins/matomo/app/bootstrap.php

    Plugin Author Thomas

    (@tsteur)

    thanks @angiepunkt . Just to make sure I understand it right: What do you mean exactly by “troubleshooting mode”? Do you see any kind of error message?

    Thread Starter angiepunkt

    (@angiepunkt)

    I mean, that I don’t see any statistics but the System Report Page.

    • This reply was modified 4 years ago by angiepunkt.
    Plugin Author Thomas

    (@tsteur)

    Thanks @angiepunkt do you maybe have the option MATOMO_SAFE_MODE enabled in your wp-config.php?

    Thread Starter angiepunkt

    (@angiepunkt)

    Thank you! Thats what did the trick. Now everything seems to be working againg. The data collected is sadly lost, I guess?
    Strange, how it worked for months and then the crucial file wasn’t there anymore…?`

    Is there a way to prevent this?

    Thank you very much for your patience and help!
    Angie.

    Plugin Author Thomas

    (@tsteur)

    Great it works now @angiepunkt and thanks for letting us know.

    Yes I assume the data would be lost. Sorry about that! We have an issue to eventually add a check to make sure that all files that should exist actually exist.

    In this case when WordPress installed the plugin it for some reason failed to write one file. We’re hoping to be able to detect this in the future so such issues will be detected sooner (ideally WordPress was to provide such a feature automatically but it’s not the case unfortunately)

    Thread Starter angiepunkt

    (@angiepunkt)

    Should I check, if the file exists on other websites I maintain?
    And if it doesn’t, can I save the data before reinstalling the plugin?

    Plugin Author Thomas

    (@tsteur)

    > Should I check, if the file exists on other websites I maintain?

    @angiepunkt it shouldn’t be needed. We’ve never had such an issue before out of many installs. It must have been some very random glitch.

    > And if it doesn’t, can I save the data before reinstalling the plugin?

    What you can do is go to Matomo Analytics -> Settings. Then click on the “Advanced” tab and disable the setting Delete all data on uninstall..

    If you were to ever run into this issue again, then you could if possible also update the plugin manually eg using FTP (if that’s a possibility) see Option 2 in https://matomo.org/installing-matomo-for-wordpress/ (if there’s an update available for the plugin then also Option 3 would work) so no uninstalling would be needed.

    Thread Starter angiepunkt

    (@angiepunkt)

    Sorry, but there’s a problem again. Without deactivating the Plugin, I can’t login in to the wp-dashboard.

    WordPress-Version 5.5.3
    Aktuelles Theme: Avada Child (Version 1.0.0)
    Aktuelles Plugin: Matomo Analytics – Ethical Stats. Powerful Insights. (Version 1.3.2)
    PHP-Version 7.3.22-1+ubuntu16.04.1+deb.sury.org+1

    Fehler-Details
    ==============
    Ein Fehler vom Typ E_COMPILE_ERROR wurde in der Zeile 62 der Datei /home/wp/disk/wordpress/wp-content/plugins/matomo/classes/WpMatomo/Bootstrap.php verursacht. Fehlermeldung: require_once(): Failed opening required ‘/home/wp/disk/wordpress/wp-content/plugins/matomo/app/bootstrap.php’ (include_path=’.:/usr/share/php’)

    Plugin Author Thomas

    (@tsteur)

    Hi @angiepunkt sorry to hear that happened again. I’ve just installed most of the same plugins you are having (some I couldn’t install because they aren’t on the WordPress plugins directory). I looked if maybe some other plugin would by accident remove that file but couldn’t find anything so far. Do you know if you maybe recently removed or updated some other plugins? I assume this happened in the very same WordPress as before?

    It’s almost like some other plugin or something seems to remove that file. “bootstrap.php” is used by quite a few plugins. Or do you know maybe about any deploy process that might remove this file somehow?

    We don’t ever remove this file as part of our plugin so it’s not quite clear how this could happen.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘E_COMPILE_ERROR’ is closed to new replies.