Documentation VIP Go VIP Go FAQ


Documentation for VIP Go is still being developed. For now we’re putting some answers to frequently asked questions here and will expand these answers into more complete docs as needed.

Q: What version of PHP is VIP Go running?
A: We’re running 7.0.

Q: Where do themes and plugins go on VIP Go?
A: You can add themes to the themes directory. You can add plugins to the plugins directory. Plugins can be activated in code using wpcom_vip_load_plugin. We have some remnant shared plugins in VIP Go currently, but we aim to remove them all soon; accordingly, you must include plugins you wish to use in your site plugins directory. A copy of a plugin in the site plugins directory will be used in preference to any copy in the muplugins/shared-plugins directory.

Q: Can we add third-party plugins and libraries/SDKs inside the plugins directory?
A: Yes. These still need to go through code review. Note that you can use git submodules where the source repository is public, but we do not support private submodules.

Q: How does deploying code work?
A: When you push changes to the master branch of your site’s repository, it will get pushed into a “deploy queue” here, where we review it before it goes out to production. There’s no need to open a ticket to request a deploy.

Q: Do static files (CSS, images, etc) auto-deploy like they do on VIP?
A: No, there is not currently any automatic deployment of files based on file type. We may add this in the future.

Q: Can I use capital letters in file paths?
A: Yes.

Q: How does file concatenation and minification work on VIP Go?
A: VIP Go will concatenate and minify files in the same ways that VIP does. If you minify files in your theme, you should also include the source files for code review.

Q: How does setting permalinks work?
A: You can set permalinks normally. Permalinks do not get flushed on deploy, instead you can include the Rewrite Rules Inspector plugin and use this to flush the rewrite rules.

Q: Can we use the “www” version of a domain, or do we have to use the non-www/root version?
A: You can use the “www” version of a domain (and the root/non-www version will also work). You can set up any needed redirects directly in the `vip-config.php` file for your website, or from within WordPress. Please note sub-subdomains are not supported at this time.

Q: Can I get a SQL dump of my site?
A: You can log into VaultPress and get a SQL backup of your site. Note, it is required to remove the jetpack_options option before MySQL exports/imports into a local development or staging environment, otherwise this will create Jetpack issues on your production site.

Q: How do I make a VIP Go site private and/or discourage search engines from indexing it?
A: We automatically add a “Disallow: /” robots.txt response for sites using the domain, but otherwise do not handle blocking/managing access for private sites at a platform level. You’re welcome to include any plugins you want to use that meet your needs and that follow VIP code guidelines.

Q: How do I enable sitemaps on VIP Go?
A: The MSM Sitemap plugin isn’t available on VIP Go by default, but you can use it as a git submodule if desired. The wpcom-sitemap.php plugin, which enables “news” sitemaps, is available via our shared plugins directory.

Q: Is there asynchronous job processing on VIP Go like there is on What about asynchronous exports for large sites?
A: No, there are not currently any asynchronous job processing options on VIP Go – all cron calls will be processed in core WordPress. If you have a large site to export, please open a support ticket and we can perform that for you directly.

Q: Can WP CLI commands be run on VIP Go?
A: Yes, please open a support ticket and we’ll be happy to run WP CLI commands on your behalf.

Q: Can I tailor the new user signup flow?
A: Yes, because each VIP Go site is a standalone install of WordPress with its own database, including the user table, VIP Go site owners are able to configure their own signup flow as they require.

Q: How do scheduled jobs (Cron) work on VIP Go?
A: Scheduled jobs on VIP Go use the WP Cron API provided by WordPress core. The cron jobs are initiated and regulated via the WP Cron Control plugin. We trigger this on a one minute interval via HTTP request from our Jobs System.

Q: How does SSL/HTTPS work on VIP Go?
A: A VIP Go site must have an SSL certificate installed in order to be active. Because every site uses a custom domain for both the front-end and admin area, and because we want each site to have a secure admin area and login process at minimum, SSL is a requirement. Read more about SSL on VIP Go.

Q: Does VIP Go support HTTP/2?
A: Yes. HTTP/2 is supported and enabled for all sites hosted on the VIP and VIP Go platforms. HTTP/2 requires that SSL be enabled to work. We currently do not support the server push functionality of the HTTP/2 specification.

Q: Can we have access to the filesystem to support a build process?
A: No. If you need to do a build one option is to use a CI tool like Travis to build from a working branch to the master branch, or similar, please contact us to discuss your requirements as this can complicate code review for your site.

Q: Does VIP Go have the “protected embeds” feature from
A: No. The VIP protected embeds feature is specific to that platform. On VIP Go there are two alternatives: (1) build shortcodes into the theme for the embeds you need (probably the safest option) or (2) implement your own protected embeds style solution for your site (here is a plugin used by some VIP Go clients for doing this).


Documentation is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.