Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Login.php page is blank


trevally

Recommended Posts

Tried to migrate my V2.3.2 store to another directory as well as updating to the latest version but it hasn't been as straight forward as I thought. (Am trying to duplicate my working site under another directory so I don't have to shut down the exiting site which is working fine but is still on V.2.3.2)

 

At this point the new duplicate site is at V 2.3.4 but you can't log in as a registered customer/user. You can see the products, add to cart but of course when you click on the checkout button, the login page simply states "Welcome, Please Sign In" but there is nothing on the page to enter your details into to get into your account.  

 

The basic steps I took as background was...

- Install V.2.3.4 on a new directory.

- Export the old database in V 2.3.2 and import into the new database created in V2.3.4 using phpMyAdmin.

- Ran 2 commands in phpMyAdmin under SQL (alter table customer_info to add password reset key + date dateline)

 

I just can't figure where to go from here to get the Login page to work. Any ideas?

Link to comment
Share on other sites

Could you display the errors?

 

try to insert into catalog/includes/application_top.php the next code

 

change

// load server configuration parameters
 

to

ini_set('display_error', 1);
// load server configuration parameters
What do you see?

 

Or blank screen is again try to read phh_errors.log to inform us about error messages.

:blink:
osCommerce based shop owner with minimal design and focused on background works. When the less is more.
Email managment with tracking pixel, package managment for shipping, stock management, warehouse managment with bar code reader, parcel shops management on 3000 pickup points without local store.

Link to comment
Share on other sites

Could you display the errors?

 

try to insert into catalog/includes/application_top.php the next code

 

change

// load server configuration parameters
 

to

ini_set('display_error', 1);
// load server configuration parameters
What do you see?

 

Or blank screen is again try to read phh_errors.log to inform us about error messages.

 

Thanking you for this - I added the code but still blank..

 

In my PHP error_log there is nothing new itemized to suggest an error has occurred also. 

 

Strangely I can click on "Create account" and it registers and I am automatically logged in  - I can add and can click on checkout and place an order... But I when I log out then try to log in I have the same problem.

 

 

Link to comment
Share on other sites

admin > modules > content > {install}

Not sure what you mean... In my administration page, under modules I don't have "content" heading. 

Can't see this in the directories on the server as well.

Link to comment
Share on other sites

  • 4 months later...

I'm having this exact same problem on 2 web sites. It look's like our osCommerce team jumped the gun calling this "milestone" v2.3.4. since it definitely has a BIG BUG with no clear cut fix at this time. Since I have made all the 2-1/2 pages of changes and added all the new items and cross-checked my work, I can say that everything was entered on 2 web sites and both have the same error as reported here. Who exactly tested this set of changes (UPGRADE OR FULL) and declared that it did not have bugs? One would assume that the current "demo" is v2.3.4 but it sure is not this package which apparently does not work.

 

As reported by many users, the 2 configure.php scripts are both missing. These are the 2 most critical programs as they are the only 2 that we change. Please stop all this development stuff and get this current milestone fixed ASAP. I entered a bug report today before my www.site5.com hosting service found and mentioned this forum item to me, so use this and/or the bug report.

Joseph E. "Joe" Stephenson
[email protected]

Link to comment
Share on other sites

@@jestep

 

I for one checked the manual install upgrade and used succesfully

 

I have 2.3.4 running on 5 ++  sites all taking orders everything  is correct??

 

So something wrong with your upgrade where did you downoad from ?

 

The x 2 configure.php are in the package  I have never seen any reports about them missing on this forum ??

 

Generaly if upgrading you would need to adust the configure.php manually  the admin has extra code so the old configure can not be used

 

http://www.oscommerce.com/Products

 

The upgrade guides are here

 

http://library.oscommerce.com/Online&en&oscom_2_3&release_notes

 

 

Now many people seem to miss the fact that the log in and create account are now modules and after upgrading they need to be installed from admin/modules/content/

 

