Left Sidebar Absent After Upgrade to 4.2

drlong wrote on Friday, January 02, 2015:

I have just attempted to upgrade from 4.1.2(7) to 4.2.

However, when loading the upgraded version, the left sidebar does not load.

Anyone have a solution for this? I have reverted back to the previous version.

drlong wrote on Friday, January 02, 2015:

I’ve attached an image of what I mean. Thanks

fsgl wrote on Friday, January 02, 2015:

Found this thread.

I remember from other threads that blank space = permission problems.

Suggest:

  1. Back up again.
  2. Follow this Guide to the letter (I should know, from bitter experience).
  3. Log into your Windows 7 laptop as Adminstrator to avoid permission problems.
  4. In step 1 of the Guide, be certain to move 4.1.2 to a place other than C-drive, e.g., an external hard drive. If you leave it on C-drive, 4.2.0 will not copy over 4.1.2.
  5. at http://localhost/openemr/sql_upgrade.php, 4.1.2 should be the default in the drop down menu. If not, re-do step 4 from above.

drlong wrote on Monday, January 05, 2015:

Good Morning fsgl,

Thank you for your quick response.

Unfortunately this has not solved my problem. I have followed the guide exactly, and for some reason the menu sidebar remains blank. Interestingly, it does not provide an error message, just a blank space.

I have successfully upgraded many times over the past few years and have never encountered this. When I roll back to the previous version and run the sql_upgrade.php I have no issue.

I am curious if it is a compatibility issue with XAMPP, as I am running the version that installed when I first started with OpenEMR many years ago.

Could this be the case? Or is there something else I am missing?

Thanks again for the excellent support!

drlong wrote on Monday, January 05, 2015:

Also, I have always been curious as to what point #4 from the upgrade guide actually means:

  1. Record the openemr/sites/default/sqlconf.php file variables from your old 4.1.2 version, and type these into the openemr/sites/default/sqlconf.php file in new openemr version.

Which variables in the sqlconf.php are required? I’ve always just copied and pasted my old sqlconf.php file and never had an issue.

Perhaps this is my problem?

I feel like such a hack when I’m working with OpenEMR. I have no clue what anything means, and just follow the instruction like a recipe. Is there anyone in Canada who is fluent in this program that is available for hire to properly maintain OpenEMR systems??

teryhill wrote on Monday, January 05, 2015:

What is your operating system?

Thanks
Terry

cmswest wrote on Monday, January 05, 2015:

it’s looking for the mysql specifics, something like this:

$host = ‘localhost’;
$port = ‘3306’;
$login = ‘openemr’;
$pass = ‘pass’;
$dbase = ‘openemr’;

drlong wrote on Monday, January 05, 2015:

Windows 7 Professional

fsgl wrote on Monday, January 05, 2015:

Try not to despair.

Stephen & Terry are excellent developers. If we are unable to walk you through this problem, there is always the option of joining their respective client list.

With patience you will learn the rationale & purpose of what you are doing. For now we must take the “cookbook” approach. If you can follow instructions to the the letter, you are far ahead of many users.

What version of XAMPP are you on? If you don’t know, what version of OpenEMR was it packaged with?

Regarding the sql.conf.php, it’s the login credentials to your MySQL database. The upgrade need them to “talk” to your database.

Let’s try to get the fatal error messages so that we can get a sense of what’s gone wrong (differential diagnoses).

Suggestion:

  1. Backup yet again.
  2. repeat steps 2-5 from above.
  3. log in, note the time & immediately go to C-drive\xampp\php\logs\php_error_log & note errors.
  4. go to xampp\mysql\data\mysql.error & note errors for the time in 3.
  5. post errors logs as attachments so that we can take a look.

drlong wrote on Monday, January 05, 2015:

I am using XAMPP 1.7.1. I believe it was packaged with version 4.0.0. I have tried to upgrade XAMPP a few times in the past to no avail.

For some reason, the file “c:\xampp\php\logs\php_error_log” does not exist for me. My install does not contain a ‘logs’ folder within the ‘php’ folder. I found “C:\xampp\php\PEAR\Log\error_log” but it does not contain any pertinent error messages. Is there somewhere else to look for fatal errors (besides in the mirror…haha)?

Working diagnosis: problem exists between keyboard and chair.

teryhill wrote on Monday, January 05, 2015:

When you tried to upgrade the XAMPP did you use the .exe upgrade file?
Thanks
Terry
From: mlong drlong@users.sf.net
To: [openemr:discussion] 202505@discussion.openemr.p.re.sf.net
Sent: Monday, January 5, 2015 3:53 PM
Subject: [openemr:discussion] Left Sidebar Absent After Upgrade to 4.2

I am using XAMPP 1.7.1. I believe it was packaged with version 4.0.0. I have tried to upgrade XAMPP a few times in the past to no avail.

For some reason, the file “c:\xampp\php\logs\php_error_log” does not exist for me. My install does not contain a ‘logs’ folder within the ‘php’ folder. I found “C:\xampp\php\PEAR\Log\error_log” but it does not contain any pertinent error messages. Is there somewhere else to look for fatal errors (besides in the mirror…haha)?

