Jetpack activation broken when using changed admin url
-
When activating Jetpack, the service not the plugin, it redirects to it’s admin page but uses /wp-admin in the url and results in 404.
For example, I change my /wp-admin to be /my-admin using this plugin and check the option to block access.
Then I install and activate jetpack plugin and from the jetpack authentication screen provide my details (email/API) which do indeed authenticate but then it redirect to it’s settings page:
/wp-admin/admin.php?page=jetpack#/dashboard
Rather than:
/my-admin/admin.php?page=jetpack#/dashboard
Is this something I should report to jetpack, i.e. not doing something the wp standard way or is this unavoidable because jetpack isn’t aware of the new htaccess rules?
The topic ‘Jetpack activation broken when using changed admin url’ is closed to new replies.