Forums / General Questions / Test site a mess!

Test site a mess!

Locked

Started by peace_freak on 19 Sep 2006, 9:26 AM · Views: 1,401

Results 1 to 6 of 6
This thread is locked. New replies are disabled.
19 Sep 2006, 9:26 AM
#1
peace_freak avatar

peace_freak

Zen Follower

Join Date:
Apr 2006
Posts:
354
Plugin Contributions:
0

Test site a mess!

I currently have a live site using version 1.3.2 with two languages, English and Japanese, and would like to upgrade to version 1.3.5. As I would like it to remain online without any major hiccups, I have taken the advice of doing the upgrade on a test site first.

So I have copied my store to a new directory and set the permissions of configure.php... but the test site looks pretty bad... (so I guess that this was a good thing for me to do so I can fix things now so if I ever have to move it to another server in the future it will go smoothly...)

I think many of the problems I am having are related to the fact that I have not used relative URLs for some of the graphics and links etc. (I used the full http://...) so I have begun to work on fixing them...

But, the first problem are the following 3 error messages that occur in the header section of the opening page. I have no idea how to fix them:

Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /home/globalpe/public_html/storetestsite/includes/extra_datafiles/music_type_database_names.php:60) in /home/globalpe/public_html/storetestsite/includes/functions/sessions.php on line 199

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/globalpe/public_html/storetestsite/includes/extra_datafiles/music_type_database_names.php:60) in /home/globalpe/public_html/storetestsite/includes/functions/sessions.php on line 199

Warning: Cannot modify header information - headers already sent by (output started at /home/globalpe/public_html/storetestsite/includes/extra_datafiles/music_type_database_names.php:60) in /home/globalpe/public_html/storetestsite/includes/init_includes/init_templates.php on line 152

19 Sep 2006, 11:00 AM
#2
paulm avatar

paulm

Totally Zenned

Join Date:
Nov 2003
Posts:
1,878
Plugin Contributions:
5

Re: Test site a mess!

Did you make any changes to:
/storetestsite/includes/extra_datafiles/music_type_database_names.php
?

If not, you can try to reupload it, overwriting the music_type_database_names.php on the server with the same file from the 1.3.5 zip. And if you have modified it, you can look if there is a typo in the file for example (and/or post it here).

(edit: the "headers already sent" means that output has been sent to the browser by this file, this may be caused by typos, a damaged file, or by ill behaved editors adding extra spaces or newlines after the last ?>)

19 Sep 2006, 11:49 AM
#3
peace_freak avatar

peace_freak

Zen Follower

Join Date:
Apr 2006
Posts:
354
Plugin Contributions:
0

Re: Test site a mess!

Thanks Paulm,

Hadn’t touched that file, but just in case I uploaded a new copy from version 1.3.5 but still no change...

I should add that I have not done an upgrade to 1.3.5 on the test site yet. The test site still is at 1.3.2. I have only moved my original site to a new directory and am trying to get it to ‘work’ as it should in the new directory. Once I have got it working I will then ‘test’ upgrade it to 1.3.5.

Anyway, I guess there is an underlying problem with paths to the items in my store as I have found that whatever products or buttons (language flags) I click on in the TEST site, take me to the the related page in my ACTUAL live store... I know they should take me to the page in the test store, so no doubt, I need to modify some basic path criteria somewhere... I just don’t know where to do so...

I look forward to any advice anyone can offer...

19 Sep 2006, 12:47 PM
#4
paulm avatar

paulm

Totally Zenned

Join Date:
Nov 2003
Posts:
1,878
Plugin Contributions:
5

Re: Test site a mess!

Ah, the problem is with a file loaded before music_type_database_names.php is loaded then.

Maybe it's your config file(s)? Did you edit those to reflect your test directory and database settings?

(I"ll be off now for some time, so hopefully someone else will jump in to help if needed)

19 Sep 2006, 1:02 PM
#5
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,511
Plugin Contributions:
176

Re: Test site a mess!

paulm:

the "headers already sent" means that output has been sent to the browser by this file, this may be caused by typos, a damaged file, or by ill behaved editors adding extra spaces or newlines after the last ?>
Paul is right.

To clarify, the message says, in part:> /storetestsite/includes/extra_datafiles/music_type_database_names.php:60
The :60 indicates that on line 60 of the file, there is a blank line or space.
Use your text editor to remove that line or space, and re-upload the file.

And in case you're looking at the original one that came with Zen Cart, yes, it does contain a blank line. Delete the blank line and you'll be fine. The file has been corrected for a future release. Not all servers will see this as a problem, and is largely predicated on how your FTP program treats the file while uploading it.

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.

20 Sep 2006, 2:13 PM
#6
peace_freak avatar

peace_freak

Zen Follower

Join Date:
Apr 2006
Posts:
354
Plugin Contributions:
0

Re: Test site a mess!

Thanks Dr. Byte... Have now got it working and looking good... Will do some more checking... Once I am satisfied it is working well, I will test upgrading to 1.3.5...