Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Xyala

    (@xyala)

    Awesome, problem solved!

    Quick question related to this, i’d like to make a small edit which would be using

    add_filter('wpa_after_login_redirect', function($url){
        return 'https://example.com/my-redirec-page/';
    });

    but instead of returning a hardcoded URL, returns a parameter of the shortcode.
    Such as
    [passwordless-login redirect_URL="http://example.com/redirectafterlogin-page"]

    What would be the change to make to that filter?

    • This reply was modified 6 years, 3 months ago by Xyala.
    • This reply was modified 6 years, 3 months ago by Xyala.

    Yeah, I switched back to 9.2.1 for now, will see what the dev can help us out with here. 🙂

    I have a similar issue since doing the update this morning.

    I have the following site structure:

    ROOT-URL
    ROOT-URL/services/ (page)
    ROOT-URL/projects/ (page)
    ROOT-URL/contact-us/ (page)

    and here is the issue:

    I have a custom post-type called portfolio
    I had set in the plugin settings (before update):

    portfolio: ROOT-URL/projects /%tagportifolio%/%postname%/
    Which sets URLs like this
    ROOT-URL/projects/project-type/project-name/
    These URL work perfect still … but now, my “projects” page isn’t working anymore. It displays it’s content as an archive of “projects”

    So I guess the rewrite rules that “projects” when alone in the URL is part of the custom post type and no more a stand alone page.

    Note: in common settings, I’ve set the following ROOT_URL/sample-post/ (default thing)

    How can I fix that?
    Thanks ahead for helping troubleshoot.

    PS: I tried to change the slug of that “projects” page into “project” and it fixed the issue which confirms that rewrite issue… I guess. Hope this additional info helps.

    PS2: I had no issue on 9.2.1

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