[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fBVakcK4jDeVHgYElYWGK_4WKrznGNefUgmeQ8WkD160":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},"michielve","https:\u002F\u002Fprofiles.wordpress.org\u002Fmichielve\u002F",4,1320,92,644,73,"2026-04-04T06:06:15.163Z",[13,37,58,76],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":19,"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":32,"vuln_count":33,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"private-google-calendars","Private Google Calendars","20251206","\u003Cp>\u003Cstrong>If you update to version 20230111, please note that\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The theming has slightly been changed. Now there is distinction between bundled and custom themes.\u003C\u002Fli>\n\u003Cli>The previously bundled dark and light themes have been renamed. So if you used these themes, you now have to manually update these themes to the new pgc-dark and pgc-light themes.\u003C\u002Fli>\n\u003Cli>The popup theme has been removed. This can now be set in your custom theme.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See for details about this release: https:\u002F\u002Fblog.michielvaneerd.nl\u002Fwordpress-plugins\u002Fprivate-google-calendars\u002Fversion-20230111-details\u002F\u003C\u002Fp>\n\u003Cp>This plugin can display multiple private and public Google calendars with a shortcode, Gutenberg block or as a widget.\u003C\u002Fp>\n\u003Cp>See the \u003Ca href=\"https:\u002F\u002Fblog.michielvaneerd.nl\u002Fwordpress-plugins\u002Fprivate-google-calendars\u002F\" rel=\"nofollow ugc\">webpage\u003C\u002Fa> for more information.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Access to \u003Cem>private\u003C\u002Fem> (and public) calendars by using OAuth2 or an API key.\u003C\u002Fli>\n\u003Cli>Adjustable caching – this can greatly improve the performance.\u003C\u002Fli>\n\u003Cli>It uses the \u003Ca href=\"https:\u002F\u002Ffullcalendar.io\u002F\" rel=\"nofollow ugc\">FullCalendar\u003C\u002Fa> library to show the calendar and can be fully customized within the Gutenberg block, shorcode attributes and the widget settings.\u003C\u002Fli>\n\u003Cli>Calendar filtering.\u003C\u002Fli>\n\u003C\u002Ful>\n","Display private and public Google Calendars on your Wordpress website.",1000,52788,96,23,"2025-12-06T17:17:00.000Z","6.9.4","4.6","5.4.0",[28,29],"calendar","google","http:\u002F\u002Fblog.michielvaneerd.nl\u002Fprivate-google-calendars\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fprivate-google-calendars.zip",98,2,0,"2025-11-10 15:11:48","2026-03-15T15:16:48.613Z",{"slug":38,"name":39,"version":40,"author":4,"author_profile":5,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":48,"homepage":54,"download_link":55,"security_score":45,"vuln_count":56,"unpatched_count":34,"last_vuln_date":57,"fetched_at":36},"api-bearer-auth","API Bearer Auth","20200916","\u003Cp>The API Bearer Auth plugin enables authentication for the REST API by using JWT access an refresh tokens. After the user logs in, the access and refresh tokens are returned and can be used for the next requests. Issued tokens can be revoked from within the users admin screen. See below for the endpoints.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note that after activating this plugin, all REST API endpoints will need to be authenticated, unless the endpoint is whitelisted in the \u003Ccode>api_bearer_auth_unauthenticated_urls\u003C\u002Fcode> filter (see FAQ for how to use this filter).\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>JWT\u003C\u002Fh4>\n\u003Cp>Access tokens can be formatted as JWT tokens. For this to work, you first have to create a secret and add it to the wp-config.php file. If you don’t do this, access tokens will work also, but are just random strings. To create a random secret key, you can do for example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>base64_encode(openssl_random_pseudo_bytes(64));\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>And then add the result to wp-config:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define('API_BEARER_JWT_SECRET', 'mysecretkey');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you have problems, you can verify your JWT tokens at: \u003Ca href=\"https:\u002F\u002Fjwt.io\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fjwt.io\u002F\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Revoke tokens\u003C\u002Fh4>\n\u003Cp>This plugin adds a column to the users table in de admin where you can see when a token expires. You can also revoke tokens by selection the “Revoke API tokens” from the bulk actions select box.\u003C\u002Fp>\n\u003Ch4>API endpoints\u003C\u002Fh4>\n\u003Cp>Note that all endpoints \u003Cstrong>expect JSON in the POST body\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Login\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Endpoint:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>POST \u002Fapi-bearer-auth\u002Fv1\u002Flogin\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Request body:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note: \u003Ccode>client_name\u003C\u002Fcode> is optional. But if you use it, make sure to use it as well for the refresh call!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"username\": \"my_username\", \"password\": \"my_password\", \"client_name\": \"my_app\"}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Response:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"wp_user\": {\n    \"data\": {\n      \"ID\": 1,\n      \"user_login\": \"your_user_login\",\n      \u002F\u002F other default WordPress user fields\n    }\n  },\n  \"access_token\": \"your_access_token\",\n  \"expires_in\": 86400, \u002F\u002F number of seconds\n  \"refresh_token\": \"your_refresh_token\"\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Make sure to save the access and refresh token!\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Refresh access token\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Endpoint:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>POST \u002Fapi-bearer-auth\u002Fv1\u002Ftokens\u002Frefresh\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Request body:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note: \u003Ccode>client_name\u003C\u002Fcode> is optional. But if you did use it for the login call, make sure to use it here as well!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"token\": \"your_refresh_token\", \"client_name\": \"my_app\"}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Response success:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"access_token\": \"your_new_access_token\",\n  \"expires_in\": 86400\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Response when sending a wrong refresh token is a 401:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"code\": \"api_api_bearer_auth_error_invalid_token\",\n  \"message\": \"Invalid token.\",\n  \"data\": {\n    \"status\": 401\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Do a request\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>After you have the access token, you can make requests to authenticated endpoints  with an Authorization header like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Authorization: Bearer \u003Cyour_access_token>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Note that Apache sometimes strips out the Authorization header. If this is the case, make sure to add this to the .htaccess file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>RewriteCond %{HTTP:Authorization} ^(.*)\n# Don't know why, but some need the line below instead of the RewriteRule line\n# SetEnvIf Authorization .+ HTTP_AUTHORIZATION=$0\nRewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you are not logged in or you send an invalid access token, you get a 401 response:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\n  \"code\": \"api_bearer_auth_not_logged_in\",\n  \"message\": \"You are not logged in.\",\n  \"data\": {\n    \"status\": 401\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Important update\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Update immediately if you’re using a version below 20200807. Before this version all access tokens were updated when calling the refresh callback.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you are affected by this the fastest solution is to execute this query:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>update wp_user_tokens set access_token_valid = NOW();\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This will invalidate all access tokens. This means that all users need to refresh their access token and will get a new access token and a unique one this time.\u003C\u002Fp>\n\u003Cp>A big thank to @harchvertelol for reporting this and suggesting the fix as well!\u003C\u002Fp>\n","Access and refresh tokens based authentication plugin for the REST API.",300,23510,100,6,"2025-12-08T09:52:00.000Z",[49,50,51,52,53],"api","authentication","jwt","jwt-tokens","rest-api","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fapi-bearer-auth.zip",1,"2019-09-05 00:00:00",{"slug":59,"name":60,"version":61,"author":4,"author_profile":5,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":34,"num_ratings":34,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":54,"tags":69,"homepage":54,"download_link":73,"security_score":74,"vuln_count":34,"unpatched_count":34,"last_vuln_date":75,"fetched_at":36},"quick-questionnaire","Quick Questionnaire","2.5","\u003Cp>Create simple exercises directly in the editor by putting the possible answer(s) in double brackets.\u003Cbr \u002F>\nA quick questionnaire must be an ordered or unordened list.\u003C\u002Fp>\n\u003Cp>The following types of answers are possible:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enter the correct answer in a textbox:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The correct answer has to be entered in a textbox.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cul>\n  \u003Cli>The capital of France is ...? {text{ Paris }}\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can also use a case insensitive textbox by using the \u003Ccode>itext\u003C\u002Fcode> property:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cul>\n  \u003Cli>The capital of France is ...? {itext{ Paris }}\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Enter the correct answer in a textbox – multiple answers possible:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The correct answer has to be entered in a textbox.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cul>\n  \u003Cli>The capital of France or Italy is ...? {text{ Paris | Rome }}\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Enter the correct answer in a textbox – regular expression:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you have some regular expression skills, you can also specify this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cul>\n  \u003Cli>The capital of France or Rome is ...? {reg{ \u002F^(Paris|Rome)$\u002F }}\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Check the correct answer in radio buttons:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>All possible answers are divided by |, the correct answer has to be marked with a *.\u003Cbr \u002F>\nThe answers are displayed as radio boxes.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cul>\n  \u003Cli>The capital of France? {radio{ Paris* | London | Berlin }}\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Check all possible answers in checkboxes:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Mark alle correct answers with a *.\u003Cbr \u002F>\nThe answers are displayed as checkboxes.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cul>\n  \u003Cli>Countries of Europe? {checkbox{ France* | Netherlands* | Canada }}\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Create simple exercises directly in the editor.",10,1822,"2023-11-25T16:50:00.000Z","6.4.8","3.0.1",[70,71,72],"exercise","practice","test","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquick-questionnaire.zip",85,null,{"slug":77,"name":78,"version":79,"author":4,"author_profile":5,"description":80,"short_description":81,"active_installs":64,"downloaded":82,"rating":34,"num_ratings":34,"last_updated":83,"tested_up_to":84,"requires_at_least":68,"requires_php":54,"tags":85,"homepage":91,"download_link":92,"security_score":74,"vuln_count":34,"unpatched_count":34,"last_vuln_date":75,"fetched_at":36},"simple-fast-highlighter","Simple Fast Highlighter","1.0.5","\u003Cp>There are other good syntax highlighter plugins, but I wanted something simple and fast and\u003Cbr \u002F>\nbe able to add the highlight classes with a select box in the TinyMCE editor.\u003C\u002Fp>\n\u003Cp>I added some default languages: Javascript, PHP, Python, C, C#, VB.NET, SQL and CSS but you can\u003Cbr \u002F>\neasily add other ones.\u003C\u002Fp>\n","Fast syntax highlighter written in Javascript.",1971,"2017-04-08T15:38:00.000Z","4.7.32",[86,87,88,89,90],"code","highlight","highlighter","sourcecode","syntax","http:\u002F\u002Fmichielvaneerd.github.io\u002Fsimplefasthighlighter\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-fast-highlighter.zip"]