So run over the install guide again and make sure you have uploaded the new content modules

 

Regards

Joli

To improve is to change; to be perfect is to change often.

 

Link to comment
Share on other sites

I'm having this exact same problem on 2 web sites. It look's like our osCommerce team jumped the gun calling this "milestone" v2.3.4. since it definitely has a BIG BUG with no clear cut fix at this time. Since I have made all the 2-1/2 pages of changes and added all the new items and cross-checked my work, I can say that everything was entered on 2 web sites and both have the same error as reported here. Who exactly tested this set of changes (UPGRADE OR FULL) and declared that it did not have bugs? One would assume that the current "demo" is v2.3.4 but it sure is not this package which apparently does not work.

 

As reported by many users, the 2 configure.php scripts are both missing. These are the 2 most critical programs as they are the only 2 that we change. Please stop all this development stuff and get this current milestone fixed ASAP. I entered a bug report today before my www.site5.com hosting service found and mentioned this forum item to me, so use this and/or the bug report.

 

For your information, 2.3.4 was tested by numerous people prior to release.  

 

If you don't understand how an upgrade is performed, ask a question.

If you do not understand new features, ask a question. 

If you believe that files are missing, ask a question or make a bug report. 

 

Either way you'll get an answer or be shot down in flames.

Link to comment
Share on other sites

I appreciate the fact that you have 5 web sites working and that others are running v2.3.4 successfully, however I have 2 web sites with the exact same problem and they are not running for over a week now.

 

I took the advice given and printed out the 57 page v2.3.4 Change Log.

I can assure you that I have implemented all the modified and new items on pages 12 thru 16 and uploaded each one to the remote. I also cross-checked the Update vs the Full and one web site vs the other.

I also found out that there were 2 required updates to the database listed on pages 32 and 33 which I have now done.

I have also uploaded all the Content changes found on page 46.

Unfortunately, I cannot do anything with them because osCommerce v2.3.4 blows up on the logon page just after the welcome and just before I am able to log in.

Turning on the debug feature did not work for me.

I know that I can circumvent the logon page and create a new user by running create_account.php - everything looks normal for a user and I have created a new user.

My gut feel is that the problem that I (and others experiencing this problem) have is probably caused by improperly coding the 2 includes/configure.php pages.

 

So I created a sample of each. I would like ONLY the people who have "WORKING" web sites running v2.3.4 to edit these examples to show the rest of us how to do these properly.

 

This is the example for catalog/includes/configure.php:

 

