Viewing 4 replies - 1 through 4 (of 4 total)
  • Either one should be ok. The first example is more straightforward, but not 100% necessary.

    If you do either, I just suggest making them relative to the root folder, so the redirect URL would be /invite/invitecode/and the destination URL would be app_name://invitecode/.

    If ‘app_name://’ is not a standard protocol, then you may need to add a filter to add the app_name protocols to the allowed protocols, so that the plugin does not strip them for being not allowed.

    Let me know if you need a hand with that.
    Warmest regards,
    Don

    Thread Starter 8bitkid

    (@8bitkid)

    I wound up having to handle all of this through the .htaccess file.

    When you mention adding filters, where would I do that?

    The filter would only be needed if you were adding the redirects via the plugin.

    For completeness and if you did use the plugin and wanted to add a filter, it would be something like this (added to the theme’s function.php file after the <?php tag):

    add_filter('qppr_allowed_protocols','custom_qppr_allowed_protocols');
    function custom_qppr_allowed_protocols($allowed){
         $allowed[] = 'app_name';
         return $allowed;
    }

    This would allow you to add redirects with the app_name:// protocol otherwise it would give you an error saying it is not allowed.

    Warmest regards,
    Don

    Thread Starter 8bitkid

    (@8bitkid)

    Thanks so much. In the future, it would be great if the plugin could handle this. I wound up just doing it via my .htaccess file, but would rather have a plugin-based solution.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘redirect to iOS app with query string or custom path’ is closed to new replies.