[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f6iBiUvstjRk7FmKFWJb5xfGtM3flcEqzYdAWV6Zov4U":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"goblindegook","Luis Rodrigues","https:\u002F\u002Fprofiles.wordpress.org\u002Fgoblindegook\u002F",3,70,85,30,84,"2026-04-04T15:13:41.249Z",[14,35,52],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":10,"downloaded":20,"rating":21,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":30,"download_link":31,"security_score":9,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"post-glue","Post Glue","1.0.0","\u003Cp>Sticky posts for WordPress, improved.\u003C\u002Fp>\n\u003Cp>This plugin addresses the following issues and limitations found in the core’s implementation of sticky posts:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Only the core \u003Ccode>post\u003C\u002Fcode> type supports this feature.\u003C\u002Fli>\n\u003Cli>Sticky posts are added in front of your homepage’s results, yielding more posts than the configured per-page setting.\u003C\u002Fli>\n\u003Cli>Sticky posts reappear as you navigate further into the archive.\u003C\u002Fli>\n\u003Cli>Sticky posts are prepended to your results when querying specific posts with \u003Ccode>post__in\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Difficult to include sticky posts in custom queries.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Some of these issues cause strange behaviour (like when using the REST API) and complicate the creation of custom homepage layouts.\u003C\u002Fp>\n\u003Cp>At one point we decided to stop fighting the core and partially reimplemented the feature using custom post fields and meta queries, giving you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Sticky posts for all non-hierarchical post types.\u003C\u002Fli>\n\u003Cli>Post stickiness on post type and taxonomy archives.\u003C\u002Fli>\n\u003Cli>Respect for your configured per-page setting, with stickies spilling over onto the next page.\u003C\u002Fli>\n\u003Cli>Duplicates filtered from your archive pages.\u003C\u002Fli>\n\u003Cli>The ability to sort by stickiness on virtually any \u003Ccode>WP_Query\u003C\u002Fcode> lookup.\u003C\u002Fli>\n\u003Cli>Support for the \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Ffunctions\u002Fis_sticky\u002F\" rel=\"nofollow ugc\">\u003Ccode>is_sticky()\u003C\u002Fcode>\u003C\u002Fa> function.\u003C\u002Fli>\n\u003Cli>A predictable WordPress REST API experience.\u003C\u002Fli>\n\u003Cli>A slight SQL query overhead (sorry!)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Post Glue will continue to save post IDs to the \u003Ccode>sticky_posts\u003C\u002Fcode> option, meaning you’ll retain some core functionality even if you decide to stop using the plugin.\u003C\u002Fp>\n\u003Cp>Please follow and contribute to Post Glue’s development on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flog-oscon\u002Fpost-glue\" rel=\"nofollow ugc\">Github\u003C\u002Fa>.\u003C\u002Fp>\n","Sticky posts for WordPress, improved.",2170,100,2,"2016-02-16T00:47:00.000Z","4.4.34","4.4","",[28,29],"stickiness","sticky-posts","https:\u002F\u002Fgithub.com\u002Flog-oscon\u002Fpost-glue\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpost-glue.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":36,"name":37,"version":38,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":10,"downloaded":41,"rating":21,"num_ratings":22,"last_updated":42,"tested_up_to":24,"requires_at_least":43,"requires_php":26,"tags":44,"homepage":50,"download_link":51,"security_score":9,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"wp-cas-server","Cassava CAS Server","1.2.3","\u003Cp>Cassava allows WordPress to act as a single sign-on authenticator using the Central Authentication Service (CAS) protocol.\u003C\u002Fp>\n\u003Cp>That way, users on your WordPress install may be able to access different applications that support the CAS protocol by providing a single set of credentials and without exposing the user’s password.\u003C\u002Fp>\n\u003Cp>By default, CAS method URIs are provided under the \u003Ccode>wp-cas\u003C\u002Fcode> endpoint:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002Flogin\u003C\u002Fcode>: Allows a remote service to request that a user authenticate on the CAS server. Will redirect back to the remote service along with a service ticket.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002Flogout\u003C\u002Fcode>: Terminates the single sign-on session. May optionally redirect the user back to the remote service.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002Fvalidate\u003C\u002Fcode> [CAS 1.0]: Allows a remote service to validate a service ticket forwarded by the user on redirect. Returns a plaintext response.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002Fproxy\u003C\u002Fcode> [CAS 2.0]: Provides access to remote services with proxy tickets in exchange for proxy-granting tickets. Returns an XML response.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002FproxyValidate\u003C\u002Fcode> [CAS 2.0]: Allows a remote service to validate a service or proxy ticket forwarded by the user on redirect. Returns an XML response.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002FserviceValidate\u003C\u002Fcode> [CAS 2.0]: Allows a remote service to validate a service ticket forwarded by the user on redirect. Returns an XML response.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002Fp3\u002FproxyValidate\u003C\u002Fcode> [CAS 3.0]: Allows a remote service to validate a service or proxy ticket forwarded by the user on redirect. Returns an XML response.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fwp-cas\u002Fp3\u002FserviceValidate\u003C\u002Fcode> [CAS 3.0]: Allows a remote service to validate a service ticket forwarded by the user on redirect. Returns an XML response.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>There are a few \u003Ca href=\"http:\u002F\u002Fwww.jasig.org\u002Fcas\u002Fclient-integration\" rel=\"nofollow ugc\">client integration\u003C\u002Fa> libraries available for CAS, as well as a handy guide for \u003Ca href=\"https:\u002F\u002Fwiki.jasig.org\u002Fdisplay\u002FCASC\u002FCASifying+Applications\" rel=\"nofollow ugc\">CASifying several existing applications\u003C\u002Fa>. Independent WordPress installations may integrate with Cassava using a client plugin such as \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcas-maestro\u002F\" rel=\"ugc\">CAS Maestro\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Please follow and contribute to Cassava’s development on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fgoblindegook\u002Fwp-cas-server\" rel=\"nofollow ugc\">Github\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Hooks\u003C\u002Fh3>\n\u003Ch4>Action: cas_server_before_request\u003C\u002Fh4>\n\u003Cp>Fires before a CAS request is processed.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$path\u003C\u002Fcode>: Requested URI path.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Action: cas_server_after_request\u003C\u002Fh4>\n\u003Cp>Fires after a CAS request is processed.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$path\u003C\u002Fcode>: Requested URI path.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Action: cas_server_error\u003C\u002Fh4>\n\u003Cp>Fires if the CAS server has to return an XML error.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>WP_Error\u003C\u002Fem> \u003Ccode>$error\u003C\u002Fcode>: WordPress error to return as XML.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Action: cas_server_validation_success\u003C\u002Fh4>\n\u003Cp>Fires on successful ticket validation.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>WP_User\u003C\u002Fem> \u003Ccode>$user\u003C\u002Fcode>: WordPress user validated by ticket.\u003C\u002Fli>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$ticket\u003C\u002Fcode>: Valid ticket string.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_enabled\u003C\u002Fh4>\n\u003Cp>Allows developers to disable CAS.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>boolean\u003C\u002Fem> \u003Ccode>$cas_enabled\u003C\u002Fcode>: Whether the server should respond to single sign-on requests.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_routes\u003C\u002Fh4>\n\u003Cp>Allows developers to override the default controller mapping, define additional endpoints and provide alternative implementations to the provided controllers.\u003C\u002Fp>\n\u003Cp>Controllers provided in this fashion should extend the \u003Ccode>\\Cassava\\CAS\\Controller\\BaseController\u003C\u002Fcode> class.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>array\u003C\u002Fem> \u003Ccode>$cas_routes\u003C\u002Fcode>: CAS endpoint to controller mapping.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_response\u003C\u002Fh4>\n\u003Cp>Lets developers change the CAS server response string.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$output\u003C\u002Fcode>: Response output string.\u003C\u002Fli>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$path\u003C\u002Fcode>: Requested URI path.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_dispatch_args\u003C\u002Fh4>\n\u003Cp>Filters the callback arguments to be dispatched for the request. Plugin developers may return a \u003Ccode>WP_Error\u003C\u002Fcode> object here to abort the request.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>array\u003C\u002Fem> \u003Ccode>$args\u003C\u002Fcode>: Arguments to pass the callback.\u003C\u002Fli>\n\u003Cli>\u003Cem>(string|array)\u003C\u002Fem> \u003Ccode>$callback\u003C\u002Fcode>: Callback function or method.\u003C\u002Fli>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$path\u003C\u002Fcode>: Requested URI path.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_login_args\u003C\u002Fh4>\n\u003Cp>Allows developers to change the request parameters passed to a \u003Ccode>\u002Flogin\u003C\u002Fcode> request.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>array\u003C\u002Fem> \u003Ccode>$args\u003C\u002Fcode>: HTTP request (GET, POST) parameters.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_redirect_service\u003C\u002Fh4>\n\u003Cp>Filters the redirect URI for the service requesting user authentication.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$service\u003C\u002Fcode>: Service URI requesting user authentication.\u003C\u002Fli>\n\u003Cli>\u003Cem>WP_User\u003C\u002Fem> \u003Ccode>$user\u003C\u002Fcode>: Logged in WordPress user.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_custom_auth_uri\u003C\u002Fh4>\n\u003Cp>Allows developers to redirect the user to a custom login form.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$custom_login_url\u003C\u002Fcode>: URI for the custom login page.\u003C\u002Fli>\n\u003Cli>\u003Cem>array\u003C\u002Fem> \u003Ccode>$args\u003C\u002Fcode>: Login request parameters.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_ticket_expiration\u003C\u002Fh4>\n\u003Cp>This filter allows developers to override the default ticket expiration period.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>int\u003C\u002Fem> \u003Ccode>$expiration\u003C\u002Fcode>: Ticket expiration period (in seconds).\u003C\u002Fli>\n\u003Cli>\u003Cem>string\u003C\u002Fem> \u003Ccode>$type\u003C\u002Fcode>: Type of ticket to set.\u003C\u002Fli>\n\u003Cli>\u003Cem>WP_User\u003C\u002Fem> \u003Ccode>$user\u003C\u002Fcode>: Authenticated user associated with the ticket.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_validation_user_attributes\u003C\u002Fh4>\n\u003Cp>Allows developers to change the list of (key, value) pairs before they’re included in a \u003Ccode>\u002FserviceValidate\u003C\u002Fcode> response.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>array\u003C\u002Fem> \u003Ccode>$attributes\u003C\u002Fcode>: List of attributes to output.\u003C\u002Fli>\n\u003Cli>\u003Cem>WP_User\u003C\u002Fem> \u003Ccode>$user\u003C\u002Fcode>: Authenticated user.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Filter: cas_server_settings_user_attribute_options\u003C\u002Fh4>\n\u003Cp>Allows developers to change the list of user attributes that appear in the dashboard for an administrator to set to return on successful validation requests.\u003C\u002Fp>\n\u003Cp>Options are stored in an associative array, with user attribute slugs as array keys and option labels as array values.\u003C\u002Fp>\n\u003Cp>These settings are valid only for CAS 2.0 validation requests.\u003C\u002Fp>\n\u003Cp>Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>array\u003C\u002Fem> \u003Ccode>$attributeOptions\u003C\u002Fcode> Attribute options an administrator can set on the dashboard.\u003C\u002Fli>\n\u003C\u002Ful>\n","Cassava provides authentication services based on the Jasig CAS protocol.",3163,"2016-02-13T00:05:00.000Z","3.9",[45,46,47,48,49],"authentication","cas","central-authentication-service","jasig-cas","single-sign-on","https:\u002F\u002Fgoblindegook.github.io\u002Fwp-cas-server","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-cas-server.1.2.3.zip",{"slug":53,"name":54,"version":55,"author":5,"author_profile":6,"description":56,"short_description":57,"active_installs":58,"downloaded":59,"rating":21,"num_ratings":60,"last_updated":61,"tested_up_to":24,"requires_at_least":62,"requires_php":26,"tags":63,"homepage":26,"download_link":69,"security_score":9,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"network-restricted-members","Network Restricted Members","0.3.1","\u003Cp>If you have a private network where all sites are open to anyone with an account, but still want the ability to invite someone from outside and limit their access to a single site, then Network Restricted Members is for you.\u003C\u002Fp>\n\u003Cp>This plugin was developed for our private \u003Ca href=\"http:\u002F\u002Fp2theme.com\" rel=\"nofollow ugc\">P2\u003C\u002Fa> network, which is open to all company employees. However, we still wanted to be able to bring contractors and clients over without giving them access to everything on the network.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Network Restricted Members provides a user setting that allows multisite network administrators to restrict a user to the sites he or she is a member of.\u003C\u002Fp>\n\u003Col>\n\u003Cli>As a super admin, navigate to the Users dashboard\u003C\u002Fli>\n\u003Cli>Click ‘Edit’ on the user you wish to restrict\u003C\u002Fli>\n\u003Cli>Check the option ‘Restrict User Access’\u003C\u002Fli>\n\u003Cli>Save your changes\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>From this point on, administrators will need to add this user to their sites before he or she is able to see them.\u003C\u002Fp>\n\u003Cp>If you wish to lift the restrictions on a user, repeat the steps above but \u003Cem>uncheck\u003C\u002Fem> the option box instead.\u003C\u002Fp>\n\u003Ch4>Other plugins\u003C\u002Fh4>\n\u003Cp>Network Restricted Members works best when combined with a network privacy plugin, such as one of the following:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmore-privacy-options\u002F\" rel=\"ugc\">More Privacy Options\u003C\u002Fa> by David Sader\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fnetwork-privacy\u002F\" rel=\"ugc\">Network Privacy\u003C\u002Fa> by Ron Rennick\u003C\u002Fli>\n\u003C\u002Ful>\n","Restrict user access to selected sites on open multisite networks.",10,2115,1,"2016-02-14T04:35:00.000Z","4.0",[64,65,66,67,68],"access-control","membership","multisite","network","user-management","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnetwork-restricted-members.0.3.1.zip"]