WordPress.org

Ready to get started?Download WordPress

Forums

Propel
[resolved] Activation causes white screen (9 posts)

  1. RogerWheatley
    Member
    Posted 2 years ago #

    When activating Propel 2.0.1 using WordPress 3.3.1, the WP Admin area will white screen and the front end will white screen. Deleting plugin via FTP restores access.

    Any fix on the white screen issue?

    Thanks.

    http://wordpress.org/extend/plugins/propel/

  2. johnciacia
    Member
    Plugin Author

    Posted 2 years ago #

    Propel has been tested in WordPress 3.3.1 on a fresh install with no problems. This white screen is likely due to an environment issue but without more information I cannot be much help. Please enable WP_DEBUG (http://codex.wordpress.org/Editing_wp-config.php#Debug) then install/activate propel. Yes, it will "white screen" again, but this time it will display errors. Copy/paste any errors/warnings that appear here, and I will push out a patch ASAP.

  3. RogerWheatley
    Member
    Posted 2 years ago #

    No sorry, that does not work. No errors displayed, nothing in wperror.log. Just white screen, period.

    Here's what I used in wp-config.php:

    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', true);
    @ini_set('log_errors','On');
    @ini_set('display_errors','On');
    @ini_set('error_log','/home/rwsitewp/logs/wperror.log');

    wperror.log was chmod to 777 (just in case).

  4. johnciacia
    Member
    Plugin Author

    Posted 2 years ago #

    Without an error, I can't be of much help. Keep in mind, in your wp-config.php file WP_DEBUG is set to false by default. Make sure you place the above code below the default definition to overwrite the value (or remove the line where WP_DEBUG is set to false).

  5. RogerWheatley
    Member
    Posted 2 years ago #

    Thanks v0idless, I appreciate your time, that was nice.

    I did do that (above), it does not throw any errors, just white screen. That's too bad. :(

    It seems therefore Propel is of no use to me, I won't waste anyone's time, and simply move on to another solution instead.

    (I'm really sorry Propel).

    And... I don't mean any of this in a bad way. (Please don't misunderstand).

  6. RogerWheatley
    Member
    Posted 2 years ago #

    For anyone this will help... My internal server WordPress install does throw this error (production server throws no error):

    Warning: require_once(__DIR__/functions.php) [function.require-once]: failed to open stream: No such file or directory in /var/www/sandbox/wp-content/plugins/propel/propel.php on line 57
    
    Fatal error: require_once() [function.require]: Failed opening required '__DIR__/functions.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /var/www/sandbox/wp-content/plugins/propel/propel.php on line 57
  7. johnciacia
    Member
    Plugin Author

    Posted 2 years ago #

    Great! Now I have something I can work with. I will take a closer look and try get a patch out today/tomorrow.

    1. Does functions.php (in the /propel/ directory) exist?
    2. What version of PHP are you running?

    I have a feeling I might know what the problem is.

    Edit 1: Propel uses the __DIR__ magic constant which was introduced in PHP 5.3. I am going to bet you are running an older version of PHP. I will fix this and push out a patch as soon as I can.

    Edit 2:: If you do indeed have a version of PHP older than 5.3, the latest version of Propel (2.0.2) should fix your problem.

  8. RogerWheatley
    Member
    Posted 2 years ago #

    1. Yes.
    2. PHP 5.2.13

    Edit 1: Correct!

    Edit 2: Correct!

    I just "upped" the internal to PHP 5.3.2 and it works.

    Testing on production server and Propel 2.0.2 is able to activate.

    Not to anyone reading this:
    Developer did a great job, especially as some other packages on the server, for the time being still need PHP 5.2.x

    Personally, I was very concerned to waste people's time (which I didn't want to do). And would have simply moved to another solution.

  9. johnciacia
    Member
    Plugin Author

    Posted 2 years ago #

    Great! This was a slight oversight on my part. Since WordPress works 5.2.x so should this plugin. So thanks for the bug report, I'm sure you saved others the headache. I'm now marking this topic as resolved.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags