Moving Server, Errors Everywhere!

I am trying to move my Revo site to a subdirectory on another server. The issue I have, and I have never had this problem when moving to the root of a domain, is that lots of my extras break terribly! I get the following error above the manager window whenever I click on a resource with a MIGX Tv entry:



On the front end:

Missing arguments for mxCalendar (properly renders but with two of these warnings above it):



and DOZENS of these for spiefeed:



I did a proper move to the server (ensuring .htaccess pointed to subdirectory) like I always have when moving a site to the root. I have NEVER had an issue moving servers but this is my first time moving to a subdirectory with a separate modx revo install in the root. I even did it again, but by doing a clean install, installing the extras in the clean install, then overwritting the database. Same results exactly.

I'm on a godaddy shared server.

Any ideas how to fix this? I'm completely stumped! Thanks for any help you can give me. [ed. note: maroonlover last edited this post 11 years, 8 months ago.]

Hi maroonlover,

1. Did you try to manually delete the contents of the "/core/cache" folder via FTP?

2. Did you re-run setup? This will fix issues with paths and permissions.


Hope this will help...

greetings

I did, sadly it did nothing.

Hi maroonlover,

and i guess you followed the documentation at http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server ?

I am sorry, i never used the specific plugins mentioned above.


Maybe someone else can help?

greetings

Yeh I did, thanks though, I appreciate it.

The deprecated call can be solved by going to the line of the file specified and removing the & from &$this.

Likewise for the return value deprecated bit, go to the line numbers of the files specified and remove the &

Apparently your new server has a newer version of PHP.

Your right! It IS a newer version and they JUST upgraded. I'm just glad I, as a php dunce, can fix it

Many extras are breaking (including some of mine) as a result of PHP upgrades and having E_NOTICE and E_DEPRECATED error reporting turned on at the server.

They are usually very easy to fix, but it's important to let the author of the extra know about them. The author may not see them on his or her platform.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Would you know how to turn that off on a godaddy shared server? They told me to edit the php.ini but there isn't one.

You should be able to create a php.ini file in the MODX root directory to solve the problem, unless MODX sets the error reporting level on its own -- I'm fairly sure that it doesn't. Just make a text file with one line.

I would recommend this:




You could use this:



but deprecated code could cause problems that would be difficult to diagnose.

In a development environment, you'd probably want this, so all possible problems would show up:



Be warned, however, that MODX can hang when a warning or notice is thrown in a plugin. A good code editor will warn you about most potential problems and help you find and fix extras that are not up to snuff.



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html