Browser Rejector
[resolved] 500 (Internal Server Error) (4 posts)

  1. infobydesign
    Posted 3 years ago #

    /wp-content/plugins/browser-rejector/rejectr.js.php 500 (Internal Server Error)

    Deletion and reinstall does not correct the problem.

  2. Nick Halsey
    Plugin Author

    Posted 3 years ago #

    Hi, I don't think this plugin could be causing that error, is it only happening when this plugin is active?

    As the wording of the error suggests, there's probably something wrong with the server configuration, which may have happened coincidentally to coincide with when you installed the plugin.

    Try some of the solutions here, do any work? http://www.cyberciti.biz/tips/http-error-500-internal-server-for-php-pages-and-solution.html

    If it is definitely something to do with this plugin, please let me know what the PHP log files say (mentioned in the link). This plugin mostly works in JavaScript, PHP is only used for setting and getting options, which most plugins do in the same way.

  3. infobydesign
    Posted 3 years ago #

    The plugin worked great for a few weeks. Then, it stopped functioning due to a 500 internal server error in rejectr.js.php. So, I disabled it.

    After migrating to LiteSpeed from Apache, I decided to give it another try - just in case the problem was on my end. Now, the plugin still doesn't work - but the error is different:

    'Uncaught SyntaxError: Unexpected token < rejectr.js.php:1'

    Nothing else in my WordPress install is experiencing problems. And, when I disable the plugin the errors messages stop. So, I have to conclude that it's the plugin.

  4. Nick Halsey
    Plugin Author

    Posted 3 years ago #

    Ok, I know what that would be. Could you open in Chrome, inspect element, and in the resources tab find rejectr.js.php (under scripts)? Then let me know what the entire first line of that file is? I'll be able to determine the specific solution for you're case.

    It's a php-generated JavaScript that threw a PHP error (which is what I need to see), so the browser can't execute the js because the error comes out as html. I'll look into ways to suppress these errors there, but something has probably gone wrong with undefined option indices I'm your case.

    I think the 500 error could have been something to do with your old configuration handling these errors differently... I'll look at ways to prevent this in general in case anyone else faces similar issues.

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Browser Rejector
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic


No tags yet.