mrthunderfield

I’m an idiot, didn’t get that the “Items displayed” metabox on the right was exactly for this.

(Removed redundant comment)

• This reply was modified 3 years, 10 months ago by mrthunderfield.
• This reply was modified 3 years, 10 months ago by mrthunderfield.
• This reply was modified 3 years, 10 months ago by mrthunderfield. Reason: Code formatting
• This reply was modified 3 years, 10 months ago by mrthunderfield. Reason: redundant comment

@drazenbebic

Yes, exactly! I basically need routes that can be called from frontend code which can’t include secrets.

I’ve been using the plugin now as it is, including the secret in the frontend code, and disabling routes that I don’t need. It’s been working great, but still feels wrong to include the secret in the frontend code.

Hi!

Thanks for the swift reply and for the fix! That is awesome.

Once I got rid of the enqueue error and got the plugin activated, I noticed that the WordPress editor was completely broken. The content was white (but selectable) and the toolbar was empty and also white.

I’ll continue hacking to maybe get a working plugin, but a swift update would be awesome!