Validating, sanitizing, and escaping
When writing theme and plugin code, it is important to be mindful of how data coming into WordPress is handled and how it is presented to the end user.
Ready to get started with WordPress VIP? Contact us
Showing page 23 of 26
When writing theme and plugin code, it is important to be mindful of how data coming into WordPress is handled and how it is presented to the end user.
All users on the VIP Platform should follow best practices when it comes to securing their devices, accounts, and access to VIP tools.
A best practice in PHP for WordPress is to use escaping functions to prevent Cross Site Scripting (XSS).
Two-factor authentication (also known as 2FA) is a method for securely granting users access to a site or application. This method requires a user to know something (e.g. a password), and requires a user to possess an object (e.g. their mobile device or a hardware security key) or a unique biological trait (e.g. a fingerprint). Requiring multiple forms of verification is a basic way to protect a site against security compromises due to leaked or guessed passwords.
By default, Jetpack is enabled on all WordPress sites hosted on the VIP Platform. Jetpack adds a suite of powerful security, performance, and marketing features. Jetpack features that aid in content consumption, distribution, and syndication are collectively referred to as “content distribution tools“.
VIP-CLI is the command-line interface for VIP Go for interacting with VIP applications and performing actions like syncing data between VIP environments.
Data syncs between VIP Platform environments facilitate testing and quality assurance (QA) of new features and allows teams to accurately reproduce and examine errors in a non-production environment. After a data sync from a production environment to a non-production environment is completed, the target environment will automatically load shared media files that were uploaded to production. This eliminates the need to copy media between environments.
Fetching data from other servers (e.g., fetching information from external APIs or resources) can be a relatively slow process, and issues relating to timeouts can occur. Remote calls such as wp_remote_get(), wp_safe_remote_get() and wp_oembed_get() should rely on the WordPress HTTP API (not cURL) and should be cached.
The Query Cache provides light-weight and transparent in-memory caching of many database queries (such as post lookups) which reduces the overall load on the database and results in a faster, more-scalable site.
Upgrades for major release versions of WordPress can be managed for an environment in the Software Versions panel of the VIP Dashboard.