~/virtual/home/joho | DeltaFelter | Stealth Cookie | FidoNet | Joaquim Homrighausen | joho68
Cloudbridge Mattermost is a WordPress plugin that provides integration between WordPress and Mattermost.
Cloudbridge Mattermost 2.1.0 has been released with fixes and new features!
New features include support for Cloudflare and verified WordPress 5.8 compatibility.
You can read more about it here: code.webbplatsen.net/wordpress/cloudbridge-mattermost. It is available via the WordPress plugin repository and from GitHub
The EasyMap for WordPress plugin provides uncomplicated Google Maps functionality for your WordPress web site. It allows a great deal of control over Google Maps features and comes with support for pre-defined location address formats as well as a custom template editor.
Basic functionality includes:
EasyMap on wordpress.org:
wordpress.org/plugins/easymap/
There’s more EasyMap information available here:
code.webbplatsen.net/wordpress/easymap
The Shortcodes for Font Awesome (SCFA) plugin has been updated to version 1.2.1 with fixes and verified compatibility with WordPress 5.8. The updated version is available via the WordPress Plugin repository and code.webbplatsen.net
One truly annoying thing with WordPress is that it doesn’t use the mbstring extensions at its core. I fully realize how big of a task a re-write is in this regard, but considering there are utility functions for just about everything you want to do as a WordPress plugin and/or theme developer, I think this needs to be addressed. Oh, and it’s 2021 by the way.
An issue that quite a few seem to be frustrated about is POST/GET form data handling, and the situation with single and double quotes being “escaped”.
Without further ado, this snippet will “unslash” a string, with support for multibyte characters (there’s no magic here, really):
function x_stripslashes( string $str ) {
return( mb_ereg_replace( '[\x{005c}][\x{0027}]', '\'',
mb_ereg_replace( '[\x{005c}][\x{0022}]', '"',
$str ) )
);
}
WP_List_Table
Whether or not it’s a good idea to use WP_List_Table for your plugin is beyond the scope of this post.
While developing a plugin that is using WP_List_Table, I came across a rather well-known issue. The issue is that once the user enters search data, you would (logically) think that the search data is maintaned while navigating the search result. Unfortunately, when the user clicks on the previous and next links, or clicks on one of the table headers to re-sort the search result, the search is “lost”.
This can, technically speaking, be avoided if you resort to using METHOD="GET" rather than METHOD="POST" in your table form. But I wanted to avoid this since the entire GET request is passed in the URL and thus ends up in logs, etc.
So, how to use POST instead of get, and still maintain the search parameter across page loads?
The WP_List_Table class makes extensive use of the set_url_scheme() function to create various headers and clickable links in the table view. Unfortunately, this function is rather generic in nature and does not take the parameters from WP_List_Table::search_box() into account. But, as is the case with most functions in WordPress, as a last action, the set_url_scheme() function calls any hooked filters before it returns.
The example assumes $your_table is an object derived from WP_List_Table.
echo '<div class="wrap">'; echo '<form action="admin.php?page=your_plugin_table" method="post" name="your_table_form">'; $your_table->prepare_items(); $your_table->mangle_url_scheme_start(); $your_table->search_box(); $your_table->display(); $your_table->mangle_url_scheme_stop(); echo '</form>'; echo '</div>';
The two functions of interest here are mangle_url_scheme_start() and its companion, mangle_url_scheme_stop(). These go into your class derived from WP_List_Table like this:
public function mangle_url_scheme_start() {
add_filter( 'set_url_scheme', [$this, 'mangle_url_scheme'], 10, 3 );
}
and
public function mangle_url_scheme_stop() {
remove_filter( 'set_url_scheme', [$this, 'mangle_url_scheme'], 10 );
}
The last piece of the workaround is the mangle_url_scheme() function:
public function mangle_url_scheme( string $url,
string $scheme,
$orig_scheme ) {
if ( ! empty( $url )
&& mb_strpos( $url, '?page=your_plugin_table' ) !== false
&& isset( $_REQUEST['s'] ) ) {
$url = add_query_arg( 's', urlencode( $_REQUEST['s'] ), $url );
}
return( $url );
}
This is only done on your plugin table page, and it’s only done if the $_REQUEST['s'] parameter is set. I can’t see how this will cause any issues further down the road, but you may experience different results. You may want to sanitize the contents of $_REQUEST['s'] further before you urlencode it.
I am reasonably convinced that there are other, and better, ways of doing this. But I haven’t found one yet.
The Shortcodes for Font Awesome (SCFA) plugin has been updated to version 1.2.0 with fixes and verified compatibility with WordPress 5.7. The updated version is available via the WordPress Plugin repository and code.webbplatsen.net
Here’s, hopefully, a resonably up to date list of URLs to use for WordPress Update Services in 2021, with duplicates removed 🙂
I don’t think there’s a “best practice” for these, and everyone’s opinion seem to differ on the subject. So I am by no means claiming that this is a complete or good list for WordPress Update Services, but it’s possibly a start.
These go into Settings > Writing > Update Services
http://api.feedster.com/ping http://api.moreover.com/ping http://api.my.yahoo.com/RPC2 http://api.my.yahoo.com/rss/ping http://bing.com/webmaster/ping.aspx http://blogdb.jp/xmlrpc http://blog.goo.ne.jp/XMLRPC http://blogmatcher.com/u.php http://blogping.unidatum.com/RPC2 http://blogsearch.google.ae/ping/RPC2 http://blogsearch.google.at/ping/RPC2 http://blogsearch.google.be/ping/RPC2 http://blogsearch.google.bg/ping/RPC2 http://blogsearch.google.ca/ping/RPC2 http://blogsearch.google.ch/ping/RPC2 http://blogsearch.google.cl/ping/RPC2 http://blogsearch.google.co.cr/ping/RPC2 http://blogsearch.google.co.cr/ping/RPC2 http://blogsearch.google.co.hu/ping/RPC2 http://blogsearch.google.co.hu/ping/RPC2 http://blogsearch.google.co.id/ping/RPC2 http://blogsearch.google.co.id/ping/RPC2 http://blogsearch.google.co.il/ping/RPC2 http://blogsearch.google.co.in/ping/RPC2 http://blogsearch.google.co.it/ping/RPC2 http://blogsearch.google.co.jp/ping/RPC2 http://blogsearch.google.co.ma/ping/RPC2 http://blogsearch.google.com.ar/ping/RPC2 http://blogsearch.google.com.au/ping/RPC2 http://blogsearch.google.com.br/ping/RPC2 http://blogsearch.google.com.co/ping/RPC2 http://blogsearch.google.com.do/ping/RPC2 http://blogsearch.google.com.mx/ping/RPC2 http://blogsearch.google.com.my/ping/RPC2 http://blogsearch.google.com.pe/ping/RPC2 http://blogsearch.google.com/ping/RPC2 http://blogsearch.google.com/ping/RPC2 http://blogsearch.google.com.sa/ping/RPC2 http://blogsearch.google.com.sg/ping/RPC2 http://blogsearch.google.com.tr/ping/RPC2 http://blogsearch.google.com.tw/ping/RPC2 http://blogsearch.google.com.ua/ping/RPC2 http://blogsearch.google.com.uy/ping/RPC2 http://blogsearch.google.com.vn/ping/RPC2 http://blogsearch.google.co.nz/ping/RPC2 http://blogsearch.google.co.th/ping/RPC2 http://blogsearch.google.co.uk/ping/RPC2 http://blogsearch.google.co.ve/ping/RPC2 http://blogsearch.google.co.za/ping/RPC2 http://blogsearch.google.de/ping/RPC2 http://blogsearch.google.es/ping/RPC2 http://blogsearch.google.fi/ping/RPC2 http://blogsearch.google.fr/ping/RPC2 http://blogsearch.google.gr/ping/RPC2 http://blogsearch.google.hr/ping/RPC2 http://blogsearch.google.ie/ping/RPC2 http://blogsearch.google.it/ping/RPC2 http://blogsearch.google.jp/ping/RPC2 http://blogsearch.google.ki/ping/RPC2 http://blogsearch.google.kz/ping/RPC2 http://blogsearch.google.la/ping/RPC2 http://blogsearch.google.li/ping/RPC2 http://blogsearch.google.lk/ping/RPC2 http://blogsearch.google.lt/ping/RPC2 http://blogsearch.google.lu/ping/RPC2 http://blogsearch.google.md/ping/RPC2 http://blogsearch.google.mn/ping/RPC2 http://blogsearch.google.ms/ping/RPC2 http://blogsearch.google.mu/ping/RPC2 http://blogsearch.google.mv/ping/RPC2 http://blogsearch.google.mw/ping/RPC2 http://blogsearch.google.nl/ping/RPC2 http://blogsearch.google.no/ping/RPC2 http://blogsearch.google.nr/ping/RPC2 http://blogsearch.google.nu/ping/RPC2 http://blogsearch.google.pl/ping/RPC2 http://blogsearch.google.pn/ping/RPC2 http://blogsearch.google.pt/ping/RPC2 http://blogsearch.google.ro/ping/RPC2 http://blogsearch.google.ru/ping/RPC2 http://blogsearch.google.rw/ping/RPC2 http://blogsearch.google.sc/ping/RPC2 http://blogsearch.google.se/ping/RPC2 http://blogsearch.google.sh/ping/RPC2 http://blogsearch.google.si/ping/RPC2 http://blogsearch.google.sk/ping/RPC2 http://blogsearch.google.sm/ping/RPC2 http://blogsearch.google.sn/ping/RPC2 http://blogsearch.google.st/ping/RPC2 http://blogsearch.google.tk/ping/RPC2 http://blogsearch.google.tl/ping/RPC2 http://blogsearch.google.tm/ping/RPC2 http://blogsearch.google.to/ping/RPC2 http://blogsearch.google.tp/ping/RPC2 http://blogsearch.google.tt/ping/RPC2 http://blogsearch.google.us/ping/RPC2 http://blogsearch.google.vg/ping/RPC2 http://blogsearch.google.vu/ping/RPC2 http://blogsearch.google.ws/ping/RPC2 http://blo.gs/ping.php http://blogs.yandex.ru/ http://blog.with2.net/ping.php http://bulkfeeds.net/rpc http://coreblog.org/ping/ http://geourl.org/ping http://ipings.com http://mod-pubsub.org/kn_apps/blogchatt http://news2paper.com/ping http://ping.bitacoras.com http://ping.bloggers.jp/rpc http://ping.blo.gs/ http://ping.blogs.yandex.ru/RPC2 http://ping.exblog.jp/xmlrpc http://ping.fc2.com http://ping.feedburner.com http://ping.myblog.jp http://pingoat.com/goat/RPC2 http://ping.rootblog.com/rpc.php http://ping.rss.drecom.jp http://ping.syndic8.com/xmlrpc.php http://ping.weblogs.se/ http://rcs.datashed.net/RPC2/ http://rpc.blogbuzzmachine.com/RPC2 http://rpc.bloggerei.de/ http://rpc.bloggerei.de/ping/ http://rpc.blogrolling.com/pinger/ http://rpc.icerocket.com:10080 http://rpc.newsgator.com/ http://rpc.pingomatic.com http://rpc.technorati.com/rpc/ping http://rpc.twingly.com http://rpc.urlfan.com/ping http://rpc.weblogs.com/RPC2 http://services.newsgator.com/ngws/xmlrpcping.aspx https://ping.blogs.yandex.ru/RPC2 http://topicexchange.com/RPC2 http://trackback.bakeinu.jp/bakeping.php http://www.a2b.cc/setloc/bp.a2b http://www.bitacoles.net/ping.php http://www.blogdigger.com/RPC2 http://www.blogoole.com/ping/ http://www.blogpeople.net/servlet/weblogUpdates http://www.blogroots.com/tb_populi.blog?id=1 http://www.blogshares.com/rpc.php http://www.blogsnow.com/ping http://www.blogstreet.com/xrbin/xmlrpc.cgi http://www.lasermemory.com/lsrpc/ http://www.mod-pubsub.org/kn_apps/blogchatter/ping.php http://www.pingerati.net http://www.pingmyblog.com
Fail2WP for WordPress 1.1.0 has been released with fixes, new functionality, and verified compatibility with WordPress 5.7. The updated version is available via the WordPress Plugin repository and code.webbplatsen.net
Fail2WP provides security functionality for WordPress sites and plays nicely with Fail2ban and Cloudflare too 🙂
Fail2WP for WordPress 1.0.0 has been released and is available via the WordPress Plugin repository and code.webbplatsen.net
Fail2WP provides security functionality for WordPress sites and plays nicely with Fail2ban and Cloudflare too!
Cloudbridge Mattermost is a WordPress plugin that provides integration between WordPress and Mattermost.
It has now been updated with OAuth2 authentication for WordPress via Mattermost.
It has been tested with Mattermost 5.30+ and WordPress 5.5.3 and WordPress 5.6.
Features at a glance:
You can download it from the official WordPress repository:
wordpress.org/plugins/cloudbridge-mattermost
You can also get it from GitHub, should you prefer that source:
github.com/joho1968/cloudbridge-mattermost
WebbPlatsen’s official website for their Open Source projects:
code.webbplatsen.net/wordpress/cloudbridge-mattermost/