PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Fatal Error activating plugin on Windows Server

  1. robertpalmer

    The latest version of Gravity Forms ( returns the following error when my customer tries to activate the plugin:

    Warning: require_once(E:\Spaces\wrightro\\wwwroot/wp-content/plugins/gravityforms/widget.php): failed to open stream: No such file or directory in E:\Spaces\wrightro\\wwwroot\wp-content\plugins\gravityforms\gravityforms.php on line 70 Fatal error: require_once(): Failed opening required 'E:\Spaces\wrightro\\wwwroot/wp-content/plugins/gravityforms/widget.php' (include_path='.;C:\php\pear') in E:\Spaces\wrightro\\wwwroot\wp-content\plugins\gravityforms\gravityforms.php on line 70

    As you can see, the customer is running this on a Windows installation. Their hosting provider says that the forward slashes in the URL are not allowed (as in the underlined URL). This seems to have cropped up in just the latest version. Is there something we can do to solve this problem?

    Thanks in advance for your help!

    Posted 10 years ago on Wednesday March 7, 2012 | Permalink
  2. The latest version of Gravity Forms is v1. and not the version you referenced below.

    There are no known issues with Gravity Forms functioning on Windows based servers and we have many users using Gravity Forms on Windows based hosts.

    Nothing has changed as far as how files are included in Gravity Forms in the last release. Gravity Forms also uses built in WordPress functions to get the correct plugin path.

    I would suggest re-installing Gravity Forms by deleting the existing plugins and then re-installing and activating the latest version which you can download from the support site.

    I have closed your support forum post as posting on both the support forum and via priority support can cause a duplication of effort by our support team and we will handle this via your priority support request.

    Posted 10 years ago on Thursday March 8, 2012 | Permalink

This topic has been resolved and has been closed to new replies.