/private directory
Files added to the /private directory are not web accessible, but can be accessed by an application’s theme, plugins, or CLI commands.
Ready to get started with WordPress VIP? Contact Us
Showing page 24 of 26
Files added to the /private directory are not web accessible, but can be accessed by an application’s theme, plugins, or CLI commands.
The /themes directory is mapped to /wp-content/themes/ ; this directory works similarly to WP_CONTENT_DIR . '/themes/' in a self-hosted WordPress installation.
The VIP Platform’s Must Use plugins (VIP MU plugins) are deployed to all VIP Platform WordPress applications. The VIP MU plugins codebase provides WordPress applications with integration to the VIP Platform infrastructure (e.g. cache management), helper functions useful to developers, managed plugin options, and commonly used performance enhancements.
Files located within the /images directory will be publicly accessible at the base path /wp-content/images/. Additions, removals, or updates to files in the /images directory must be made through GitHub. These files can not be managed or accessed from within a site’s WordPress Media Library.
All third-party plugins that are added to a site on the WordPress VIP Platform should be kept up to date with their latest available version.
The WordPress load order hook that is used to activate a plugin determines which point within the load process that plugin will load.
On the VIP Platform the /mu-plugins directory is not directly accessible, and will not appear in a site’s code repository. Instead, plugins can be loaded as MU (“must use”) plugins by adding them to the /client-mu-plugins directory found in the root of a site’s code repository. The /client-mu-plugins directory works similarly to WP_CONTENT_DIR . '/mu-plugins/' in a self-hosted WordPress installation.
The /plugins directory is mapped to /wp-content/plugins/ ; this directory works similarly to WP_CONTENT_DIR . '/plugins/' in a self-hosted WordPress installation.
Themes and plugins can only be installed, updated, or deleted via the application’s wpcomvip GitHub repository; they cannot be installed, updated, or deleted in the WordPress Admin dashboard.
Some functions in WordPress Core are purposely uncached, and will always result in an SQL query when called. This can have performance implications for a site.