We are now working on a custom web site test suite written in Playwright running in Node.js.
What is Playwright? The npm, Inc. site says on their Playwright page says
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API. Playwright is built to enable cross-browser web automation that is ever-green, capable, reliable and fast.
We will then host it on one of our WebApps accounts for our client.
This week we completed an export and then conversion of a knowledge base, from a third party commercial “online knowledge base” provider, to DokuWiki format.
A software firm from New Zealand contacted us to do this job for them, and then host their new wiki.
Migrating from Drupal 7 to Drupal 10 isn’t a straightforward upgrade; it’s a complete site rebuild. This means that for anyone currently running a site on Drupal 7, transitioning to Drupal 10 will involve recreating the entire structure, design, and functionality of the website. Alternatively, this transition could also be an opportunity to consider other platforms, such as WordPress, which would similarly require a full rebuild but might offer different advantages depending on your site’s goals and audience.
The level of effort required depends on several factors, including the amount and type of content, the specific features in use, and the overall complexity of the site. Sites with intricate customizations, numerous content types, or complex workflows will need more extensive planning and development time than simpler setups.
In terms of cost, rebuilding a site from Drupal 7 to Drupal 10 or migrating to WordPress typically ranges from $2,000 to $5,000. This range reflects the time and expertise needed to ensure a smooth transition, with attention to preserving functionality, enhancing user experience, and maintaining security on the new platform—whether you choose to stay with Drupal or make the switch to WordPress.
https://www.php.net/manual/en/migration83.php
PHP 8.1 will remain the default PHP version for new accounts and subdomains on our servers. As always, you can configure the new PHP version on a per-subdomain basis through the hosting Control Panel > PHP Settings section.
Error creating thumbnail: File missing
This can happen when all the images are indeed in the correct locations.
One easy way to fix this is to set the $wgCacheEpoch variable as per the manual:
We will give at least 7 days notice, but between September 1st 2023 and October 1st 2023, Miraheze will cease to exist as a wiki farm.
We have begun to transfer wikis from Miraheze to our servers. They also mention there:
From the date above for an indefinite period of time as funds allow, Miraheze will have all backups of all wikis available upon request. The domain will remain active with information displaying how to access these dumps.
Any interested parties should use our Contact Us to discuss how we can help. Our hosting is not free, but with us, you indeed get quality hosting and quality support in return for your purchase.
have the code ready for Javascript. You must of course enter your API key.
The only other point they don’t mention is the parameters for the search call. The ‘q’ parameter is the standard search text. Then the ‘cx’ parameter is required, and that’s the ID of your Google Custom Search Engine. So this line:
return gapi.client.search.cse.list({})
must look more like this:
return gapi.client.search.cse.list({
“cx”: “XXXXXXX”,
“q”: “My Search Text”
})
With that, it works very well. 🙂
Subaddressing allows you to use multiple email addresses as subaddresses within a single e-mail account. Our system supports subaddresses with minus addressing. It works by adding a “-” sign followed by a keyword to the local part of the email address, just before the “@” symbol.
For example, if your email address is contact@example.com, you can use subaddresses like contact-work@example.com or contact-personal@example.com. Messages sent to a subaddress will be delivered to the main address (contact@example.com in this case). You can use subaddresses for different purposes such as filtering emails, tracking the source of spam, or organizing messages into specific folders.
You can see our FAQ on this here: Email subaddressing.
Note that we only support the “-” character for sub-addressing and CiviCRM by default uses the “+” character. The truth is, however, that VERP separator may be any other character as well. It is configured via the “Administer -> CiviMail -> Mail Settings -> VERP Separator” area in CiviCRM.