<?php
/*
  $Id$

  osCommerce, Open Source E-Commerce Solutions
  http://www.workingwebsite.com'); // eg, http://www.workingwebsite.com'); // (NEW-v2.3.4 - 3 of 7) - can be left blank or look like this
  define('HTTPS_COOKIE_DOMAIN', 'http://www.workingwebsite.com'); // (NEW-v2.3.4 - 5 of 7) - can be left blank or look like this
  define('HTTPS_COOKIE_PATH', 'http://www.workingwebsite.com'); // eg, http://www.workingwebsite.com'); // (NEW-v2.3.4 - 3 of 7) - can be left blank or look like this
  define('HTTPS_COOKIE_DOMAIN', 'http://www.workingwebsite.com'); // (NEW-v2.3.4 - 5 of 7) - can be left blank or look like this
  define('HTTPS_COOKIE_PATH', 'https://www.workingwebsite.com'); // (NEW-v2.3.4 - 6 of 7) - can be left blank or look like this
  define('HTTP_CATALOG_SERVER', '');
  define('HTTPS_CATALOG_SERVER', ''); // (NEW-v2.3.4 - 7 of 7)
  define('ENABLE_SSL_CATALOG', 'false'); // secure webserver for catalog module
  define('DIR_FS_DOCUMENT_ROOT', $DOCUMENT_ROOT); // where your pages are located on the server. if $DOCUMENT_ROOT doesnt suit you, replace with your local path. (eg, /usr/local/apache/htdocs)
  define('DIR_WS_ADMIN', '/admin/');
  define('DIR_WS_HTTPS_ADMIN', '/admin/');
  define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN);
  define('DIR_WS_HTTP_CATALOG', 'http://www.workingwebsite.com/catalog/');
  define('DIR_WS_HTTPS_CATALOG', 'https://www.workingwebsite.com/catalog/'); // (NEW-v2.3.4 - 7 of 7)
  define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . DIR_WS_CATALOG);
//  define('DIR_FS_CATALOG','/home/workingwebsite/public_html/catalog/'); // a completely replaced vesion may look like this

  define('DIR_WS_IMAGES', 'images/'); // Should normally not be changed
  define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
  define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');
  define('DIR_WS_INCLUDES', 'includes/'); // Should normally not be changed
  define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');
  define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/'); // Should normally not be changed
  define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/'); // Should normally not be changed
  define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/'); // Should normally not be changed
  define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/'); // Should normally not be changed
  define('DIR_WS_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');
  define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');
  define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');
  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
  define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

// define our database connection
  define('DB_SERVER', ''); // eg, localhost is commonly used - should not be empty for productive servers
  define('DB_SERVER_USERNAME', ''); // Get this from your hosting service or control panel and insert your official Username
  define('DB_SERVER_PASSWORD', ''); // Get this from your hosting service or control panel and insert your official Password
  define('DB_DATABASE', 'osCommerce'); // Get this from your hosting service or control panel and replace osCommerce with the name you get friom them (e.g. examplename_osc2)
  define('USE_PCONNECT', 'true'); // use persistent connections? Only use true or false.
  define('STORE_SESSIONS', 'mysql'); // leave empty '' for default handler or set to 'mysql'
?>

 

Thanks

Frustrated and sleepless in Dallas

jestep

Joseph E. "Joe" Stephenson
[email protected]

Link to comment
Share on other sites

I have tracked the path the program takes thogh the login script.

At line 13 it required the application_top.php

It passed the cookie tests

Set the $login_customer_id to false at line 27

Got the $page_content at line 29

Tested the $login_customer_id at line 31

Invoked function tep_session_recreate at line 33

Went to includes/functions/sessions.php

but I have no evidence that it executed the function at line 179.

 

In another test going straight to login, I saw that it went to line 97 which is:

return session_start();

Subsequently it went to catalog/admin/includes/functions/general.php line 38 which is:

header ('Location: ' . $url);

 

 

So, based on that I am deducing that there is possibly some kind of session problem because it does not appear to actually execute the function tep_session_recreate at line 33.

If that helps, maybe one of you programmers/testers, etc can take it from here. It certainly did not appear to get back to the login next step to print "Returning Customer" which is the next item according to the osc demo.

Joseph E. "Joe" Stephenson
[email protected]

Link to comment
Share on other sites

This part is completely wrong

define('HTTP_COOKIE_DOMAIN', 'http://www.workingwebsite.com'); // (NEW-v2.3.4 - 3 of 7) - can be left blank or look like this 
  define('HTTPS_COOKIE_DOMAIN', 'https://www.workingwebsite.com'); // (NEW-v2.3.4 - 4 of 7) - can be left blank or look like this 
  define('HTTP_COOKIE_PATH', 'http://www.workingwebsite.com'); // (NEW-v2.3.4 - 5 of 7) - can be left blank or look like this 
  define('HTTPS_COOKIE_PATH', 'https://www.workingwebsite.com'); // (NEW-v2.3.4 - 6 of 7) - can be left blank or look like this 
  define('DIR_WS_HTTP_CATALOG', 'http://www.workingwe...com/catalog/');
  define('DIR_WS_HTTPS_CATALOG', 'https://www.workingw...com/catalog/'); // (NEW-v2.3.4 - 7 of 7) 

"cookie domain" is the domain, not the url, so 'www.domain.com' or 'domain.com' depending what you decided to go with, www or non www

"cookie path" and "dir_ws_" should point to the directory where the store is located on the web server. This can be '/' in case the store is in the root or '/catalog/' in case of folder catalog etc

 

There are many posts on the forum that explain how to setup the configure files correctly, the mistakes you have are not caused by the upgade

 

You can also do a test nstall in some other folder, run the install script and compare the resulting configure.php giles with what you have

Link to comment
Share on other sites

This part is completely wrong

define('HTTP_COOKIE_DOMAIN', 'http://www.workingwebsite.com'); // (NEW-v2.3.4 - 3 of 7) - can be left blank or look like this 
  define('HTTPS_COOKIE_DOMAIN', 'https://www.workingwebsite.com'); // (NEW-v2.3.4 - 4 of 7) - can be left blank or look like this 
  define('HTTP_COOKIE_PATH', 'http://www.workingwebsite.com'); // (NEW-v2.3.4 - 5 of 7) - can be left blank or look like this 
  define('HTTPS_COOKIE_PATH', 'https://www.workingwebsite.com'); // (NEW-v2.3.4 - 6 of 7) - can be left blank or look like this 
  define('DIR_WS_HTTP_CATALOG', 'http://www.workingwe...com/catalog/');
  define('DIR_WS_HTTPS_CATALOG', 'https://www.workingw...com/catalog/'); // (NEW-v2.3.4 - 7 of 7) 

Multimixer

I agree completely. I had already decided  to make the 4 cookie entries blank.

 

I have been trying to track down the source of the problem using inserted print commands.

What I know/believe is this:

After selecting the product to buy on the catalog/product_info.php page

we go to includes/function/sessions.php to start a session

it seems that (with the tracking in the sessions.php) it is going to the

tep_session_start at about line 59

but eventually goes to about line 95 where it executes

register_shutdown_function ('session_write_close');

and then it goes to session_start

My tracking stops here and does not print out the Welcome message

If my guess is correct the session has been closed and there is probably a session check after the Welcome message that finds a closed session and just stops

If that is the case, we need to see what is causing the session to be closed which will solve this problem (I didn't say "bug").

 

What concerns me is that I have been installing contributions for 10 years including the 3 or 4 prior upgradesby myself  with absolutely no problem . Then along comes v2.3.4 and I have 2 web site shut down with what should be a relatively simple upgrade.  If the problem stems from the mis-coding of the 2 configure.php programs, then one of you fellows who has a "working" web site with v2.3.4 can take the example code I posted above, correct it, and post it to this forum.

 

 

Joseph E. "Joe" Stephenson
[email protected]

Link to comment
Share on other sites

Best would be you make a new fresh test install in a directory of your server and run the installation script.

 

After the test store is installed, you can check following

 

- That it work correctly. There is no bug anywhere that need to be corrected

- The 2 configure.php files that you can use as an example of a correct setup

 

Then setup your configure.php files the correct way. It is not only about the _COOKIE_ constants, the _WS_ constants are also wrong. I don't think that your configure.php was setup that way before the upgrade? Any changes there are not related to the upgrade

 

If you still have a problem, then please describe it exactly - I still didn't understood exactly what the issue is. A exact description of the problem will help people to help you

 

The process you describe regarding how the session is build is not exactly correct, however, setup things correctly first, then we see further

Link to comment
Share on other sites

@@jestep

 

i checkout your site, and just by the looks of it, i do not think you have the right to complain about the developers works.

 

you should really consider the fault on your end and not put the ball at "our" end.

you screwed up, not Oscommerce.

Link to comment
Share on other sites

In case this is of any help to you @@jestep , here are my working configure.php files from my osC 2.3.4 store. My details omitted, obviously.

catalog/includes/configure.php
 

<?php
/*
  $Id$

  osCommerce, Open Source E-Commerce Solutions
  http://www.oscommerce.com

  Copyright (c) 2003 osCommerce

  Released under the GNU General Public License
*/

