I have installed a version of Cometchat Nulled on my web site. I got this messages in my chatrooms window. Besides, I don't use any CMS, my pages are HTML files.
Image:
As I indicated in the comments, your chat script is outputting a warning because:
there is a problem it wants you to know about
PHP's settings in your installation (specifically display_errors) require it to render the issue on-screen
This warning is telling you that this script is using an old database library. It is possible there is a setting to swap to a newer database library such as PDO - please do look into it. Presently you cannot use PHP7 at all because of this problem, even though your host offers it.
The solution here was to edit this configuration setting in your config.php:
define('DEV_MODE','0'); // Set to 1 only during development
I swapped the 1 to a 0 and this must have reset the display_errors setting for us within the script itself.
Related
I've got a CakePHP 1.2-based web site (I know.. too ancient) that I need to upgrade only to whatever is the oldest Cake to support PHP 7.1 (I think roughly Cake 2.8, from what I've seen so far), because my host is upgrading PHP to 7.1 across the board. This site only needs to live maybe 1 more year before we totally replace it, but we don't have time to do that before the host upgrades PHP at end of year.
I am trying to get the web site as-is running in a vagrant VM, so I can go through the upgrade steps there, carefully, and understand exactly what I need to do. My problem now is that I can't get the site to display. More concretely, when I try to load the site with nginx in vagrant, I get nothing but a blank screen with a few PHP warnings (strict standards to the effect of Non-static method Configure::read() should not be called statically), but nothing obviously broken. There's basically nothing in the PHP log, and nothing in the Nginx log. Again, this is the site as currently running (successfully) in production, which means my vagrant PHP is 5.6.38 (the actual production PHP is 5.6.25). Running with php-fpm.
Cake's own logs are only reporting the following, which arises inside a controller method function disableCache(), which is trying to insert headers to prevent the browser from caching the request:
2018-10-22 15:18:57 Warning: Warning (2): Cannot modify header information - headers already sent by (output started at /usr/share/nginx/html/www.mydomain.com/cake/libs/object.php:63) in [CORE/cake/libs/controller/controller.php, line 844]
I have inserted an early return in that method just to stop these warnings.
In PHP, I've got these settings:
error_reporting(E_ALL^E_DEPRECATED);
ini_set('display_errors', 1);
ini_set('error_log', '/var/log/php_errors.log');
In Cake 1.2's app/config/core.php, I've got:
Configure::write('debug', 3);
Database is local MySQL in vagrant, with settings in app/config/database.yml.
Can someone suggest where I should go next in debugging this?
From my own experience, PHP 7.1 and CakePHP 1.2 can work together. You simply need to upgrade your source code to make it compatible with PHP 7.1 but you can continue to have your system in CakePHP 1.2 without having to upgrade CakePHP. Of course, if you can use a newer or the latest version of CakePHP that would be perfect but think of it as a separate project and not something you must do now only because your host is upgrading PHP to 7.1 across the board.
If you can get your Cake project upgraded to 1.3.21 (the last 1.x release), you may be able to use this: https://github.com/littleant/cakephp-1.3.21 instead of upgrading to Cake 2.x. Might buy you a little time!
We are running a private MediaWiki server used at our workspace for internal documentation. We recently installed the VisualEditor extension, along with the prerequisite Parsoid (v0.8.0) service and Stunnel (as our wiki is served through HTTPS). However, we are having the issue where the "Edit" tab for the visual editor will appear when a page is loaded, then suddenly disappear after about half a second.
We double checked that the extension settings in LocalSettings.php were properly set to automatically enable the VisualEditor interface, and make it default.
We first looked at the error logs for MediaWiki, as well as Parsoid, and there is nothing out of the ordinary. We made sure that the wiki API was available, and that Parsoid could reach it, and was working. We have also looked at the debug console in the browser for error messages, which was also silent as to the nature of the issue. We have tried all of the listed troubleshooting steps on both the Parsoid and VisualEditor pages, and all of the checks point to the service running without error.
When we inspected the source for the page, we noticed that the html tag had been assigned the class type "ve-not-available", which made us think that the extension was potentially loading (at least enough to assign this class), but that something was preventing it from working properly. It's just that something has left zero footprint in any logs or files that we can find.
We would like to know where to look next to potentially help diagnose the problem.
If I recall correctly, this issue has something to do with the Visual Editor not recognizing the current skin being compatible. Are you using a custom skin?
If so, try adding the following to your LocalSettings.php;
$wgVisualEditorSupportedSkins = ['MySkin'];
I'm trying to run a copy of a joomla site (that works perfectly on the hosting) but, when I put all its files on my directory and install its BD just works administrator site but the site itself keeps in white screen.
I update its configuration file (configuration.php) exactly:
-DB
User
Password
Host
DB & DB prefix no changes needed
-Logs
log_path = 'C:\wamp\www\sitename\logs'
tmp_path = 'C:\wamp\www\sitename\tmp';
I don't know what to do, I don't understand (I'm new with Joomla)
Joomla version: 3.5.1
PHP: 7.0
A white screen usually is a sign of a server error of any kind. A first step to identify the underlying problem is to enable the debug mode and set the error reporting to development. You should then get an error message instead of the white screen.
In general, it is a good idea to use a tool like Akeeba Backup to transfer sites. It takes care of some environmental differences between the production server and localhost. You can even utilise another database management system.
Its not much complicated.. As you said you have already configure DB, Prefix, Host and Password.
So verify it again and suggest to check your localhost PHP version and online PHP version. Its create problem if your PHP version and live PHP version are different.
And make sure the PHP libraries you used on live site, these all need to install on your local PC too.
and make error_reporting maximun to check exact error and tell me error you get.
Please do this and if still you have issue than please wirte comment me, we will find more about your issue.
Thank You.
I am not so into PHP and I have the following problem.
I reinstalled an old Joomla website (it is an old version of the CMS that I have to upgrade) on my local server (XAMPP).
The problem is that now I obtain some warning message like this into the pages:
Strict Standards: Only variables should be assigned by reference in C:\xampp\htdocs\erusma\plugins\content\embed_google_docs_viewer\embed_google_docs_viewer.php on line 61
The website works fine but somewhere I have these warning. I think that maybe is something related to the PHP log settings or something like this.
What can I do to avoid these links? (I can't change the code)
Here are a few options (listed in increasing level of difficulty):
Ignore the warning messages as they are likely doing no harm especially on local host.
Suppress the warning messages via the appropriate option in Joomla Global Configuration and/or directives in php.ini or .htaccess files.
Downgrade PHP to an earlier version.
Upgrade Joomla / third party extensions to later versions.
Fix the code.
My php code is in the hostgator server and since I have to write a few scripts I don't have to install the wamp/lamp server.
I did a bit digging and found extensions namely PHP console. I added it and tested once, it showed me the line number of the errror.
But after a few hours when I tested the extension it is not working anymore for the same script and the same error.
I also tried another popular extension called Xdebug helper. But that also seems to be not working.
To test I have removed a semicolon in my working script and the link is : http://arqamahmad.com/music_app/getmusic.php
PS : I am using a shared hostgator server and I have done my research on the .htaccess and php.ini files. Nothing is helpful. The PHP console extension was the best but there seems to be some problem to that.
Answer : I had to add a php.ini file inside public_http making allowing the php debug mode on then only it the extensions work.
For Firefox, there is FirePHP (http://www.firephp.org/) in combination with Firebug. There is a similar extension for Chrome, but I haven’t tested that (https://github.com/itsgoingd/clockwork-chrome).
The general thing is that you need to somehow transfer your error messages from PHP back to the client. If you don’t want to use a browser extension for that, you can also use an approach chosen by many frameworks (e.g. Symfony): add an admin module in your page, where the error messages are displayed (you need to intercept errors on the servers for that, by registering a custom error handler).
Edit: This of course requires PHP to output error messages at all, which depends on (among others) the php.ini settings like error_reporting, which need to be set to a level that the errors you desire for reporting will trigger the error handler functions.
Concerning your remark about Xdebug: to use Xdebug helper, Xdebug (a PHP extension for debugging) needs to be available on the server, which it usually is not on production systems.
Since php is executed on the server side, no browser add-on will help you. You need to add a few lines of code to the php file to show the errors.
Here's a link for you: https://stackoverflow.com/a/21429652/6735510