Blank Page

Discussion forum about Anuko Time Tracker
Post Reply
j552
Posts: 6
Joined: Wed Mar 27, 2019 3:02 am

Blank Page

Post by j552 » Wed Mar 27, 2019 3:15 am

Thanks for reading.

I installed the latest stable version as of 03/26/2019.

The issue I'm having is that once I login, it is a blank page.

When I go to the timetracker root at mysite.com/, it goes to /time.php?date=2019-03-26 with a blank page.

When I go to /login.php, it pulls up the login page.
Entering in invalid passwords gives the proper ("Incorrect login or password.") error.

I can access /password_reset.php. It sends the reset link when I enter a login that has an email address associated with it.

The dbinstall.php page produced the error "Error: WEB-INF/config.php file does not start with PHP opening tag."
I was able to create the db tables without a problem. There were no errors. Accessing the page now still produces the error, but I have not pressed anything, since there is no reason to at this point. I renamed it back to .bak again for now.

templates_c is all 777, although I see that new file entries coming into it are 644.

I have not been able to get to anything besides login and reset so far.

This is a new install.


time tracker tables on phpmyadmin:
tt_clients
tt_client_project_binds
tt_config
tt_cron
tt_custom_fields
tt_custom_field_log
tt_custom_field_options
tt_expense_items
tt_fav_reports
tt_files
tt_groups
tt_invoices
tt_log
tt_monthly_quotas
tt_predefined_expenses
tt_projects
tt_project_task_binds
tt_roles
tt_site_config
tt_tasks
tt_templates
tt_timesheets
tt_tmp_refs
tt_users
tt_user_project_binds
Last edited by j552 on Wed Mar 27, 2019 3:43 pm, edited 4 times in total.

Nik
Posts: 474
Joined: Wed May 26, 2010 5:55 pm

Re: Blank Page

Post by Nik » Wed Mar 27, 2019 2:47 pm

Latest version is 1.18.61.4886, you can see it on the footer of the login.php page.

What does your web server error log say when a blank page occurs?

j552
Posts: 6
Joined: Wed Mar 27, 2019 3:02 am

Re: Blank Page

Post by j552 » Wed Mar 27, 2019 3:35 pm

It's V. 1.18.61.4886. I downloaded it yesterday.

I don't think error logs were enabled. I think I added the appropriate code to my .user.ini to make that happen, but it might take a while to produce a log if I did it correctly.

Thanks for the help so far.

j552
Posts: 6
Joined: Wed Mar 27, 2019 3:02 am

Re: Blank Page

Post by j552 » Fri Mar 29, 2019 5:54 am

I don't think I've figured it out yet. It doesn't help that I'm on shared hosting. For something else I needed was able to get some other software on after the first one needed something I couldn't figure out. It's challenging. It seems like I'm so close with time tracker... :-(

admin
Posts: 554
Joined: Fri Oct 08, 2004 9:46 pm
Location: Vancouver, Canada
Contact:

Re: Blank Page

Post by admin » Sun Mar 31, 2019 1:05 pm

j552 wrote:
Fri Mar 29, 2019 5:54 am
I don't think I've figured it out yet. It doesn't help that I'm on shared hosting. For something else I needed was able to get some other software on after the first one needed something I couldn't figure out. It's challenging. It seems like I'm so close with time tracker... :-(
Some shared hosting have peculiar requirements to directory and file permissions, for example, they may not like a group write on files (664) and require 644 instead, or directories (755, instead of 775). Access to logs would help to determine what exactly is going on.

If logs are not available I would try to debug by inserting these statements temporarily into various pages, to see if execution reaches them (message is printed on screen and the program exists).

Code: Select all

die("some message");
For example, it looks like a redirect occurs successfully to time.php - as designed, so you can start from the beginning in this file (time.php) and determine at which point exactly the problem occurs. Once you know the precise location of the problem, look closely to the code that causes it, it should get you enough information to troubleshoot further.

It is much easier to order a support incident and provide us with temporary remote access to see if we can figure out what is going on.

j552
Posts: 6
Joined: Wed Mar 27, 2019 3:02 am

Re: Blank Page

Post by j552 » Thu Apr 11, 2019 8:27 pm

admin wrote:
Sun Mar 31, 2019 1:05 pm


If logs are not available I would try to debug by inserting these statements temporarily into various pages, to see if execution reaches them (message is printed on screen and the program exists).

Code: Select all

die("some message");
Thank you for all your help.

Ok, so I got the logging to work*, but there is nothing in the log yet. Putting the php code in the login and time .php files gave me either the message or a blank page depending on where I put it.