// Define the webserver and path parameters
// * DIR_FS_* = Filesystem directories (local/physical)
// * DIR_WS_* = Webserver directories (virtual/URL)
  define('HTTP_SERVER', 'http://www.*****.co.uk');
  define('HTTPS_SERVER', 'https://www.*****.co.uk');
  define('ENABLE_SSL', true);
  define('HTTP_COOKIE_DOMAIN', 'www.*****.co.uk');
  define('HTTPS_COOKIE_DOMAIN', 'www.*****.co.uk');
  define('HTTP_COOKIE_PATH', '/');
  define('HTTPS_COOKIE_PATH', '/');
  define('DIR_WS_HTTP_CATALOG', '/');
  define('DIR_WS_HTTPS_CATALOG', '/');
  define('DIR_WS_IMAGES', 'images/');
  define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
  define('DIR_WS_INCLUDES', 'includes/');
  define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
  define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
  define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
  define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

  define('DIR_WS_DOWNLOAD_PUBLIC', 'pub/');
  define('DIR_FS_CATALOG', $_SERVER['DOCUMENT_ROOT']);
  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
  define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

  define('DB_SERVER', '*****');
  define('DB_SERVER_USERNAME', '*****');
  define('DB_SERVER_PASSWORD', '*****');
  define('DB_DATABASE', '*****');
  define('USE_PCONNECT', 'false');
  define('STORE_SESSIONS', 'mysql');
  define('CFG_TIME_ZONE', 'Europe/London');

