Home>Support>After baseline sitepack install, wp-admin redirects/fails

After baseline sitepack install, wp-admin redirects/fails

By VWFeature, 7 years ago. Last reply by Alex S, 7 years ago.

I just dl’d the baseline sitepack plugin, and installed it as directed. When it finished, it said “”cookie expired, log in again.””
when I did, I got
“The www.pcmhpcc.com page isn’t working
www.pcmhpcc.com redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS”

I CAN load CPanel.
I CAN load www.pcmhpcc.com, with title I added, but it seems to have reverted themes to 2017 (Zen Aloe.) I had installed theme w tigers.

Did the sitepack just break the WP install? :(
Is there an easy way to fix this, or would it be simpler to reinstall WP and start over?
I didn’t have that much content, and all copied to home computer. :)
Thanks!

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 7 years, 6 months ago Alex S
    Hi, I Work Here

    Hi VWFeature,

    That’s odd. To clarify, were there any redirects previously? If so, what were they used for?
    I’m trying to work out why there would be a redirect occurring as we don’t add any so that definitely shouldn’t be happening. I suspect the site pack has broken a previous redirect somehow.

  2. 7 years, 6 months ago VWFeature

    Computers are inscrutable. I rolled the WP install back to the day before installing Baseline sitepack plugin, and not only does WP work again, but Baseline is installed, and works.
    I’m guessing it was some bizarre plugin interaction. We’ll never know for sure.
    *************************
    A few days before, I had had the hosting service change the canonical from //website.com to http://www.website.com.
    I had 2 redirects on Cloudflare:
    http to HTTPS, and
    https://website.com* to https://www.website.com$1
    I disabled Cloudflare, but problem persisted.
    ******************************
    Web hosting support insisted it was a problem w DNS caching, even after the restore fixed it. True wisdom means admitting, “I don’t know.”

    All better after the restore from backup. Thank you.
    (Mark as resolved.)

  3. 7 years, 6 months ago Alex S
    Hi, I Work Here

    Hi VWFeature,

    Weird stuff. Well, the important thing is that it’s working for you now. I’ll try and run a few tests to see if I can replicate this regardless.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More