Ron Wardenier

Removing `default` didn't help unfortunately.

Take a look at [Using Function Calls (data-*@)](https://learn.getgrav.org/16/forms/blueprints/advanced-features#using-function-calls-data-at)in the Grav documentation. I've never used this method with the `placeholder` field property but in theory it should work as it works...

I'm using Apache. Thanks to your elaborate answer I came up with the following solution. To allow the normal use of some specific files I added a rule similar to...

Apparently my explanation wasn't clear. I'm sorry for that. The extra rule does not apply to the `public` directory. In the example it allows direct access to the `robots.txt` file...

Okay. However I just don't understand why you want to advertise a limitation which can so easily be lifted.

@fredrikekelund and @guins, would it be possible to merge the two use cases into a single (this) plugin and select the 'mode' via a configuration option?

I can not replicate this. As can be seen in line https://github.com/bleutzinn/grav-plugin-editable-contenttools/blob/8965544681807a99e19f5445e873a1d0cc2788ab/editable-contenttools.php#L23 all assets, being the 2 CSS and 4 JS files, are added in one go. So when the...

Yes, these URL's are relative to the webroot of your site. It appears you've installed Grav in the webroot. The demo is installed in a subdirectory (`demo-grav-plugin-editable-contenttools`) and thus the...

When enabling the JavaScript pipeline Grav will try to include the file `editor.js` as well. But will fail to do so because there is no such physical file at that...

Are you having this with the JavaScript pipeline enabled or disabled?