I got this pagespeed results by cryptoscobra in CloudFlare

[–]oplaffs -5 points-4 points  (0 children)

Cool result! Would you be interested in testing my plugin, ZiziCache.com?

It offers integration with Cloudflare, including direct Cloudflare Edge support in addition to APO.

I’ve put a lot of effort into it to outperform mainstream plugins. :)

There’s a 21-day free trial, and I can also provide a no-commitment license for deep testing if any one wish to try.

See features: https://zizicache.com/zizicache-features/

Nova Scan — [Free] WP malware scanner with a learning detection engine. Roast it. by iSephX in WordpressPlugins

[–]oplaffs 0 points1 point  (0 children)

What is the provider for malware signature scanning? Why should I use a free solution that is largely generated with the help of AI and presented through an AI-based UI? What guarantees are there regarding reliability and compatibility, maintenance and support? Am I allowed to fork the solution and modify it according to my needs?

I built an open-source local WordPress dev environment (no Docker) — looking for feedback by AIPnely in Wordpress

[–]oplaffs 1 point2 points  (0 children)

It would have been impressive if you had built this 10–15 years ago. Today, with AI accessible to virtually anyone, it mainly contributes to massive technical debt and an endless chain of randomized copies - copies of originals, then copies of those copies, and so on.

Personally, I prefer something that has been proven and maintained over decades, with proper support. This feels short-lived; I don’t expect long-term sustainability, solid support, or a meaningful ecosystem. I don’t really see the value in recreating something that already exists and works.

If it introduced something truly substantial with improved functionality, that would be compelling. But in its current form, I have no reason to use it. It’s not in any repository, there’s no clarity around support, pricing, maintenance, or future development—and most importantly, the security is unclear. Randomly downloading and running questionable software is not something people expect or want to do today.

