• Hi, after correctly installing W3 Total Cache and configuring it I’ve added the Cloudflare extension. Correctly setup Cloudflare to work with W3 Total Cache. Then, I’ve got a paid account with Stackpath and configured the CDN according to
    https://support.stackpath.com/hc/en-us/articles/360001078983-WordPress-with-W3-Total-Cache-CDN-Setup-Guide

    However, if I select General Settings->CDN->StackPath (recommended), I cannot configure Stackpath with the Client ID and Client Secret keys because the fields do not show up. Instead, by selecting General Settings->CDN->Generic Mirror the fields show up and I can fill it. Then, I switch to General Settings->CDN->StackPath and save.

    It seems to work….

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello,

    If I may confirm. When you select CDN and StackPath (recommended) from a dropdown menu and save all settings. After that, you go to Performance>CDN and click the Authorize button. You should get a new pop-up window to enter Your StackPath Account credentials with following fields:
    API Client ID:
    and
    API Client Secret:
    Can you confirm that you are not getting that and if so, what does actually show up?

    Thread Starter scubarob

    (@scubarob)

    Hi Marko,

    I confirm I cannot get the pop-up window. Nothing happens when I click the “Authorize” button.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello,
    Can you try to disable Cloudflare and see if you can authorize Stackpath while Cloudflare is disabled?

    Thread Starter scubarob

    (@scubarob)

    Hi Marko. I’ve already tried, it doesn’t work either.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello,

    Are you using any other language in your WP dashboard instead of English? If that the case please switch to English and try again.
    If you already use English then we need server access to check the issue.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    @scubarob Do not ask anyone to log into you site please. I have archived your post. @vmarko would risk getting banned from these forums if that happenes.

    @vmarko Please reply here to make it clear that you will not log into a user’s site. It’s that serious.

    Thread Starter scubarob

    (@scubarob)

    Hi Jan,

    please take the time to read the posts above. Then look below:

    First, Marko kindly asked access to my site

    Second, it appears to be common practice on WP support forums as it already happened to me

    Third, I acknowledge your rules but when issuing reminders please assess the situation and then act

    Regards

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I don’t disagree with you exactly but this is a bad take.

    Second, it appears to be common practice on WP support forums as it already happened to me

    Not here it’s not. People who do that get warned. When that happens again, they risk getting banned and their plugin pulled. It’s that serious and saying it’s common doesn’t matter. When it’s found it’s corrected as I have done.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello,
    @jdembowski I can confirm that I will not log in to users site.
    If it’s ok with you, I would like to suggest to @scubarob to contact us via plugin?

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    If it’s ok with you, I would like to suggest to @scubarob to contact us via plugin?

    Sure. But even then, don’t log into the user’s site or ask to.

    Please note: I’m not picking on you and I think you understand that. 😉

    Your company had this experience before a few months back. Too many plugin support/authors have been walking around the rule and that needs to stop for everyone.

    Here’s some suggestions for what/how to get that data without logging into a user’s site.

    There are many ways to get information you need and accessing the user’s site is not one of them. That’s going too far.

    You get the idea.

    Volunteer support is not easy. But these forums need to a safe place for all users, experienced or new. Accessing their system that way is a short cut that will get you into real trouble in these forums.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @jdembowski,

    Thank you for your suggestion.
    I am sorry about this and it will not happen again.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Stackpath + Cloudflare’ is closed to new replies.