?>

catalog/admin/includes/configure.php

<?php
/*
  $Id$

  osCommerce, Open Source E-Commerce Solutions
  http://www.oscommerce.com

  Copyright (c) 2014 osCommerce

  Released under the GNU General Public License
*/

// define our webserver variables
// FS = Filesystem (physical)
// WS = Webserver (virtual)
  define('HTTP_SERVER', 'http://www.*****.co.uk'); // eg, http://localhost or - https://localhost should not be NULL for productive servers
  define('HTTPS_SERVER', 'https://www.*****.co.uk');
  define('ENABLE_SSL', 'true');
  define('HTTP_COOKIE_DOMAIN', 'www.*****.co.uk');
  define('HTTPS_COOKIE_DOMAIN', 'www.*****.co.uk');
  define('HTTP_COOKIE_PATH', '/');
  define('HTTPS_COOKIE_PATH', '/');
  define('HTTP_CATALOG_SERVER', 'http://www.*****.co.uk');
  define('HTTPS_CATALOG_SERVER', 'https://www.*****.co.uk');
  define('ENABLE_SSL_CATALOG', 'true'); // secure webserver for catalog module
  define('DIR_FS_DOCUMENT_ROOT', '$DOCUMENT_ROOT'); // where your pages are located on the server. if $DOCUMENT_ROOT doesnt suit you, replace with your local path. (eg, /usr/local/apache/htdocs)
  define('DIR_WS_ADMIN', '/admin/');
  define('DIR_WS_HTTPS_ADMIN', '/admin/');
  define('DIR_FS_ADMIN', DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN);
  define('DIR_WS_CATALOG', '/');
  define('DIR_WS_HTTPS_CATALOG', '/');
  define('DIR_FS_CATALOG', DIR_FS_DOCUMENT_ROOT . DIR_WS_CATALOG);
  define('DIR_WS_IMAGES', 'images/');
  define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
  define('DIR_WS_CATALOG_IMAGES', DIR_WS_CATALOG . 'images/');
  define('DIR_WS_INCLUDES', 'includes/');
  define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');
  define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
  define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
  define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
  define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
  define('DIR_WS_CATALOG_LANGUAGES', DIR_WS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_LANGUAGES', DIR_FS_CATALOG . 'includes/languages/');
  define('DIR_FS_CATALOG_IMAGES', DIR_FS_CATALOG . 'images/');
  define('DIR_FS_CATALOG_MODULES', DIR_FS_CATALOG . 'includes/modules/');
  define('DIR_FS_BACKUP', DIR_FS_ADMIN . 'backups/');
  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
  define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

  define('DB_SERVER', '*****');
  define('DB_SERVER_USERNAME', '*****');
  define('DB_SERVER_PASSWORD', '*****');
  define('DB_DATABASE', '*****');
  define('USE_PCONNECT', 'false');
  define('STORE_SESSIONS', 'mysql');
  define('CFG_TIME_ZONE', 'Europe/London');

?>

I remember having this problem a while back and it was to do with my having not set up my cookies' paths in configure.php properly.
It also wouldn't hurt to run the code in the files that you think are causing problems through a syntax checker like: http://www.piliapp.com/php-syntax-check/ to see if you've missed a brace or semi-colon anywhere. You never know.

 

I hope you sort it.

 

Graham

Not enough time in the day. Need a time machine...

 

Would build one, but not enough time. Ironically.

Link to comment
Share on other sites

  • 6 months later...

I posted some where else... but thanks whom ever stated to look in the modules for the login screen module.  Ugh, I completely missed that for some reason (need to think more modular on this one).

Link to comment
Share on other sites

  • 5 months later...

joli1811. You rock!

My best answer!

Now many people seem to miss the fact that the log in and create account are now modules and after upgrading they need to be installed from admin/modules/content/

HTH

Neil

 

Common sense is genius dressed in working clothes.

Ralph Waldo Emerson

Link to comment
Share on other sites

  • 2 months later...

Please forgive me if this is the wrong section to post this request.  I am looking for a developer to assist us in migrating a very small DB since we are experiencing this exact problem.  Is there a proper forum to post a "help-wanted" offer?

 

Chris

 

Link to comment
Share on other sites

@@upstateuni
 

 

Please forgive me if this is the wrong section to post this request.  I am looking for a developer to assist us in migrating a very small DB since we are experiencing this exact problem.  Is there a proper forum to post a "help-wanted" offer?

 

Chris

http://www.oscommerce.com/forums/tracker/project-6-commercial-support-enquiries/

:blink:
osCommerce based shop owner with minimal design and focused on background works. When the less is more.
Email managment with tracking pixel, package managment for shipping, stock management, warehouse managment with bar code reader, parcel shops management on 3000 pickup points without local store.

Link to comment
Share on other sites

  • 3 weeks later...

Hello Community Team members.... I think I possibly have a "similar problem" as the first fellow above so I'm going to post my request for help on this string. 

 

I am running OSCommerce version 2.3.3. The last time I was into it to make changes was back in June 2015, subsequently; I logged back into it on December of 2015 to make some additional changes and found that, once logged into the "Admin" page, the whole sidebar on the left which allows editing of my Site is completely missing!

 

So, my question is this; if I upgrade to version 2.3.4 (which seems to be the latest version available on my Webpage-support), will this take care of the problem? The commerce site seems to be running fine, although I haven't gone active online yet... so I'm not absolutely sure and there may be other problems I'm not aware of yet :-O !!!

 

Thanks so much for your help and support

Culley

Link to comment
Share on other sites

Could your host have upgraded PHP in the meantime? osC 2.3.3 is old enough that it could have some problems with PHP 5.5 and up (maybe even 5.4). Possibly your host might have also upgraded the server software, or even the database version. Otherwise, check the "last updated" timestamps of your files and see if some hacker might have been in there messing with your files. Maybe it was even your host, concerned about a hacker using your site editing functions to do nasty things to you! They certainly should have told you that they did such a thing.

 

osC 2.3.4 should certainly bring you up to date on PHP and MySQL compatibility, although while you're at it, you might consider migrating your data to a fresh osC 2.3.4BS (bootstrap responsive version) installation, and be all caught up for now. In any case, be sure to back up your files and database before making any changes, just in case.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...