*How do you know it works? WordPress has a error log plugin that will not show you that it's working if the error logging is not configured properly.

EDIT: logs below. There are SSL things I know how to fix that have nothing to to with timecard, but I will work on them in the near future. I was having the problems before SSL was added.

Code: Select all

[11-Apr-2019 20:53:11 UTC] ** Detecting configuration **
[11-Apr-2019 20:53:11 UTC] plugin version: 3.1.5
[11-Apr-2019 20:53:11 UTC] Already on SSL, start detecting configuration
[11-Apr-2019 20:53:11 UTC] SSL type: LOADBALANCER
[11-Apr-2019 20:53:11 UTC] ** Configuring SSL **
[11-Apr-2019 20:53:11 UTC] testing htaccess rules...
[11-Apr-2019 20:53:11 UTC] test page url, enter in browser to check manually: ***REDACTED***
[11-Apr-2019 20:53:11 UTC] htaccess rules tested successfully.
[11-Apr-2019 20:53:11 UTC] checking if .htaccess can or should be edited...
[11-Apr-2019 20:53:11 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 20:53:11 UTC] retrieving redirect rules
[11-Apr-2019 20:53:11 UTC] converting siteurl and homeurl to https
[11-Apr-2019 20:53:17 UTC] ** Detecting configuration **
[11-Apr-2019 20:53:17 UTC] plugin version: 3.1.5
[11-Apr-2019 20:53:17 UTC] Already on SSL, start detecting configuration
[11-Apr-2019 20:53:17 UTC] SSL type: LOADBALANCER
[11-Apr-2019 20:53:17 UTC] ** Configuring SSL **
[11-Apr-2019 20:53:17 UTC] testing htaccess rules...
[11-Apr-2019 20:53:17 UTC] test page url, enter in browser to check manually: ***REDACTED***
[11-Apr-2019 20:53:17 UTC] htaccess rules tested successfully.
[11-Apr-2019 20:53:17 UTC] checking if .htaccess can or should be edited...
[11-Apr-2019 20:53:17 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 20:53:17 UTC] retrieving redirect rules
[11-Apr-2019 20:53:17 UTC] converting siteurl and homeurl to https
[11-Apr-2019 20:53:17 UTC] retrieving redirect rules
[11-Apr-2019 20:53:23 UTC] ** Detecting configuration **
[11-Apr-2019 20:53:23 UTC] plugin version: 3.1.5
[11-Apr-2019 20:53:23 UTC] Already on SSL, start detecting configuration
[11-Apr-2019 20:53:23 UTC] SSL type: LOADBALANCER
[11-Apr-2019 20:53:23 UTC] ** Configuring SSL **
[11-Apr-2019 20:53:23 UTC] testing htaccess rules...
[11-Apr-2019 20:53:23 UTC] test page url, enter in browser to check manually: ***REDACTED***
[11-Apr-2019 20:53:23 UTC] htaccess rules tested successfully.
[11-Apr-2019 20:53:23 UTC] checking if .htaccess can or should be edited...
[11-Apr-2019 20:53:23 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 20:53:23 UTC] retrieving redirect rules
[11-Apr-2019 20:53:23 UTC] converting siteurl and homeurl to https
[11-Apr-2019 20:53:24 UTC] Mixed content fixer was successfully detected on the front end.
[11-Apr-2019 20:53:24 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 20:53:24 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 21:08:50 UTC] ** Detecting configuration **
[11-Apr-2019 21:08:50 UTC] plugin version: 3.1.5
[11-Apr-2019 21:08:50 UTC] Already on SSL, start detecting configuration
[11-Apr-2019 21:08:50 UTC] Opening testpage to check server configuration: ***REDACTED***
[11-Apr-2019 21:08:52 UTC] test page url, enter in browser to check manually: ***REDACTED***
[11-Apr-2019 21:08:52 UTC] Could not open testpage 
[11-Apr-2019 21:08:52 UTC] SSL type: LOADBALANCER
[11-Apr-2019 21:08:52 UTC] ** Configuring SSL **
[11-Apr-2019 21:08:52 UTC] testing htaccess rules...
[11-Apr-2019 21:08:52 UTC] test page url, enter in browser to check manually: ***REDACTED***
[11-Apr-2019 21:08:52 UTC] htaccess rules tested successfully.
[11-Apr-2019 21:08:52 UTC] checking if .htaccess can or should be edited...
[11-Apr-2019 21:08:52 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 21:08:52 UTC] retrieving redirect rules
[11-Apr-2019 21:08:52 UTC] converting siteurl and homeurl to https
[11-Apr-2019 21:08:52 UTC] Mixed content fixer was successfully detected on the front end.
[11-Apr-2019 21:08:52 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 21:08:52 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 21:13:41 UTC] ** Detecting configuration **
[11-Apr-2019 21:13:41 UTC] plugin version: 3.1.5
[11-Apr-2019 21:13:41 UTC] Already on SSL, start detecting configuration
[11-Apr-2019 21:13:41 UTC] SSL type: LOADBALANCER
[11-Apr-2019 21:13:41 UTC] ** Configuring SSL **
[11-Apr-2019 21:13:41 UTC] testing htaccess rules...
[11-Apr-2019 21:13:41 UTC] test page url, enter in browser to check manually: ***REDACTED***
[11-Apr-2019 21:13:41 UTC] htaccess rules tested successfully.
[11-Apr-2019 21:13:41 UTC] checking if .htaccess can or should be edited...
[11-Apr-2019 21:13:41 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 21:13:41 UTC] retrieving redirect rules
[11-Apr-2019 21:13:41 UTC] converting siteurl and homeurl to https
[11-Apr-2019 21:13:41 UTC] Mixed content fixer was successfully detected on the front end.
[11-Apr-2019 21:13:41 UTC] .htaccess does not contain default Really Simple SSL redirect
[11-Apr-2019 21:13:41 UTC] .htaccess does not contain default Really Simple SSL redirect

