Perhaps you could add a word in the README file for saying that asciidoctor format is supported as well? (And what else?)

Also, apparently there’s no support for recurse option in awesome_bot but I was able to make it work with find -name "*.adoc" -print0 | xargs -0 awesome_bot in the .travis.yml file. Perhaps this would also deserve mention in the doc.

Description

Production site has non-super admin editors in the Control Panel that can not change the author of an entry. Worked with Craft guys on support ticket to figure out that when SEO plugin is disabled, the author can be changed. With it enabled, it can not. Stack trace:

2019-11-01 11:11:35 [-][81660][-][error][yii\web\HttpException:400] yii\web\BadRequestHttpException: Unable

Is your enhancement related to a problem? Please describe.
Once WordPress 5.4 is released, we'll want to test Safe Redirect Manager to see if any incompatibility issues arise.

Describe the solution you'd like

• test Safe Redirect Manager on WP 5.4
• op

Description

Create a brand new Jekyll site with the following content:

• index.md

Hello, world!
[Target](target.md)
or {% include include.md %}

• target.md

(anything)

• _includes/include.md

Also try go to the [Target](target.md)

Enable jekyll-relative-links, and build the site.

Expected behavior

Both links to target.md are ren

Right now even contributors can see and create redirects. This might not be ideal so we should at least restrict it to those with publishing caps or even just to admins.

If we make it easy to change who has access via a filter or just documenting using the roles API then I think restricting to admins is the right call.

Maybe it would be better to change style of the button "Add new redirect"?

It could be something like this using the class btn-info.

When clicking any page the current page is used to filter redirect destinations. However, this skips t3:// URNs and is thus not that useful. Thus I'd like to see an option to disable this default filter.