2
10
14K
0
27 June 2024
01 July 2013
Based on 2 on WordPress.org
As of 1.8.0, you can enable real user monitoring by navigating to the Raygun settings page and checking the Enable Real User Monitoring checkbox.
User information will be sent alongside RUM sessions if you have the Customers feature enabled.
When enabled, the currently logged in user’s email address, first name and last name will be transmitted with each error or session. This will be visible in the Raygun dashboard. If this feature is not enabled, a random ID will be assigned to each user.
This plugin automates the installation of Raygun4PHP, the PHP provider for Raygun.
The server that your WordPress site runs on requires a PHP 7.4 or newer environment. This also requires that your WordPress version be at least 5.3.
This plugin is not guaranteed to work with multisite installations in certain environments. The following procedure should first be followed on a staging server that matches your production environment as closely as possible before being replicated live. It is recommended to use the most recent version WordPress and PHP.
On your root network site, install the plugin using the Admin dashboard’s Plugin page as standard, but do not activate it.
FTP in and modify wp-content/plugins/raygun4wp/raygun4wp.php – change the value on line 16 ($multisite_support_enabled) to true.
Visit the Admin dashboard of a child site (not the root network site). Go to its Plugin page, and you should see Raygun ready to be activated – do so.
A new Raygun submenu will be added to the left sidebar. There, you may click on Settings, paste in your API key, and save changes. You can now click Send Test Error and confirm that it appears in your Raygun dashboard.
Repeat the above process for any other child sites – you can use different API keys (to send to different Raygun applications) or the same one.
Finally, if you so desire, you should be able to visit the root network site, activate it there and configure it. You must, however, activate it on at least one child site first.
When enabled, the currently logged in user’s email address, first name and last name will be transmitted with each error or session. This will be visible in the Raygun dashboard. If this feature is not enabled, a random ID will be assigned to each user.
This plugin automates the installation of Raygun4PHP, the PHP provider for Raygun.
The server that your WordPress site runs on requires a PHP 7.4 or newer environment. This also requires that your WordPress version be at least 5.3.
This plugin is not guaranteed to work with multisite installations in certain environments. The following procedure should first be followed on a staging server that matches your production environment as closely as possible before being replicated live. It is recommended to use the most recent version WordPress and PHP.
On your root network site, install the plugin using the Admin dashboard’s Plugin page as standard, but do not activate it.
FTP in and modify wp-content/plugins/raygun4wp/raygun4wp.php – change the value on line 16 ($multisite_support_enabled) to true.
Visit the Admin dashboard of a child site (not the root network site). Go to its Plugin page, and you should see Raygun ready to be activated – do so.
A new Raygun submenu will be added to the left sidebar. There, you may click on Settings, paste in your API key, and save changes. You can now click Send Test Error and confirm that it appears in your Raygun dashboard.
Repeat the above process for any other child sites – you can use different API keys (to send to different Raygun applications) or the same one.
Finally, if you so desire, you should be able to visit the root network site, activate it there and configure it. You must, however, activate it on at least one child site first.
This plugin automates the installation of Raygun4PHP, the PHP provider for Raygun.
The server that your WordPress site runs on requires a PHP 7.4 or newer environment. This also requires that your WordPress version be at least 5.3.
This plugin is not guaranteed to work with multisite installations in certain environments. The following procedure should first be followed on a staging server that matches your production environment as closely as possible before being replicated live. It is recommended to use the most recent version WordPress and PHP.
On your root network site, install the plugin using the Admin dashboard’s Plugin page as standard, but do not activate it.
FTP in and modify wp-content/plugins/raygun4wp/raygun4wp.php – change the value on line 16 ($multisite_support_enabled) to true.
Visit the Admin dashboard of a child site (not the root network site). Go to its Plugin page, and you should see Raygun ready to be activated – do so.
A new Raygun submenu will be added to the left sidebar. There, you may click on Settings, paste in your API key, and save changes. You can now click Send Test Error and confirm that it appears in your Raygun dashboard.
Repeat the above process for any other child sites – you can use different API keys (to send to different Raygun applications) or the same one.
Finally, if you so desire, you should be able to visit the root network site, activate it there and configure it. You must, however, activate it on at least one child site first.
This plugin is not guaranteed to work with multisite installations in certain environments. The following procedure should first be followed on a staging server that matches your production environment as closely as possible before being replicated live. It is recommended to use the most recent version WordPress and PHP.
On your root network site, install the plugin using the Admin dashboard’s Plugin page as standard, but do not activate it.
FTP in and modify wp-content/plugins/raygun4wp/raygun4wp.php – change the value on line 16 ($multisite_support_enabled) to true.
Visit the Admin dashboard of a child site (not the root network site). Go to its Plugin page, and you should see Raygun ready to be activated – do so.
A new Raygun submenu will be added to the left sidebar. There, you may click on Settings, paste in your API key, and save changes. You can now click Send Test Error and confirm that it appears in your Raygun dashboard.
Repeat the above process for any other child sites – you can use different API keys (to send to different Raygun applications) or the same one.
Finally, if you so desire, you should be able to visit the root network site, activate it there and configure it. You must, however, activate it on at least one child site first.