Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Haw can I get rid this message?


Mookie_Jam

Recommended Posts

Warning: session_write_close(): Your script possibly relies on a session side-effect which existed until PHP 4.2.3. Please be advised that the session extension does not consider global variables as a source of data, unless register_globals is enabled. You can disable this functionality and this warning by setting session.bug_compat_42 or session.bug_compat_warn to off, respectively. in /home/httpd/vhosts/lacamelia.com/httpdocs/includes/functions/sessions.php on line 197

 

I don't know php, but it seems easy to quit... I tryied following the instrucci?n, but didn't get it...

 

Could you explain me what to do?

 

Thanks!!

Link to comment
Share on other sites

Nobody else had this problem?? :blink:

It's not a very common one.

 

What version of php is the server running?

 

Did you get osC running without installing the register globals patches?

Local: Mac OS X 10.5.8 - Apache 2.2/php 5.3.0/MySQL 5.4.10 • Web Servers: Linux

Tools: BBEdit, Coda, Versions (Subversion), Sequel Pro (db management)

Link to comment
Share on other sites

4.3.2 is a big no no, full of holes, get that fixed first, else your site is going to get hacked by some of the works

Thats going to be difficult... My host company is not as cooperative as I would wish...

 

Which version of PHP do you recomend me?

 

 

Thanks!!

Link to comment
Share on other sites

Thats going to be difficult... My host company is not as cooperative as I would wish...

 

Which version of PHP do you recomend me?

Thanks!!

 

Move hosting companies

Link to comment
Share on other sites

Move hosting companies

 

 

Hi

 

I'm getting the same "session.bug_compat_42" error.

 

I'm running PHP 4.4.1, Apache 1.3.34 on Unix, MySQL 4.0.25-standard.

 

Any reasons as to why its botched?

 

Full error message: "Fatal error: Cannot redeclare tep_db_connect() (previously declared in /home/public_html/shop/admin/includes/functions/database.php:13) in /home/public_html/shop/admin/includes/functions/database.php on line 13

 

Warning: Unknown(): Your script possibly relies on a session side-effect which existed until PHP 4.2.3. Please be advised that the session extension does not consider global variables as a source of data, unless register_globals is enabled. You can disable this functionality and this warning by setting session.bug_compat_42 or session.bug_compat_warn to off, respectively. in Unknown on line 0"

 

Craig

... Too close for missiles, I'm switching to guns ...

Link to comment
Share on other sites

Hi

 

I'm getting the same "session.bug_compat_42" error.

 

I'm running PHP 4.4.1, Apache 1.3.34 on Unix, MySQL 4.0.25-standard.

 

Any reasons as to why its botched?

 

Full error message: "Fatal error: Cannot redeclare tep_db_connect() (previously declared in /home/public_html/shop/admin/includes/functions/database.php:13) in /home/public_html/shop/admin/includes/functions/database.php on line 13

 

Warning: Unknown(): Your script possibly relies on a session side-effect which existed until PHP 4.2.3. Please be advised that the session extension does not consider global variables as a source of data, unless register_globals is enabled. You can disable this functionality and this warning by setting session.bug_compat_42 or session.bug_compat_warn to off, respectively. in Unknown on line 0"

 

Craig

 

The fact that you are running an insecure version of PHP should be more of an issue, if you are on a shared hosted box and your hosting company will not upgrade your PHP to remove the threat then you are doing your customers a dis-service and also risking your own business (legal threat)

 

So rather upgrade PHP to stop the error than hid the error.

Link to comment
Share on other sites

The fact that you are running an insecure version of PHP should be more of an issue, if you are on a shared hosted box and your hosting company will not upgrade your PHP to remove the threat then you are doing your customers a dis-service and also risking your own business (legal threat)

 

So rather upgrade PHP to stop the error than hid the error.

 

 

I'm using Version 4.4.1 of PHP, is this secure enough?

 

Not wishing to hide the error, as that throws up other issues along the line.

 

Craig

... Too close for missiles, I'm switching to guns ...

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...