Working diagnosis: problem exists between keyboard and chair.


Left Sidebar Absent After Upgrade to 4.2


Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/openemr/discussion/202505/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

fsgl wrote on Monday, January 05, 2015:

Good to see that you are able to laugh.

We’re going change tactics. Because XAMPP is outdated, let’s update both by installing the 4.2.0 XAMPP Package.

It’s easier if we break this task down into bite sized pieces.

We need to transfer data from the xampp/htdocs/openmer folder & the database before we can install the package.

Firstly, backup to another drive.
Second, copy the xampp/htdocs/openemr folder to another drive.

The third task will involve the use of Command Prompt. To this day, it still makes me a bit queasy, but it is the method least likely to give errors while copying the database.

You will need the MySQL rootpassword, found in C:\xampp\security\security\mysqlrootpassword.txt if you don’t have it written down.

Third task:

  1. Use this link to open Command Prompt.
  2. Copy the two commands & paste in Command Prompt (see attachment 1) & hit Enter:

CD C:\

C:\xampp\mysql\bin\mysqldump -u root -prootpassword openemr > dumpfile.sql

Remember to insert the rootpassword, allowing no space after the p. The dumpfile should appear in C-drive. It will take time to create this .sql file if you have a large database.

fsgl wrote on Monday, January 05, 2015:

Fourth task will be to get rid of the old OpenEMR Xampp package.

  1. Go to xampp->xampp control & click the stop buttons for both Apache & MySQL. Deletion will not be possible without first stopping the 2 services.
  2. Click the Quit button to get out of xampp control.
  3. Right click on the xampp folder to delete it. See screenshot. This will take time to complete.

The entire xampp folder should disappear from C-drive tree upon completion.

Fifth task involves the install of the new package.

fsgl wrote on Monday, January 05, 2015:

Sixth task would import your default folder & database into the new package.

  1. Copy old xampp\htdocs\openemr\sites\default folder replacing the new default folder. Right click the default in the other drive to copy it. Right click the new sites folder & choose paste. Say yes to copy & replace.
  2. Import the old database via Command Prompt with the dumpfile in C-drive into the new database with these 2 commands:

CD C:\

C:\xampp\mysql\bin\mysql -u root -p openemr < dumpfile.sql

Again copy & paste commands as demonstrated earlier & hit Enter.

The new database does not have a rootpassword yet, hence there is nothing after the p.

You will be setting the rootpassword in the 8th task, below.


Edit Jan. 9, 2015

Instead of importing the entire old default folder, copy only the following to the new default folder:

openemr/sites/default/documents 
openemr/sites/default/edi 
openemr/sites/default/era 
openemr/sites/default/letter_templates

blankev wrote on Monday, January 05, 2015:

Need to remove Apache form the Services in Windows. Only removing Xampp is not enough.

This is something do-able, but need to find the different steps under remove Apache as a Service somewhere on the net.

fsgl wrote on Monday, January 05, 2015:

Seventh task is to upgrade (which is from 4.0.0 to 4.2.0) the database. You should be able to do this with your eyes closed. If not, we will help.

Steps 1 though 5 have been completed with the above tasks.

Just do steps 6 (upgrading from 4.0.0 or whichever version you are on) & 7.

Eighth task is housekeeping chores.

  1. Set the time zone as described here. Because Apache & MySQl have not been started, there is no need to stop them before setting time zone.
  2. Start both services.
  3. At a minimum, set up the Security Console.
  4. Secure OpenEMR.
  5. At login check that you have version 4.2.0. See 2.

Edit Jan. 9, 2015

See this for MU2 instructions.

drlong wrote on Tuesday, January 06, 2015:

I’m not exaggerating when I say this is the most outstanding forum support I’ve ever received. I will follow your guidance tomorrow in office and report back. Thanks again, this is amazing!

drlong wrote on Tuesday, January 06, 2015:

Thank-you, thank-you fsgl!

Your guide worked perfectly.

The only issue I have encountered in your guide is that sqlconf.php from the fresh install cannot be replaced by the sqlconf.php from the old install. Namely, the password variable must remain ‘escargot’ as it is listed by default, and not be replaced by my previous password.

When I replace with the old sqlconf.php variables it provides the error message “Check that mysqld is running.” Reverting back appears to work, and I am assuming this should not have any negative effect?

Thanks again. The support I’ve received in this thread goes above and beyond.

fsgl wrote on Tuesday, January 06, 2015:

Don’t be concerned about the database credentials. The error message does not make sense; but if it works, it’s good; be it sense or nonsense.

So very pleased that you mastered the command line (Command Prompt) on your very first try. Wow!

We look forward to your return visits to the Fora to help new members. Who knows, you may acquire a GitHub account before I do.

aethelwulffe wrote on Wednesday, January 07, 2015:

BTW, real good job on getting upgraded to the new xampp package. You will find you like some things a good bit better. The database (via phpmyadmin) might look a little different when listing tables (does ‘pages’) and the bookmarked queries you had will no longer be available (but they still exist).
Having your system upgraded to the new (er) PHP is a very good thing.