Upgrade errors while debugging

[safede]

I get these three errors during the debug process....any ideas???

 

Warning: Function includeController() is deprecated in /data/11/1/90/124/1090613/user/1137135/htdocs/safede/store/classes/ControllerFactory.php on line 62

in /data/11/1/90/124/1090613/user/1137135/htdocs/safede/store/classes/Tools.php on line 1845

 

Warning: require_once(/data/11/1/90/124/1090613/user/1137135/htdocs/safede/store/classes/../controllers/IndexController.php) [function.require-once]: failed to open stream: No such file or directory in /data/11/1/90/124/1090613/user/1137135/htdocs/safede/store/classes/ControllerFactory.php on line 43

 

Fatal error: require_once() [function.require]: Failed opening required '/data/11/1/90/124/1090613/user/1137135/htdocs/safede/store/classes/../controllers/IndexController.php' (include_path='.:/usr/services/vux/lib/php') in /data/11/1/90/124/1090613/user/1137135/htdocs/safede/store/classes/ControllerFactory.php on line 43

[safede]

ok...I found the message in the logfile that said .....The function includeController (Line 62) is deprecated and will be removed in the next major version.

 

Next I edited the ControllerFactory.php file and replaced (__FILE__) on line 43 with

(include_path='.:/usr/services/vux/lib/php').....and when I debugged....this is the next error.

 

Parse error: syntax error, unexpected '=' in /data/11/1/90/124/1090613/user/1137135/htdocs/safede/store/classes/ControllerFactory.php on line 43

 

I think I'm getting close...ut any suggestions would be appreciated.

[bellini13]

you should not replace _FILE_ with (include_path='.:/usr/services/vux/lib/php'), not sure what made you do that.

 

What version are you trying to upgrade to? I assume PS v1.5.4.1?

 

The process is trying to locate IndexController.php within the folder classes/controllers, but the file exists within controllers/front.

[safede]

Thanks for the reply...yes I'm upgrading to v1.5.4.1......

 

What adjustments should I make with the php file to correct the issue? or could I just copy that file over to that directory?

 

I will rollback the changes and get the original three errors.

[safede]

Well...I've tried to reinstall just to see if that would clear up any errors....and it did not....right now I'm trying to reinstall to an earlier veriosn of 1.5 to see what that might produce.

 

Any tips or advice would be appreciated....

Edited August 10, 2013 by safede (see edit history)

[safede]

ok...here's my latest update!!! Upgraded to v 1.5.1.0 and it corrected the errors from v1.5.4.1

 

I'm seeing two other issues....

 

#1 - 1 click upgrade is giving me this error. The controller adminselfupgrade is missing or invalid.

 

#2 - cannot delete a shipping carrier...I get an internal server error and this is the URL

www.mywebsite/index.php?controller=admincarriers&id_carrier=5&deletecarrier&token=token

 

Any ideas or suggestions would be great!!

[safede]

after a long day....and many attempts to clear up these two errors...I believe we can close this thread as solved (in a very long roundabout way)

 

First the fix and then the few problems...then a recap of eventual steps to get there.

The Fix-

Did an upgrade from v1.5.3.1 to v1.5.4.1 that cleared up my two earlier errors. But now...there are two additional problems that I'm trying to deal with....one minor and the other a showstopper.

 

First the minor- the header logo under Preferences/Themes will not keep my uploaded file within the system. Although it says that the changes were accepted, when I navigate to another page and come back...my uploaded header logo is gone. Tried about 15 times to keep the logo...would not work. The end result was to rename my header logo on my local machine to logo.jpg and FTP to the /img folder....it worked.

 

Now the showstopper. The payment module (Paypal) does not show up as installed during the checkout process even though it was setup in the back office and api settings entered. I've tried to disable it, reconfigure it, delete, upload module and reinstall...I've tried every step backwards, forwards....etc. Now...my shop is setting in maintenance mode until I get this figured out. I've tried to install the backwards compatibility module and install an older version of paypal. The bc module installs...and when I try to install the paypal v3.5.7 the module doe not upload correctly....in fact the back office says the download was successful. The module cannot be found anywhere in the module list.

 

I wish I could find an older version of paypal...like ver 3.5.5...I could at least try that. **Additional notes....I read in another thread that paypal was most likely the culprit by blocking the api....so that is my next step to take. It will most likely take forever for them to even get back with me.

 

 