Nik
Posts: 474
Joined: Wed May 26, 2010 5:55 pm

Re: Blank Page

Post by Nik » Mon Apr 15, 2019 2:15 pm

I added some debug trace in version 1.18.65.4942.

Try installing it. Then, in your config.php, make sure that DEBUG constant is defined as true.

Code: Select all

define('DEBUG', true);
Then try accessing the time.php page. You should see some diagnostics messages printed on screen. Example of expected output is attached.
Attachments
time_tracker_debug_trace_example.png
time_tracker_debug_trace_example.png (69.4 KiB) Viewed 352 times

j552
Posts: 6
Joined: Wed Mar 27, 2019 3:02 am

Re: Blank Page

Post by j552 » Mon Apr 15, 2019 11:26 pm

Nik wrote:
Mon Apr 15, 2019 2:15 pm
I added some debug trace in version 1.18.65.4942.

Try installing it. Then, in your config.php, make sure that DEBUG constant is defined as true.

Code: Select all

define('DEBUG', true);
Then try accessing the time.php page. You should see some diagnostics messages printed on screen. Example of expected output is attached.
time.php
blank except the following:
/home/content/***REDACTED***/52/42451252/html/timecard/time.php: page entry after imports

login.php (after successful login)
blank except the following:
array(2) { ["login"]=> string(5) "admin" ["id"]=> string(1) "1" }

my other login:
array(2) { ["login"]=> string(15) "***REDACTED***" ["id"]=> string(1) "2" }

Version on login page: 1.18.65.4945
Browsers: Chrome, IE, Edge

wrc
Posts: 273
Joined: Tue May 25, 2010 8:30 pm

Re: Blank Page

Post by wrc » Mon Apr 15, 2019 11:58 pm

I think your problem may be related to the "Error: WEB-INF/config.php file does not start with PHP opening tag." that you see in dbinstall.php.

What seems to be happening is that redirects (such as after a successful login) don't appear to work at all because config.php file format is wrong. Check the comment in the environment check, it says:

Code: Select all

    // Config file must start with the PHP opening tag. We are checking this because
    // a Unicode editor may insert a byte order mark (BOM) before it. This is not good as it will
    // spit white space before output in some situations such as in PDF reports.
Try using another editor and make sure that the config file does not start with any (hidden) garbage. Examine the file using hex editor to make sure there is nothing there. Once you resolve the "Error: WEB-INF/config.php file does not start with PHP opening tag." redirects should start working, I think.

j552
Posts: 6
Joined: Wed Mar 27, 2019 3:02 am

Re: Blank Page

Post by j552 » Tue Apr 16, 2019 12:25 am

wrc wrote:
Mon Apr 15, 2019 11:58 pm
I think your problem may be related to the "Error: WEB-INF/config.php file does not start with PHP opening tag." that you see in dbinstall.php.
I uploaded the hex edited (removed the garbage) config.php.

New dbinstall.php message:
Error: browser cookies are off.
WEB-INF/templates_c/ directory is writable.
WEB-INF/config.php file exists.
DSN is defined.
PHP version: 7.2.15, good enough.
mysqli PHP extension is loaded.
mbstring PHP extension is loaded.
gd PHP extension is loaded.
Connection to database successful.
There are 121 tables in database.
Database version is: 1.18.61.

It works now. I appreciate everyone's help!

Post Reply