Adam Silverstein

@ivan192 can you check now, i tried a fix

Hmm, I have these running thru the translansation function in JavaScript, maybe I am not loading the text domain correctly? https://plugins.trac.www.ads-software.com/browser/mathml-block/trunk/src/mathml-block.js#L37 I’ll need to read thru the documentation further to see what is wrong.

Hey @ivan192 thanks for your offer to help translate the plugin. I’ll take some time soon to ensure all my strings are translated correctly and comment back here when I have that completed.

Haven’t tried this with Woo, are those standard users or user roles? This is only set up to work with standard users.

Thanks for the reminder @roseyazman

@primaltalk – are you creating the post in a published state? try creating a draft, then updating to being published, I believe Publicize relies on the ‘transition_post_status’ hook and this may not fire if you create a published post directly (which never happens in wp-admin since an autodraft is created as soon as you open the editor).

This issue is resolved in the most recent version of the plugin.

Hey @jdslimz! thanks for your note! I missed it until now!

I welcome your contribution, the plugin is already on github here: https://github.com/adamsilverstein/user-admin-simplifier

@alfablue I did update the plugin recently, are you still having any issues with the latest version?

glad it worked well for your use case @pigo3934blog, thanks for the review.

Yes, the wp-api client will handle cookie-based authentication which you need for anything beyond public reading endpoints. OAuth and basic auth are two other authentication options. To secure the API endpoints you would use the same types of users checks you would use elsewhere in core (‘current_user_can()’). If the user is authenticated they the check will be for that user.

Hi @jvke,

Are you talking about in the case where you are building a JavaScript based theme that pulls its data from the API? This will require some extra work.

WordPress stores the post data in a temporary ‘autosave’ revision when you click the preview button: you will need to alter or filter your endpoint return to use the revision data instead of the post data to display the preview. You can do this by adding a custom route with for ‘{route}/preview’, which adds a query var. the data endpoint responds to this by grabbing the autosave with ‘wp_get_post_autosave’ and returning the data from the revision.

@jaspercreel – the filter parameter was deprecated when the API was merged with core in WordPress 4.7.0. You can re-enable the filter functionality with this plugin: https://github.com/WP-API/rest-filter

This plugin restores the original filter functionality from the plugin in WordPress core: https://github.com/WP-API/rest-filter

Where you ever able to get this working? Can you tell me what theme and plugins you have active? If possible, can you test the plugin using no other active plugins and the default theme active and see if it works for you then?