Support Forum
Support Forum
Offline
- SP Version 5.6.7
- Blog Post Linking Version 1.2.18
- WordPress Version 4.5.2
The Editor does show with the BP Linking plug-in installed now, however, I do continue to get the White Page after I publish the post (regular WP blog post). Once I refresh the post listings, the posts does show it published. However, it appears that we're having an issue with the dashboard not returning to the post after we click on "Publish", as it normally should. Again, this problem disappears as soon as I deactive that BPL plug-in.
After disabling the BPL plug-in, I pulled my server error log and so far I don't see any new entries.
Offline
did you try the wp debug switch as requested? would like to see if anything is displayed when you do a post and get the white screen...
Visit Cruise Talk Central and Mr Papa's World
Offline
Mr Papa said
did you try the wp debug switch as requested? would like to see if anything is displayed when you do a post and get the white screen...
Yes, we have modified the config file to show 'true', however, we immediately get a white page with errors. The site won't load unless we revert back to the old config without the debug mode on. Apparently, setting the site to debug mode could result in these deprecated modes that we're experiencing? In addition, because this is a live site, we can't afford to have the site down for a good length of time.
Here are the top level message that pops-up;
Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/inception/public_html/wp-includes/wp-db.php on line 1520
Offline
Sorry about the delay.
My initial impression is that there is something fishy going on here. WordPress has not used mysql_connect() for quite a long time - unless the preferred mysqli library is not installed - which would be unusual. They certainly do not use it at line 1520 although they DO use the mysqli equivalent.
I would suggest before we go any further it would be worth checking with your host the PHP and MYSQL version numbers and, specifically, whether your PHP has the mysqli library installed.
However, I would doubt that the lack of that library would cause the white screen. That sounds like a php 'fatal error'. If it is then it would be reported in the error log (which is what the wp debug setting should show on the screen except for the intervention of the mysql issue). So can you taker a look at your php error log? If you do not know where it is then you can usually get to look at it via the hosting control panel.
You may have many entries but you are specifically looking for one marked as 'fatal error' following the white screen occurence,
 |
YELLOW
SWORDFISH
|
Offline
I am trying to find a way to generate and retrieve a PHP error log. I wanted to note that we have been running 10.0.25-MariaDB for the past few months. We made the change after we noticed the initial issue with the SP plug-in. The site has run a bit more efficiently after upgrading from an outdated version of MySQL to Maria.
Regarding these missing libraries and such. I do have WHM access and could try to add any missing modules via easyapache. I'm just not sure what modules I should be looking for in the exhaustive options list??
Offline
its called mysqli...and its just another module...its actually php that is doing away with mysql_connect in favor of the mysqli variant...
dont know why the debug would take the site down and show white page... it doesnt do anything differently than display errors... could you have mistyped the command?
also, the deprecated warning wont stop things from running...
Visit Cruise Talk Central and Mr Papa's World
Offline
I can install that module using EasyApache.
Here is the segment of the config file that I modified in bold:
/**
* For developers: WordPress debugging mode.
*
* Change this to true to enable the display of notices during development.
* It is strongly recommended that plugin and theme developers use WP_DEBUG
* in their development environments.
*
* For information on other constants that can be used for debugging,
* visit the Codex.
*
* @link https://codex.wordpress.org/De....._WordPress
*/
define('WP_DEBUG', true);/* That's all, stop editing! Happy blogging. */
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
Offline
@mr-papa - I am guessing that the debug put up the message but whatever is actually causing the error then stopped with a fatal error and then the white page. Although the mysqli error would then stop display with a headers sent condition.
This is going to need the error log I think.
|
YELLOW
SWORDFISH
|
Offline
I am still running into these error issues. I created a phpinfo file and I can't seem to locate any missing add-ons that would be prompting these errors.
Could you guys please take a look and confirm my findings?
Offline
Off-hand I can see two libraries that your php does not contain,. One is the mysqli library and the other is mbstring. Both WordPress and Simple:Press use both of these libs. WordPress does appear to check for the existence of mysqli and it use to check for mbstring as well but is starting not to now as it seems rare not to have it included.
Are you able to get you php recompiled with these two libs?
|
YELLOW
SWORDFISH
|
All RSS1 Guest(s)