WP Toolkit and WWW

General Rules
1

WP Toolkit does not support WWW when I tested a new installation.

How to manage redirection using Page rule as I like to work also admin URL?

https://example.com/wp-admin/
Website should be https://www.example.com/ and not https://example.com/

4

If you do that, you’ll also be affected by the redirect and it will be very difficult to reach wp-admin.

This doc on Rules should help,

5

I have read. Thank you for the message!
Each wildcard corresponds to a variable when can be referenced in the forwarding address. The variables are represented by a $ followed by a number. To refer to the first wildcard you’d use $1, to refer to the second wildcard you’d use $2, and so on.

Can you inform us specific WP Page rules (3 fields) if this will work:
From: https://example.com/*
Forwarding URL (Status Code: 301 - Permanent Redirect, Url: https://www.example.com)

modified Page Rule:
https://example.com/$1
Forwarding URL (Status Code: 301 - Permanent Redirect, Url: https://www.example.com)

6

You cannot reference the wildcard with $1 in the match section. It is * there. It becomes $1 when you reference it in the rule action. See the following examples.

If the URL matches: https://example.com/*
Forwarding URL (Status Code: 301 - Permanent Redirect, URL: https://www.example.com/$1)

If the URL matches: https://*.example.com/*
Forwarding URL (Status Code: 301 - Permanent Redirect, URL: https://$1.example.net/$2)

7

Can you post for us an example for https://example.com/wp-admin/

8

I cannot. I am unclear on your objective. I have read and re-read your original post and do not understand the problem that you are trying to solve. You shouldn’t have to do any special redirect on your wp-admin URL. You might find better answers from the WP Toolkit developers.

9

It is very simple.

  1. If you have HTTPS://example.com we need to redirect to https://WWW.example.com.
    If we involve WP Toolkit, it is not supported WWW but instead it demands HTTPS://example.com.
  2. As there is CMS, it should solve also https://example.com/wp-admin/
    So, our objective is to solve point number 1 HTTPS://example.com into https://WWW.example.com
    and the second point to login into CMS.
10

I don’t know what else to tell you. I don’t use WP Toolkit and I only ever access my wp-admin path using the canonical hostname defined in the WordPress instance. I suggest asking the WP Toolkit developers becusse if it is subject to the strange limitations that you describe, they would likely have experience in recommending a working solution to the problem they have created.

11

It is Cloudflare Page Rule issue not related to WP Toolkit for redirections.

12

It looks to me like you are trying to use Page zrules to overcome a limitation in WP Toolkit. Whatever it is, there is nothing else I can suggest. Maybe another Community member will have something else to offer.

16

Hi,

Do you mind to share the documentation detailing this limitation?

Anyway, if WP Toolkit handles domains and subdomains somehow like Softaculous does, you could perhaps try cloning your example.com installation onto the www. subdomain, provided you have a working www. subdomain in cPanel.

1 Like
17

Issue is how to force domain to WWW and HTTPS and keep login for a WP installation.
If you install WP Toolkit, you see it is pure HTTPS://example.com without WWW. Page rules solve this option but do not know how to manage.

18

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.