Plugin helper file
Plugin authors can add alternative code to a plugin helper file in order to load code for their plugins that is compatible with the VIP Platform.
Ready to get started with WordPress VIP? Contact us
Showing page 8 of 26
Plugin authors can add alternative code to a plugin helper file in order to load code for their plugins that is compatible with the VIP Platform.
The application view in the VIP Dashboard provides access to more information about the environments that belong to an application and manage their settings.
The organization view of the VIP Dashboard provides access to more information about the applications and team members that belong to that organization.
A general-purpose webhook URL can be configured for the Destinations of organization and application Notifications and Important Alerts.
Notifications for an application are configured per-environment type (production vs. non-production), or for a single specific environment of that application.
Notifications for an organization are configured per-environment type (production vs. non-production) of its applications, or for a single specific environment.
Notifications for an event are sent to a Destination. Destinations can be a webhook URL for Slack, Google Chat, or Microsoft Teams, a general-purpose webhook URL, or an email address.
Notifications are automated messages triggered by events that occur on the environments of an organization’s applications (e.g., code deployments, performance metrics anomalies, plugin vulnerabilities identified in application code). All types of Notifications, including Important Alerts, can be configured in the VIP Dashboard.
The branch of VIP MU plugins that deploys to an environment—production branch or staging branch—can be configured in the Software Versions panel of the VIP Dashboard.
Once the New Relic Integration has been activated for an environment, users can be granted access to the New Relic dashboard.