

So, all in all, it’s still not very helpful and does absolutely nothing to address the “ future developers to face an unnecessary hurdle ” issue in the WordPress guidelines. I also agree with that the source files on the repo bear little resemblance to the compiled files. So that does appear to show that RM hasn’t always been helpful. Just as aside, I did come across this in the many fruitless times I’ve searched on Google for a Rank Math repo:

Their GitHub repo was only created on or around 11 June 2020, probably to coincide with the release of v1.0.44 (although there’s no mention of this in the release notes). It’s taken RM a long time to embrace the open source philosophy and I’m still not sure they have even now. Having said that, I do believe RM could have been more helpful. I was grateful to be able to use RM as a base for Classic SEO and RM certainly seemed to be the preferred option among the ClassicPress community. Just want to start off by saying it is not my aim to antagonize Rank Math. I would appreciate if this matter could be investigated and hopefully resolved so that future tags contain human-readable JavaScript files. This makes it impossible to verify the plugin’s lack of malicious intent, and prevents other developers from investigating bugs or developing integrations. However, all the JavaScript files in the “assets/admin/js” folder of Rank Math plugin are obfuscated. Guideline 4 states (paraphrasing) that code must not be deliberately obfuscated. I need to inform you that the plugin “WordPress SEO Plugin - Rank Math” (URL below) violates at least one of the repository guidelines.

So I decided to email the main WordPress plugins email address as follows: This is arguably the most effective method for preventing spam, while still allowing mailto: links. This plugin provides an easy-to-use ROT13 substitution cipher WordPress shortcode for mailto: links. Making code non-human readable forces future developers to face an unnecessary hurdle, as well as being a common vector for hidden, malicious code. Welcome to the ROT13 Email Obfuscator plugin repository on GitHub. Obscuring code by hiding it with techniques or systems similar to p,a,c,k,e,r ‘s obfuscate feature, uglify’s mangle, or unclear naming conventions such as $z12sdf813d, is not permitted in the directory. It’s particularly frustrating for ACF users because there’s a bug which interferes with the SEO scoring mechanism for custom fields.īecause Rank Math is in the WP repository, it has to abide by the repository’s guidelines, and I’ve found that guideline 4 states the following: Some of us (particularly are aware that the Classic SEO plugin inherited a load of obfuscated JavaScript files when it was forked from Rank Math, and the authors of Rank Math have declined to assist in any way.
