After setup the PHP unit test on your Windows operating system maybe you get below error:
PHP Warning: require_once(/tmp/wordpress//wp-includes/class-phpmailer.php): failed to open stream: No such file or directory in C:\Users\MaheshW\AppData\Local\Temp\wordpress-tests-lib\includes\mock-mailer.php o
n line 2
...
...
Warning: require_once(/tmp/wordpress//wp-includes/class-phpmailer.php): failed to open stream: No such file or directory in C:\Users\MaheshW\AppData\Local\Temp\wordpress-tests-lib\includes\mock-mailer.php on lin
e 2
...
...
PHP Fatal error: require_once(): Failed opening required '/tmp/wordpress//wp-includes/class-phpmailer.php' (include_path='C:\xampp\php\PEAR') in C:\Users\MaheshW\AppData\Local\Temp\wordpress-tests-lib\includes\
mock-mailer.php on line 2
...
...
Fatal error: require_once(): Failed opening required '/tmp/wordpress//wp-includes/class-phpmailer.php' (include_path='C:\xampp\php\PEAR') in C:\Users\MaheshW\AppData\Local\Temp\wordpress-tests-lib\includes\mock-
mailer.php on line 2
...
...
In file C:\Users\MaheshW\AppData\Local\Temp\wordpress-tests-lib\wp-tests-config.php line 7 has code:
Before writing about how to create a website screenshot of website with CLI command, I think, I need to share some background.
Recently, I was working on some project in which I need to set 1000+ web page screenshots and resize them and set as a featured featured image for the post.
In this article I’ll just share how to capture the website screenshot with the CLI command. I’ll create another article to share how I was resize the screenshot and set the featured images in future articles.
Research About the Right Tool
I have research about this and found some below tools.
After some research, I have tried all of the above tools and finally select the capture-website-cli because of it fulfill all my requirement and also create better screenshots.
After executing the above command below screenshot is generated.
In above screenshot the string Mahesh Waghmare and This Screenshot is generated with 'capture-website-cli'. And also the string "Mahesh Waghmare" and this paragraph both are also injected with the JavaScript while creating https://wordpress.org/ web page screenshot.
Both are added though JS by injecting it with custom JS file while creating screenshot.
In above command the parameter --script is used. In which the script.js is set. And in this JS file I have write the below code:
Additional Parameters
Don’t forget try below parameters too. These are interesting.
--width Page width [default: 1280]
--height Page height [default: 800]
--type Image type: png|jpeg [default: png]
--quality Image quality: 0…1 (Only for JPEG) [default: 1]
--scale-factor Scale the webpage n times [default: 2]
--list-devices Output a list of supported devices to emulate
--emulate-device Capture as if it were captured on the given device
--full-page Capture the full scrollable page, not just the viewport
--no-default-background Make the default background transparent
--timeout Seconds before giving up trying to load the page. Specify 0 to disable. [default: 60]
--delay Seconds to wait after the page finished loading before capturing the screenshot [default: 0]
--wait-for-element Wait for a DOM element matching the CSS selector to appear in the page and to be visible before capturing the screenshot
--element Capture the DOM element matching the CSS selector. It will wait for the element to appear in the page and to be visible.
--hide-elements Hide DOM elements matching the CSS selector (Can be set multiple times)
--remove-elements Remove DOM elements matching the CSS selector (Can be set multiple times)
--click-element Click the DOM element matching the CSS selector
--scroll-to-element Scroll to the DOM element matching the CSS selector
--disable-animations Disable CSS animations and transitions [default: false]
--module Inject a JavaScript module into the page. Can be inline code, absolute URL, and local file path with .js extension. (Can be set multiple times)
--script Same as --module, but instead injects the code as a classic script
--style Inject CSS styles into the page. Can be inline code, absolute URL, and local file path with .css extension. (Can be set multiple times)
--header Set a custom HTTP header (Can be set multiple times)
--user-agent Set the user agent
--cookie Set a cookie (Can be set multiple times)
--authentication Credentials for HTTP authentication
--debug Show the browser window to see what it’s doing
--launch-options Puppeteer launch options as JSON
--overwrite Overwrite the destination file if it exists
Hope you enjoy this article. Try it yourself and let me know for any question. Some useful link:
Example 2: In below example I’m translating ShortcodeHub plugin.
E.g. To download the plugin .po files Im using command wp wpi18n download_plugin_po shortcodehub --lang=mr
D:\xampp\htdocs\wpi18n\wp-content\plugins\wp-i18n (master)
λ wp wpi18n download_plugin_po shortcodehub --lang=mr
shortcodehub | CREATED - po-files/plugins/shortcodehub/mr/wp-plugins-shortcodehub-dev-mr.po | https://translate.wordpress.org/projects/wp-plugins/shortcodehub/dev/mr/default/export-translations
shortcodehub | CREATED - po-files/plugins/shortcodehub/mr/wp-plugins-shortcodehub-dev-readme-mr.po | https://translate.wordpress.org/projects/wp-plugins/shortcodehub/dev-readme/mr/default/export-translations
shortcodehub | CREATED - po-files/plugins/shortcodehub/mr/wp-plugins-shortcodehub-stable-mr.po | https://translate.wordpress.org/projects/wp-plugins/shortcodehub/stable/mr/default/export-translations
shortcodehub | CREATED - po-files/plugins/shortcodehub/mr/wp-plugins-shortcodehub-stable-readme-mr.po | https://translate.wordpress.org/projects/wp-plugins/shortcodehub/stable-readme/mr/default/export-translations
Now, Im using command wp wpi18n generate_plugin_po shortcodehub --lang=mr to auto generate the .po files.
E.g. It looks like below:
D:\xampp\htdocs\wpi18n\wp-content\plugins\wp-i18n (master)
λ wp wpi18n generate_plugin_po shortcodehub --lang=mr
shortcodehub | 4 | 178 | 4508 UPDATED Documentation | WITH डोक्युमेंटशन
shortcodehub | 4 | 177 | 0 NOT EXIST Support
...
...
shortcodehub | 1 | 2 | 0 NOT EXIST Fix: Updated wrong 5 star rating link from dashboard page
shortcodehub | 1 | 1 | 0 NOT EXIST Initial release
shortcodehub | 1 | COMPLETE - TRANSLATED 36 STRINGS
shortcodehub | 1 | po-files/plugins/shortcodehub/mr/wp-plugins-shortcodehub-stable-readme-mr-translated.po
shortcodehub | TOTAL TRANSLATED 36
ALL TRANSLATED STRINGS COUNT: 2901
Screenshot for reference:
After executing both commands we have 36 auto translated strings. Also we have 2901 available strings in Marathi language.
All translated strings are stored in directory: /wp-i18n/po-files/plugins/shortcodehub/mr/
Now file wp-plugins-shortcodehub-dev-mr.po is original file and wp-plugins-shortcodehub-dev-mr-translated.po is translated file.
We can use this auto translated file and import into Glotpress.
To confirm the translated strings the log file is generated which show all the translated strings. E.g. /wp-i18n/po-files/plugins/shortcodehub/mr/log.txt
This file show the content like below:
1 | Documentation | डोक्युमेंटशन
2 | Version %s | आवृत्ती %s
...
...
36 | Features | वैशिष्ट्ये
I notice that there are lot of common strings which are already translated in WordPress core releases.
E.g. Strings Leave a comment, Comment Content, Comment Date, Completed are some of the common strings examples which already translated into WordPress core releases.
In this article I’m giving an example of Marathi (मराठी) (mr) which have now 160 contributors.
With this option we can export the translated project translated strings in below formats:
Android XML (.xml)
Portable Object Message Catalog (.po/.pot)
Machine Object Message Catalog (.mo)
.NET Resource (.resx)
Mac OS X / iOS Strings File (.strings)
Java Properties File (.properties)
JSON (.json)
Jed 1.x (.json)
NGX-Translate (.json)
Development Background
I have create a fresh WordPress setup and created a plugin wpi18n.
In this plugin I have register a post type which store the original string as a post title.
And its translated language version in post meta.
E.g.
Now,
I have downloaded the .po files of all the core projects from 4.1.x to dev with the help of WP CLI command wp wpi18n download_all_core_files
We have all the translated files of each core release of each language. To process all languages it takes too much time. So, I have added the individual language support for importing the translated strings.
The CLI command wp wpi18n import_translated_strings mr download the original & translated string in Marathi language.
After importing strings, I notice that there are lot of strings which are translated as different in different core projects.
E.g. The string Leave a comment is translated as below:
टिपणी करा (4-1-x)
प्रतिक्रिया लिहा (4-2-x)
टिपणी करा (4-3-x)
टिपणी करा (4-4-x)
टिपणी करा (4-5-x)
टिपणी करा (4-6-x)
टिपणी करा (4-7-x)
टिपणी करा (4-8-x)
टिपणी करा (4-9-x-development)
So, To keep the consistency I have used most repetitive strings as a translated strings. E.g.
(8 times) टिपणी करा
(1 times) प्रतिक्रिया लिहा
So, I have used string टिपणी करा to auto translate the string Leave a comment in theme and plugin.
Some other examples:
Example 2: String – Password: have 3 variations in Marathi (mr) language as below:
To detect all the repeated strings I have created the command which generate the file of all repeated strings.
To discuss with other teammates and confirm it works for all languages I have created a log file which show the original string and its log of repetitive strings with most repetitive string.
Below are the some language files:
ru [85] – http://tinyurl.com/yb9ew4yk
ary [264] – http://tinyurl.com/y7achghc
mr [683] – http://tinyurl.com/y8m4vdb2
hi [1103] – http://tinyurl.com/y9pgvllx
To translate the string into any language I have create a command which set the most repeated string into the meta box.
E.g. String Sites is most 3 time repeated with Сайты So, I have set this most repeated string and used it while translating the string with CLI.
I have created some commands to auto generate the .po file of any theme/plugin.
// Commands to download the .po files of theme/plugin.
wp wpi18n download_plugin_po {plugin-slug} --lang={language}
wp wpi18n download_theme_po {theme-slug} --lang={language}
// Commands to generate the .po files of theme/plugin.
wp wpi18n generate_theme_po {theme-slug} --lang={language}
wp wpi18n generate_plugin_po {plugin-slug} --lang={language}
To confirm strings, I have first used my own native language and I found that its 100% works. After that I have tried another language.
After translating plugins and themes I found that the Import Translation feature just import any .po file and detect the string into it.
Finally, I have create each language .po file which set the most repeated string as a translation string. And imported it into the theme/plugin. And it works as expected.
Known Issues
After discuss with yui, I found that the repeated strings are depends on plural/singular, male, female or neutral or sometimes its participle highly depends on context.
The string Sites is translated as in (4-1-x-administration-network-admin) as сайтов because it has the context.
And in (4-1-x) its Сайты because there is no context.
While translating strings It does not check its context. I’ll discuss with community and maybe change this or maybe implement another way to do this same thing.
GlotPress Background
WordPress use the GlotPress to translate the strings from WordPress Core, Themes, Plugins etc.
In GlotPress Roadmap there is a target Translation Memory which is scheduled for version x+5. It is the almost same as reusing strings from existing approved strings.
I have read about this from below reference links:
I’ll discuss this with the Polyglot team on slack channel. You can also try this for your theme/plugin. Its super easy. Just you wan’t to setup the WP CLI on your local environment.
I personally work on Github, GitLab and BitBucket. I’m more familiar with Git commands.
WordPress itself use the SVN for hosting plugins and themes. I have created a WordPress Theme and Plugins. But, I personally not use SVN though command line.
I personally use Tortoise SVN for managing my theme and plugins. It provides a GUI (Graphic User Interface) which allow working on SVN with a very easy way. Read more about Tortoise SVN.
I was always querying about,
How to work on SVN though command line?
Which are the basic SVN commands like Git?
What is the difference between Git and SVN commands?
etc.
I’ll create an article on all the above questions which I have tried to resolve soon.
For now, I have created a table of Git vs SVN commands. You can also check below the table of Git vs SVN commands for reference.
You can add a download button on your website with the link of latest plugin zip. So, Your users always get the latest zip of your plugin which is hosted on wp.org.
Same like a plugin, You can add a download button on your website with the link of your latest theme zip. So, Your users always get the latest zip of your theme which is hosted on wp.org.
WordPress multisite introduces a new database table wp_blogmeta to store metadata associated with sites. This allows for the storage of arbitrary site data relevant in a multisite/network context.
It provides an alternative to using options and can be retrieved from multiple sites in a more performant way—without calling switch_to_blog(). Sites can now also be queried by their meta with parameters supported by WP_Meta_Query.
Note: A network update is required to install the new database table.
All of these functions are ONLY available in multisite, however they work similarly to other metadata wrapper functions, such as for posts, terms, comments and users. In addition to these functions, it is now possible to use the common meta query arguments when querying sites with WP_Site_Query or its wrapper get_sites().
WordPress 5.1 will start showing notices to administrators of sites that run on long outdated PHP versions. (Below PHP 5.6 version). See bump of the minimum required PHP version.
Warning about outdated PHP version in WordPress backend
Provided filter wp_update_php_url for a more dynamic approach on the code level. Replacing the URL should happen in cases where a more specific guide to update PHP on the given environment exists. E.g. screenshot:
Warning about outdated PHP version with custom URL and related annotation
Fatal Error Protection with the so-called WSOD protection (white-screen-of-death protection), A mechanism has been implemented to detect fatal errors and, in certain designated areas of WordPress, recover from them. E.g. Screenshot.
Default output in the frontend when WSOD protection detects has detected an error
Note that, while the primary reason for implementing the fatal error protection mechanism was making the process of updating PHP less “dangerous”, it is technically not tied to the update at all. In fact, it will be enabled permanently and discover fatal errors under any circumstances.
The functionality can also be disabled entirely if that is preferred, via a new constant WP_DISABLE_FATAL_ERROR_HANDLER or, more dynamically, a corresponding wp_fatal_error_handler_enabled filter.
WordPress 5.1 will display a warning for those plugins that require a higher PHP version than the one currently active.
