WPMU DEV In Your Language
Translation of Hummingbird: Spanish (Spain)
| Prio | Original string | Translation | — |
|---|---|---|---|
| https://wpmudev.com/ | You have to log in to add a translation. | Details | |
|
https://wpmudev.com/ You have to log in to edit this translation.
or Cancel
|
|||
| https://wpmudev.com/project/wp-hummingbird/ | You have to log in to add a translation. | Details | |
|
https://wpmudev.com/project/wp-hummingbird/ You have to log in to edit this translation.
or Cancel
|
|||
| Note: Scheduled uptime reports are only available for network sites and not subsites. This is because the network sites and subsites are located on the same server, meaning that subsite uptime reports would be redundant. | You have to log in to add a translation. | Details | |
|
Note: Scheduled uptime reports are only available for network sites and not subsites. This is because the network sites and subsites are located on the same server, meaning that subsite uptime reports would be redundant. You have to log in to edit this translation.
or Cancel
|
|||
| Email Reports | You have to log in to add a translation. | Details | |
|
Email Reports You have to log in to edit this translation.
or Cancel
|
|||
| Database entries removed successfully. | You have to log in to add a translation. | Details | |
|
Database entries removed successfully. You have to log in to edit this translation.
or Cancel
|
|||
| Not enough permissions to access the endpoint. | You have to log in to add a translation. | Details | |
|
Not enough permissions to access the endpoint. You have to log in to edit this translation.
or Cancel
|
|||
| Import an exported Hummingbird settings file to apply the Manual Asset Optimization configuration. | You have to log in to add a translation. | Details | |
|
Import an exported Hummingbird settings file to apply the Manual Asset Optimization configuration. You have to log in to edit this translation.
or Cancel
|
|||
| Use this tool to import the Manual Asset Optimization configuration from another site. | You have to log in to add a translation. | Details | |
|
Use this tool to import the Manual Asset Optimization configuration from another site. You have to log in to edit this translation.
or Cancel
|
|||
| Set Expires by Type to %1$s31536000 (1 year)%2$s to meet Google’s recommended benchmark. | You have to log in to add a translation. | Details | |
|
Set Expires by Type to %1$s31536000 (1 year)%2$s to meet Google’s recommended benchmark. You have to log in to edit this translation.
or Cancel
|
|||
| Manually configure the %1$sCache-Control%2$s header for browser caching in your WebAdmin Console following the Open LiteSpeed guide <a href="%3$s" target="_blank">here</a>. | You have to log in to add a translation. | Details | |
|
Manually configure the %1$sCache-Control%2$s header for browser caching in your WebAdmin Console following the Open LiteSpeed guide <a href="%3$s" target="_blank">here</a>. You have to log in to edit this translation.
or Cancel
|
|||
| The Asset Optimization feature optimizes your files and in doing so, it creates database entries. Problems related to Asset Optimization can be settled by deleting the database data, which will substantially reset the feature. | You have to log in to add a translation. | Details | |
|
The Asset Optimization feature optimizes your files and in doing so, it creates database entries. Problems related to Asset Optimization can be settled by deleting the database data, which will substantially reset the feature. You have to log in to edit this translation.
or Cancel
|
|||
| Asset Optimization - Database Data | You have to log in to add a translation. | Details | |
|
Asset Optimization - Database Data You have to log in to edit this translation.
or Cancel
|
|||
| Note: The data we are referring to do not relate to the posts in the wp_posts table. | You have to log in to add a translation. | Details | |
|
Note: The data we are referring to do not relate to the posts in the wp_posts table. You have to log in to edit this translation.
or Cancel
|
|||
| When an asset is optimized, it is mapped to a hidden custom post type, which has multiple entries of metadata in the wp_postmeta table. Clearing Asset Optimization cache should remove both the custom post type and its multiple meta fields. But in rare cases, when a custom post type is removed, the data in the wp_postmeta table remains and can bloat the database. This can be fixed by deleting the data stored in the wp_postmeta table. | You have to log in to add a translation. | Details | |
|
When an asset is optimized, it is mapped to a hidden custom post type, which has multiple entries of metadata in the wp_postmeta table. Clearing Asset Optimization cache should remove both the custom post type and its multiple meta fields. But in rare cases, when a custom post type is removed, the data in the wp_postmeta table remains and can bloat the database. This can be fixed by deleting the data stored in the wp_postmeta table. You have to log in to edit this translation.
or Cancel
|
|||
| Deleting... | You have to log in to add a translation. | Details | |
|
Deleting... You have to log in to edit this translation.
or Cancel
|
|||
Export as •
Translators
- Jorge Díaz: 23.5%
- hernestra: 7.5%
- Nacho Aldama: 6.1%
- Jhon Hernandez: 3.4%
- BKBAI: 2.6%
- JersonFlorez: 0.3%
- Mugikor App: 0.2%
- Tom: 0.1%
- Cristian: 0.1%
- Erick Fogtman: 0.1%
- Atsekabe: 0.1%