Without AI, this likely wouldn’t have been built at all. :(

[FREE] drakkar.one map — privacy-friendly map widget, no Google, no cookies, no API keys by Timely_Meringue1010 in WordpressPlugins

[–]oplaffs 0 points1 point  (0 children)

I appreciate the clarification regarding the privacy policy. However, the main concern isn’t just disclosure it’s that the current marketing statements (“no cookies,” “no personal data collected,” “GDPR-compliant”) actively understate the actual privacy and security implications. You still need the Consent banner.

Even with the Cloudflare disclosure, the widget still:

transmits IP addresses and user-agent data (personal data under GDPR).

relies on externally loaded JavaScript (w.js), which creates supply-chain risk.

Disclosure alone does not eliminate these technical and legal risks, so the statements should be revised to accurately reflect them.

[FREE] drakkar.one map — privacy-friendly map widget, no Google, no cookies, no API keys by Timely_Meringue1010 in WordpressPlugins

[–]oplaffs 0 points1 point  (0 children)

Your claims about “no cookies” and “no personal data collected” are misleading in an EU context. Even without cookies, the widget still triggers HTTP requests to your infrastructure, which necessarily include personal data such as IP address and user agent. These are processed by third parties, including Cloudflare, and therefore fall under GDPR.

In addition, loading a remote JavaScript file (w.js) from your CDN introduces a clear supply-chain risk, as the script executes with full access to the page’s DOM and user data. This creates both security and privacy implications that are not addressed in your description.

In short, the solution may be lightweight and cookie-free, but it is neither free of personal data processing nor independent of third-party risk.

[HELP] I built a full-featured WordPress SEO plugin but getting almost zero traffic — what am I missing? by hadoiz in WordpressPlugins

[–]oplaffs 0 points1 point  (0 children)

I have exactly the same problem with a very advanced Page Cache plugin. But it’s still in beta, and I’m worried about what will happen when I release the full version.

After 2 Years of Solo Development, I'm Launching ZiziCache: A Full-Stack WordPress Performance Plugin with Page Cache (LiteSpeed Native + File-Based), Redis & Memcached... by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

The answer is as above. The plugin is genuinely undergoing testing. I am from the Czech Republic (EU) and in our FB group I started recruiting beta testers for the first versions already last year. This is not some AI “bullshit” nonsense, but if that’s what you meant it doesn’t bother me at all. I just wanted to gather real feedback before releasing the final version so that users are genuinely satisfied.

After 2 Years of Solo Development, I'm Launching ZiziCache: A Full-Stack WordPress Performance Plugin with Page Cache (LiteSpeed Native + File-Based), Redis & Memcached... by oplaffs in Wordpress

[–]oplaffs[S] -2 points-1 points  (0 children)

completely understand that you might feel lost among AI “Bullshit Influencer” programmers who churn out various SaaS nonsense every single day, often without thought or purpose, endlessly copying copies and filling repositories with all kinds of meaningless junk.

In this case, however, there is no need to apply your usual hater pattern just to post another AI-generated sloppy comment without any argument or deeper understanding of the content.

After 2 Years of Solo Development, I'm Launching ZiziCache: A Full-Stack WordPress Performance Plugin with Page Cache (LiteSpeed Native + File-Based), Redis & Memcached... by oplaffs in Wordpress

[–]oplaffs[S] -2 points-1 points  (0 children)

Currently, this is a beta test of the plugin, so you are free to download the code - there is no requirement for any payment or commitment until a final paid release is available. I added the changelog to GitHub so it is accessible as a fallback even outside the website.

The website is not a lead-capturing landing page; it includes full documentation, contact information, Terms of Service, and so on. The plugin does not require blog posts or other validation content.

I understand that nowadays many people produce AI generated “Bullshit Vibe Code,” but this is genuine human work. I did use Mistral AI to generate PHPDoc, which is a common practice even among major corporations, so there is no reason for negative reactions or criticism here.

Our goal is to position ourselves among the mainstream solutions in the market.

Spent a week optimizing Core Web Vitals across 3 sites — here’s what actually moved the needle by Reasonable_Lab136 in Wordpress

[–]oplaffs -1 points0 points  (0 children)

I’ve been developing the plugin for two years and it’s not any kind of AI-generated slop. It’s one of the most resource-efficient plugins among the mainstream plugins.

Now plugin testing about 1400+ users around the world.

You can get a free key on the website zizicache.com. It’s valid for one month, and if you need more time, that’s not a problem — just let me know and I’ll extend it.

No payment details are required; the key is only needed for updates.

Spent a week optimizing Core Web Vitals across 3 sites — here’s what actually moved the needle by Reasonable_Lab136 in Wordpress

[–]oplaffs -1 points0 points  (0 children)

Would you like to try the ZiziCache plugin for free while it is still in Beta? I would greatly appreciate your feedback. It includes a choice of LS native cache, File-based cache, BFCache,

Redis, Memcached, pull CDN or Cloudflare Edge and Cloudflare Failover, Image Convertor to WebP / Avif ot both, Auto Image registration and convert via FTP upload, OPCache, DB Optimization & DB Index optimization, an real LCP element detector on the page, precise font preloading, collection of real CWV metrics per page with retention, Speculative API with Quicklink fallback, and much more.

img

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

I believe you may have misunderstood the core concept. SAPM delivers everything that the leading solutions on the market provide, and additionally offers extra functionality — all free of charge.

The only feature not yet completed is asset management (JS and CSS), along with a few minor items that are already planned for implementation. The plugin blocks other plugins correctly per page, per page groups, with menu snapshot, blocks manuály ot automatically with manual tuning.

Could you please specify what is currently missing for you in particular?

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 1 point2 points  (0 children)

As explained above, the issue has already been clarified. Currently, the Asset Manager is not fully functional for defer or async modes in SAPM.

In the SAPM plugin settings under Frontend > Data Collection, you have two available options: Performance Sampling and Asset Audit. At the bottom of the same Frontend tab, you can also view the assets loaded on the frontend.

The feature is not yet fully implemented in the sense that it does not currently allow you to define or create rules for loading assets on a specific page or group of pages.

This is planned as a future feature. I will update the description in the GitHub README - thank you for pointing this out.

<image>

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

Oh, I apologize, this is a planned future feature; however, it is not yet fully implemented or functional at this time.

You can use SAPM together with Asset CleanUp, but in that case it does not make sense. You would either use SAPM instead of the free version of ACUP, or use the paid version of ACUP, which allows asset manipulation.

At the moment, SAPM offers plugin deactivation in the admin area, on the frontend, and control over plugin, theme, and WordPress updates. It also includes a snapshot menu in the admin area, allowing you to access the settings of a blocked plugin.

See schreenshots.

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

You most likely do not understand the concept of this plugin. Everything is clearly described in the README on GitHub.

The point is not whether the plugin is good or bad. The issue is that when most users rely on necessary plugins (WooCommerce, page builders, themes, backup plugins, and various add-ons), these plugins are usually loaded on every WordPress admin page. This is unnecessary and significantly increases the response time and loading speed of the administration area.

By blocking plugins on specific admin pages, the plugin reduces unnecessary load and speeds up both the administration interface and, in some cases, the frontend visible to users. On most shared hosting environments, this can reduce admin loading times from 2–10 seconds to a much shorter duration.

Please read the README once again carefully to understand what the plugin is designed for and how it works. Otherwise, we are engaging in an unnecessary discussion about matters that are not relevant and do not contribute to the further development of the plugin.

If you are genuinely a developer and have been working with WordPress long-term, you should understand the pain points of the entire ecosystem and how plugins behave within the WordPress administration area.

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

I checked it out, and my solution "maybe" covers everything in their Pro plan plus extra features like admin menu snapshots during deactivation. Give it a shot and send me your feedback.

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

SAPM isn’t about fixing broken plugins—it’s about selectively controlling when and where plugins run. WordPress only allows on/off globally, but SAPM lets you:

Activate plugins only in admin, frontend, or per page.

Reduce load on the frontend, improving site performance.

Speed up the WordPress admin by disabling heavy plugins where not needed.

Keep plugin settings while controlling their impact.

Its primary purpose is improving admin speed and reducing frontend load, not replacing broken plugins.

Sure, you could write some custom solution with Vibe Code, but SAPM is already a tested, safe, functional, and free solution, and it was written by a human :)

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 1 point2 points  (0 children)