Now...in this section I will explain the basic steps as to how I upgraded and fixed my original two errors.

 

#`1. was using v1.4.10 when paypal stopped working and would not process payments....tried many times to reconfigure, install, delete and try again, installed backward compatibility...all to no avail....thought it would be best to upgrade to latest version.

 

#2. installed 1 click upgrade...tried to auto update....received failed ajax server error and would not completed the final stage to update. Tried this several times and had to keep rolling back the version to 1.4.10

 

#3. decided to try to do a manual update...after the install received two errors (see the beginning of this post)...attempted several more times to reinstall...but still the same errors.

 

#4. finally decided to install an earlier version of v1.5 to see if that would clear up these two original errors. Installed v1.5.1.0 and this seemed to clear up my two original errors...but now two additional errors came up....(see earlier post)...tried everything I could think of and then cleared up the 1-click upgrade error by downloading and installing this module. Still could not remove the carriers under shipping. Tried to use the 1-click update and go to v1.5.4.1 and again received the failed ajax server error....did a rollback and decided to try a different version.

 

#5. decided to try with v1.5.0.1.....still was having the same problems.

 

#6. decided to try v1.5.3.1...and this seemed to make some progress. I was able to eliminate the shipping carrier issues by deleting all the carriers and relisting them...I thought his was good....so I tried the 1-click upgrade and again....the failed ajax server error....so I then decided to do a manual upgrade....was finally able to install v1.5.4.1....but now...two additional issues started...(see the beginning of this post)

 

After what seems like a marathon day trying to figure this out....I not sure what to do next other than to try to contact paypal and open a technical ticket.

 

One last thought...here's the irony of all this....I have another store on a different domain....same server and provider....running v1.4.6.2 with paypal module v2.8.5 and everything is working on that site...no problems.....go figure.????

 

Thoughts....comments....ideas...would be appreciated.

[bellini13]

when you install the paypal module, are you uploading the module from the backoffice? have you tried to uninstall the module, then delete the module, then using FTP upload the extracted module file. Then go to the back office modules section, search for Paypal, and click install.

[safede]

I did not try that...but I believe that would not have worked because I finally discovered what was wrong...and have corrected the problem and now paypal is working again!!!

 

Let me explain in case someone else has the same issues....btw...paypal technical support was not available....so after non-stop work...I discovered an error in the permissions....Administration Permissions

It seems that I was getting 4 permission errors on modules that were loaded but missing files...the paypal module was one of them...this seemed odd. I went back to my modules loaded and made sure I deleted the paypal module.

 

I then accessed my database through phpMyAdmin and located the 7 ps_module files using the browse function.

 

I started out with the ps_module and sorted by name...I found the 4 modules on the list, made a note of their id_module number..then I started to delete these modules...I repeated each step for the remaining 6 ps_module files.

 

I also found my paypal v1.2.1 which was loaded during my upgrade....I also deleted this module from the database....

 

I must add that I felt confident changing my database...since I had a backup copy that could be restored if something went wrong. I also believed that I was on the right track when after each time deleting a module in the tables...I would check the permissions and each time the error was gone.

 

Next I reinstalled paypal v1.2.1 and applied the API information. Also please note that I discovered another possible error that others may encounter...on your API settings....make sure your setting under the PayPal Business Account required field is the email address that is associated with your account....If you enter a name...during the checkout process...the buyer will encounter an error stating that there was something wrong with the seller's email address associated with the account.

 

I hope this information helps others....and I encourage others to keep working on their errors and not give up....this has been a marathon session for me...over the last three days...but finally it is working!!!

 

A side note...I've discovered that the images associated with previously viewed items do not show up...I get a blank image...the url is pointing here...img/p/en-default-medium_default.jpg

 

Thanks for all the help

Edited August 11, 2013 by safede (see edit history)

[bellini13]

thanks for providing the steps to correct the issue.

 

I would not call those "permission" issues however. Those are what we call orphaned records, and I have encountered the same issue in the past. During the upgrade, it seems Prestashop does not delete these orphaned records appropriately, and that they expect you to have manually uninstalled these modules prior to the upgrade. I would guess that it is just a gap in the design of the software.

 

In any event, my suggest to cleanly uninstall the paypal module, delete it, and then manually upload it, should have had the same effect as you manually removing the records from the database.

[safede]

Thanks for your suggestions thepast few days,,,,I used the term permissions...because that how PrestaShop identified these "orphaned records". In any event...I hope these steps will help others..