• Resolved samanthafastforward

    (@samanthafastforward)


    The “preview mode” setting does not appear to do anything.

    When I check the “preview mode” box and not the “enable” box:

    – A preview URL is generated, but trying to visit the link results in a 302 redirect to the base URL/no query string. I do not see the notification appear.
    – With debug mode enabled, I see “[WPFront Notification Bar] Preview mode is not enabled” logged to the console. This is true even after clearing the cache in the same way I do to successfully enable and disable a message from showing.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Swathi S

    (@swathiswpfront)

    Hello @samanthafastforward ,

    Can you please share a screenshot of our plugin settings page?

    Thanks!

    Thread Starter samanthafastforward

    (@samanthafastforward)

    Hi Swathi, thanks for the response and sorry for the delay. The screenshot is here – tried pasting the image directly here as well as linking with the image uploader and neither worked, so here is the link. https://drive.google.com/file/d/1C2L3wELO-TK26wIN0Rv0hjVFWeLt9Nsf/view?usp=drive_link

    I blocked out the URL of the dev site but can share it with you privately if possible/necessary.

    Moderator Support Moderator

    (@moderator)

    @samanthafastforward Please revoke that admin access, that is not permitted here even for a staging or non-production site.

    @swathiswpfront You must reply to this topic that you understand and will not repeat that again.

    If you do repeat that, you will be banned from this site and @syammohanm may be removed from www.remarpro.com. It is that serious.

    While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

    If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

    Thankfully are other ways to get information you need:

    • Ask the user to install the Health Check plugin and get the data that way.
    • Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
    • Ask the user to create and post a link to their phpinfo(); output.
    • Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
    • Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
    • Ask the user for the step-by-step directions on how they can reproduce the problem.

    You get the idea.

    We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

    When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

    Plugin Support Swathi S

    (@swathiswpfront)

    I understand and acknowledge that I will not ask for admin access or any other access permissions.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.