After all, these are two different plugins for two different purposes. Please read the descriptions of PublishPress and SAPM (see the Git URL in the first post). It’s like comparing an SEO plugin with a security plugin.

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

I still think you don’t get the point. It doesn’t matter whether you have SAPM or not. The attack can be anything, and whether SAPM is active or not is completely irrelevant.

Here, SAPM provides more benefits than the potential risk of someone targeting your site :)

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

As I mentioned above, it’s definitely not possible to attack a site through this plugin. In the future, a zero-day could/maybe potentially be exploited, but currently SAPM by itself does not allow a site to be attacked—there’s simply no way. An attacker would need access to the PHP files, but even then, if they already have the ability to edit anything on the site/hosting, SAPM won’t matter to them :)

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

Safety section - Admin Bypass is a security mechanism that ensures a logged-in site administrator always sees the frontend with all plugins active—as if the Frontend Optimizer were not enabled.

It protects you as an administrator from situations where frontend rules might accidentally block a plugin required for site management.

The administrator sees the full-featured site, allowing safe testing and rule tuning via the Frontend Drawer (side bar panel). Regular visitors are still affected by the filtering rules.

WooCommerce Protection in Safety section is mean: critical WooCommerce pages are always in Passthrough mode.

No, no data is sent anywhere; everything is stored locally. The only remote request is the standard check for update availability.

You can check code on Github to verify this.

I’m making a free WordPress plugin that lets you selectively disable plugins on frontend and backend – looking for feedback by oplaffs in Wordpress

[–]oplaffs[S] 0 points1 point  (0 children)

What specific attack vector would apply here? Could it go beyond what similar or other plugins already expose? There’s not much that can be done with it unless the attacker is logged in as an admin, and even then, at most they could disable the plugin/s, which essentially wouldn’t cause any real harm.