Display Log Files [Support Thread] (v1.5.1-to-v1.5.6)

[lat9]

I have added the debug-file file-size to the listing of the debug file. I find this very handy in finding potentially the same errors. If anyone else is interested, I will upload this "upgraded version"

Sounds great, Design75!

[Design75]

BTW here is a screen-shot

[picandnix]

I have added the debug-file file-size to the listing of the debug file. I find this very handy in finding potentially the same errors. If anyone else is interested, I will upload this "upgraded version"

great addition!

[Design75]

The update has been submitted. There are only three lines of code added to "/YOUR_ADMIN/display_logs.php". They are clearly marked with a comment.

[twi]

zc1.51
display log files v1.02

has anyone encounter this problem? The display log files heading displays "TABLE_HEADING_FILESIZE" instead of "Files Size" word. I know this is labeling problem but I don't know how to fix it. Can anyne help me?

[DrByte]

That's a classic symptom of a corresponding language file being missing from the server.

[twi]

where do I look for this file?

[DrByte]

Here's what I would do:

Based on how 99% of plugins are prepared (ie: matching the ZC folder structure pattern), there is a main module file in the /admin/ folder, and there is a corresponding language file in the /admin/includes/languages/english/ folder. So that's the first place to look.

Or, just as with any plugin that doesn't work correctly for some unexplained reason, I'd start by looking at the files that come with the plugin and make sure I've got them on my server.

And, if I've recently installed an update to a plugin, maybe I missed installing updated versions of *all* the files that come with that plugin.


Or, maybe the plugin author made a mistake and left out a necessary constant/define when they put together their latest update. You can help them become aware of the specific problem by investigating to find whether the TABLE_HEADING_FILESIZE constant is missing from the language file. You can do that by looking at the file itself. Perhaps it's there but maybe they misspelled it? Or you might find it using the Developers Toolkit ... and that would reveal if it's "there" but maybe you uploaded it to someplace other than where it belongs.

[lat9]

Or, maybe the plugin author made a mistake and left out a necessary constant/define when they put together their latest update.

Exactly! The last update was missing that define. You'll need to edit /YOUR_ADMIN/includes/languages/english/display_logs.php and add the line that I've highlighted in red:

define('TABLE_HEADING_FILENAME', 'File Name');
define('TABLE_HEADING_MODIFIED', 'Date Modified');
define('TABLE_HEADING_FILESIZE', 'File Size (bytes)');  /*v1.0.3a*/
define('TABLE_HEADING_DELETE', 'Delete?');
define('TABLE_HEADING_ACTION', 'Action');

[twi]

Here's what I would do:

Based on how 99% of plugins are prepared (ie: matching the ZC folder structure pattern), there is a main module file in the /admin/ folder, and there is a corresponding language file in the /admin/includes/languages/english/ folder. So that's the first place to look.

Or, just as with any plugin that doesn't work correctly for some unexplained reason, I'd start by looking at the files that come with the plugin and make sure I've got them on my server.

And, if I've recently installed an update to a plugin, maybe I missed installing updated versions of *all* the files that come with that plugin.


Or, maybe the plugin author made a mistake and left out a necessary constant/define when they put together their latest update. You can help them become aware of the specific problem by investigating to find whether the TABLE_HEADING_FILESIZE constant is missing from the language file. You can do that by looking at the file itself. Perhaps it's there but maybe they misspelled it? Or you might find it using the Developers Toolkit ... and that would reveal if it's "there" but maybe you uploaded it to someplace other than where it belongs.

I will do that Dr Byte and report back if I find the error and able to fix it. If not I will report back too. Thanks so much.