Thread

Is it the same error, about ob_end_clean()? Can you try to disable your extensions?

No, this time around I do NOT see an error message.  Just a blank screen.

I can get to pages withing the control panel (address removed by author).

Is the long string there right?  I feel like those long strings are new.  But I’m not sure.

but if I click back to “CP Home” again, blank page.

Also, LG TinyMCE is not working.

OK extensions disabled.  Same problems.

Also - I checked with my host and no changes occurred there yesterday.

?

The “long string” is just a session id, and just fine. A blank screen is usually a suppressed PHP error. Can you try to turn on error reporting, see if that gets us a meaningful message? Also, do you know how much RAM you have in your environment? Try to bump that up a little, if your host lets you.

Error reporting IS turned on.

And that worked at some point, but not any more? Does it work on regular, non-EE PHP pages? Try to create an error on purpose, like so

<?php echo foo ?>

Hello, error reporting worked for the initial transient error, I left it on.

It’s still on.  It works on sub pages (I had incorrect file in the extentions folder for an unrelated reason and that caused and error that showed) but nothing is showing on the blank page after log in.

Can I re-enable the extensions now?

Hi, Here might be a clue

As I test, I turned error reporting “OFF” - results in blank page

<?php

error_reporting(0); 

$pathinfo = pathinfo(__FILE__);
$ext = '.'.$pathinfo['extension'];

require './core/core.system'.$ext;

?>

So then I turn it “ON” - page shows - but no error shows.

<?php

error_reporting(E_ALL); 

$pathinfo = pathinfo(__FILE__);
$ext = '.'.$pathinfo['extension'];

require './core/core.system'.$ext;

?>

SO then I assume I need to force PHP errors to show, so I add the code line for that - this worked for the first error I was having but it DOES NOT WORK NOW - back to blank page.

<?php

error_reporting(E_ALL); 
ini_set('display_errors', 1); 

$pathinfo = pathinfo(__FILE__);
$ext = '.'.$pathinfo['extension'];

require './core/core.system'.$ext;

?>

I’ve tried this resetting several times and these results are consistant.  Only the middle code here works.  It works in both IE and Firefox.

Maybe I should just leave it like that.

Meanwhile, why is LG TinyMCE no longer working?  Is this related?  How could this happen when I have not made any file changes?

I guess I’ll go ahead and uninstall and reinstall LG TinyMCE.

Any thoughts on this are appreciated.  I’ll be offline for a few hours but back on EST 9:00pm.  Thanks so much.

Did you update your extensions when you did the update?

I’m running 1.3.3 LG Tiny MCE which looks like the latest version.  ( I backed up the extensions separately and re-uploaded after the update).

My plan is re-download a fresh version and completely reinstall.  I’m also using TinyBrowser which required some modifications to the LG Tiny Mice and I’ll redo those too.

I’ll provide an update when that’s done.

OK, I’m using tips from this thread. 

And I’m having success with SEEING TinyMCE in the entry fields using the settings with the URL path including www/... and making sure the pages are viewed with www/...

I’m still having some issues with the Tiny Browser and will keep working on those and post an update.

charmedworks - are you still experiencing blank pages when logging into the control panel?  Or has that now been rectified and you’re moving on to extensions?

I am no longer seeing blank pages when logging into the control panel using the code supplied above (middle example) in the index.php page.

Update - I have reinstalled LG TinyMCE and other extensions and now everything is working fine.  That’s great.

However I am seeing blank pages when using the index.php page (top example) as supplied in the install and upgrade.  Or when I attempt to force error reporting (bottom example).

Not sure if I can just leave it as is (attempting to report errors but not showing them) - as that’s working fine.  I just want to make sure it’s ok to leave it like that or if I should keep troubleshooting.