/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.
Tag: tech-ref
Showing page 24 of 26
/themes directory
The /themes directory is mapped to /wp-content/themes/ ; this directory works similarly to WP_CONTENT_DIR . '/themes/' in a self-hosted WordPress installation.
Developing on WordPress VIP
WordPress VIP’s infrastructure is built with robust, built-in security and performance enhancement features. Because of these customizations, developers will find that several aspects of the platform are dissimilar to other hosting platforms. The information below is intended to highlight some of those differences for developers who are new to the VIP Platform and provide an overview of the tools and accounts that they need to get started.
VIP MU plugins
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.
/images directory
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.
Version updates for third-party plugins
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. It is the responsibility of the customer and their developer teams to maintain, test, and update the plugins installed on their sites.
Load order of plugins
Depending on the method used to activate a plugin, it will hook into the WordPress load order at different points. Plugins will load based on the following hooks—from earliest to latest in the WordPress load process—when activated with the described methods:
/client-mu-plugins directory
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.
/plugins directory
The /plugins directory is mapped to /wp-content/plugins/ ; this directory works similarly to WP_CONTENT_DIR . '/plugins/' in a self-hosted WordPress installation.
Add a plugin
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.