Fatal error after save of privacy.php

[Ray B]

I am a dummy. Building a new store in oscommerce. In admin opened the privacy.php file in "define language" Entered a couple paragraphs in place of the default entry and saved. Went to the store to see how it looked and got this message

 

Fatal error: Call to a member function add_current_page() on a non-object in /home/wetpetss/public_html/includes/application_top.php on line 312

 

I opened the application_top.php file with "freefileopener" and can't determine the problem. I was hoping the lines would be numbered. As a complete php dummy I probably need a php pro to get me out of this. But I am willing to try - I think.

 

Ray B

[Guest]

Ray,

 

 

The ONLY way you should be editing your files is with a text editor such as Editplus+ or Notepad++. For these you have to use your FTP client to download the file, edit it with one of the text editors and then upload it back to your server.

 

 

 

More than likely, the editor you used has placed hidden formatting into the file that now makes it unreadable. Restore your back up and make the changes again as described.

 

 

 

 

Chris

[Ray B]

Chris, thanks. The restore returned everything. I will explore the editing of the info pages - very carefully.

Ray

 

Ray,

 

 

The ONLY way you should be editing your files is with a text editor such as Editplus+ or Notepad++. For these you have to use your FTP client to download the file, edit it with one of the text editors and then upload it back to your server.

 

 

 

More than likely, the editor you used has placed hidden formatting into the file that now makes it unreadable. Restore your back up and make the changes again as described.

 

 

 

 

Chris

[satish]

Call to a member function add_current_page() this is an indication of session issues with navigation variable.

 

You need to make sure that a global register patch to get hold of navigation object is applied.

 

Satish

[Ray B]

Hmmm, Satish. I apologize. I don't have the smarts to follow what you said. I think you are raising the possibility that there is something other than the save of the privacy.php file as a problem. Even though a "Restore" has returned us to a functioning level, there may be a problem that needs attention. It was there before and is still there. How do I find out and apply the fix.

 

Ray

[satish]

http://www.oscommerce.info/confluence/display/OSCOM23/%28C%29+%28BUG%29+Fix+Navigation+History+Session+Content

 

// navigation history - if (tep_session_is_registered('navigation')) { + if (tep_session_is_registered('navigation') && is_object($navigation)) { if (PHP_VERSION < 4) { $broken_navigation = $navigation; $navigation = new navigationHistory;

[MrPhil]

Wasn't the navigation problem fixed in 2.3.1? Ray, if you're building a new store, don't use anything older than version 2.3.1 (the current version). It sounds like you may be trying to set up with an obsolete version of osC. "Templates" and such you purchase may still be based on older versions -- avoid them if you possibly can.

[Ray B]

Phil, you are right. I am using 2.2 primarily because of easy populate. I used easy populate to add the products to the catalog. I will uss easy populate routinely to add and modify the products. My understanding is that they haven't upgraded easy populate yet to work with more advanced versions of osc.

 

Reading back over this note i must have thought I would get paid a nickle for each mention of easy populate.

 

Ry

[Xpajun]

Phil, you are right. I am using 2.2 primarily because of easy populate. I used easy populate to add the products to the catalog. I will uss easy populate routinely to add and modify the products. My understanding is that they haven't upgraded easy populate yet to work with more advanced versions of osc.

 

Reading back over this note i must have thought I would get paid a nickle for each mention of easy populate.

 

Ry

 

Easy Populate for 2.3.1