[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fbQBn4vC05mPDY1422KoJw-X0IO27Z3yGfLFI7AQmgMc":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"apunker","https:\u002F\u002Fprofiles.wordpress.org\u002Fapunker\u002F",2,10,93,30,89,"2026-08-28T18:29:00.796Z",[13,34],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":20,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":24,"download_link":30,"security_score":31,"vuln_count":20,"unpatched_count":20,"last_vuln_date":32,"fetched_at":33},"openmeetings-integration-plugin-widget","Openmeetings widget","0.1","\u003Cp>Openmeetings WordPress integration widget.\u003Cbr \u002F>\nOpenMeetings is a free browser-based software that allows you to set up instantly a conference in the Web. You can use your microphone or webcam, share documents on a white board, share your screen or record meetings. It is available as hosted service or you download and install a package on your server with no limitations in usage or users.\u003C\u002Fp>\n\u003Cp>Please visit us for more information and updates at:\u003C\u002Fp>\n\u003Cp>http:\u002F\u002Fwww.eyecatchers.co.il\u002Fopenmeetings-widget-wordpress-plugin\u002F\u003Cbr \u002F>\nOpenmeetings hosting at: http:\u002F\u002Fwww.linux-hosting.co.il\u002F\u003C\u002Fp>\n\u003Cp>Openmeetings has now been released more advanced plugin for WordPress for a few dollars. I suggest you go grab a copy at:\u003Cbr \u002F>\nhttp:\u002F\u002Fcode.google.com\u002Fp\u002Fopenmeetings\u002Fwiki\u002FWordpressIntegration\u003C\u002Fp>\n\u003Ch3>Arbitrary section\u003C\u002Fh3>\n\u003Cp>Nothing here.\u003C\u002Fp>\n\u003Ch3>A brief Markdown Example\u003C\u002Fh3>\n\u003Cp>TODO list:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Improvements.\u003C\u002Fli>\n\u003C\u002Ful>\n","This is an attampt to make an Openmeetings Wordpress integration widget. OpenMeetings is a free browser-based software that allows you to set up insta …",5307,0,"2011-08-04T15:25:00.000Z","3.1.4","3","",[26,27,28,29],"conference","conferencing","openmeetings","video","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fopenmeetings-integration-plugin-widget.zip",85,null,"2026-04-16T10:56:18.058Z",{"slug":35,"name":36,"version":37,"author":4,"author_profile":5,"description":38,"short_description":39,"active_installs":20,"downloaded":40,"rating":20,"num_ratings":20,"last_updated":41,"tested_up_to":42,"requires_at_least":43,"requires_php":44,"tags":45,"homepage":51,"download_link":52,"security_score":53,"vuln_count":20,"unpatched_count":20,"last_vuln_date":32,"fetched_at":54},"jabali-cache","Jabali Cache","1.1.0","\u003Cp>\u003Cstrong>Jabali Cache makes WordPress fast by keeping its object cache in Redis instead of rebuilding it on every request.\u003C\u002Fstrong> WordPress normally throws away its internal cache at the end of each request, so the same expensive database queries run again and again. This plugin makes that cache persistent — backed by the Redis instance the \u003Ca href=\"https:\u002F\u002Fjabali-panel.com\" rel=\"nofollow ugc\">Jabali hosting panel\u003C\u002Fa> already runs — so pages assemble from memory instead of hammering MySQL.\u003C\u002Fp>\n\u003Cp>It is purpose-built for shared hosting, where many sites share one Redis server. That shapes every design decision: strict per-site isolation, safe behaviour under memory pressure, and a hard rule that a caching layer must \u003Cem>never\u003C\u002Fem> take a site down.\u003C\u002Fp>\n\u003Ch4>Why you might want it\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Fewer database queries, faster pages.\u003C\u002Fstrong> Options, post meta, terms, user data and transients come from Redis on repeat requests instead of MySQL.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lighter database load.\u003C\u002Fstrong> Especially noticeable on WooCommerce, membership, and query-heavy sites under traffic.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Drop-in.\u003C\u002Fstrong> Activate it and WordPress’s standard object-cache API (\u003Ccode>wp_cache_*\u003C\u002Fcode>, transients) starts using Redis. No theme or plugin changes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Built for the way Jabali hosts sites\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Zero-config on Jabali.\u003C\u002Fstrong> Connects to the panel Redis over the unix socket \u003Ccode>\u002Frun\u002Fredis\u002Fredis.sock\u003C\u002Fcode>, logical database 1. Nothing to type — no host, port, or password.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Strict per-site isolation.\u003C\u002Fstrong> Every install gets its own key prefix. Sites share one Redis database but can never read or flush each other’s cache. A site’s flush only clears that site’s keys.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No phpredis required.\u003C\u002Fstrong> If the \u003Ccode>redis\u003C\u002Fcode> PHP extension is present it is used automatically; if not (the Jabali default), the plugin falls back to a dependency-free, pure-PHP RESP client over the same socket. Either way it just works.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Safe under memory pressure.\u003C\u002Fstrong> The panel Redis runs an \u003Ccode>allkeys-lru\u003C\u002Fcode> policy, so it may evict keys at any time. Every read is best-effort — an evicted or missing key simply falls through to the database. An eviction is never an error.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Fails safe, always.\u003C\u002Fstrong> If Redis is unreachable for any reason, WordPress keeps running with its normal per-request cache. Nothing breaks; caching just stops accelerating until the connection is back. The admin screen tells you exactly what is wrong and how to fix it.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Multisite-aware.\u003C\u002Fstrong> On a network, per-blog data is namespaced per site while genuinely global groups (network, site meta) are shared correctly.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Object cache vs. page cache\u003C\u002Fh4>\n\u003Cp>The persistent \u003Cstrong>object cache\u003C\u002Fstrong> is the main event and is on as soon as you activate the plugin.\u003C\u002Fp>\n\u003Cp>A full \u003Cstrong>page cache\u003C\u002Fstrong> is also included, but it is \u003Cstrong>off by default\u003C\u002Fstrong>. Jabali already serves a faster page cache at the edge via nginx (FastCGI microcache), so turning on the WordPress page cache as well would just cache the same HTML twice. Enable the in-WordPress page cache only on hosts where the nginx one is not available.\u003C\u002Fp>\n\u003Ch4>Privacy\u003C\u002Fh4>\n\u003Cp>Jabali Cache stores WordPress’s own cache data in your Redis server and nowhere else. It does not collect analytics, contact any external service, or send data off your server.\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>Development happens on GitHub. Found a bug, or have a feature request? Please open an issue:\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fshukiv\u002Fjabali-panel\u002Fissues\" rel=\"nofollow ugc\">https:\u002F\u002Fgithub.com\u002Fshukiv\u002Fjabali-panel\u002Fissues\u003C\u002Fa>\u003C\u002Fp>\n","Persistent Redis object cache for WordPress. Zero-config on the Jabali panel, works without the phpredis extension, and always fails safe.",275,"2026-07-20T19:32:00.000Z","7.0.2","5.6","7.4",[46,47,48,49,50],"cache","object-cache","page-cache","performance","redis","https:\u002F\u002Fjabali-panel.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjabali-cache.1.1.0.zip",100,"2026-07-22T17:31:50.256Z"]