We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Installation errors for 1.0.5

    • 20135
    • 188 Posts
    moniarde Reply #1, 15 years, 5 months ago
    http://modxcms.com/forums/index.php/topic,54290.0.html


    Receive the following error when trying to upgrade from 1.0.0 to 1.0.5 on standard installation.

    « MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »
 
PHP error debug
  Error: 	Missing argument 1 for AjaxSearch::run(), called in /home/xxx/public_html/manager/includes/document.parser.class.inc.php(770) : eval()'d code on line 411 and defined	 
  Error type/ Nr.: 	Warning - 2	 
  File: 	/home/xxx/public_html/assets/snippets/ajaxSearch/classes/ajaxSearch.class.inc.php	 
  Line: 	64	 
  Line 64 source: 	function run($tstart, $dcfg, $cfg = null)

    Have tried uploading AjaxSearch 1.9.2b prior to running install, no change.

    Running Linux with Apache 2, Mysql 5.0.92 and PHP 5.2.17.
      • 8609
      • 607 Posts
      einsteinsboi Reply #2, 15 years, 5 months ago
      Did you do a backup before running the upgrade? If yes, it might be a good idea to revert to your original site then redo the upgrade but first disable and completely remove Ajaxsearch and make sure you unselect the Ajaxsearch snippet when running the upgrade. If that works fine, you can then manually install the new version of Ajaxsearch.
        The Coding Pad - MODx        MODx Beginner Tutorials     
        MODx Video Tutorials 
        MODx Development
        • 20135
        • 188 Posts
        moniarde Reply #3, 15 years, 5 months ago
        Good idea. I did take a backup, and restored it when the upgrade didn’t work.

        Would be wise to have this problem sorted, as per the link in my original post, I’m not the first one to come across it.
          • 8609
          • 607 Posts
          einsteinsboi Reply #4, 15 years, 5 months ago
          I’m honestly not sure why some people have this error and some don’t. I’ve upgraded a bunch of MODx sites through from 0.9.6.3 to 1.0.5 and never run into this issue before. However, I did incremental upgrades, so when 1.0.0 came out I upgraded to that, then I upgraded to 1.0.2 when it came out, then to 1.0.4 then to 1.0.5, so it wasn’t too much of a jump during upgrades. Not really sure that has anything to do with it. I do remember though that at some point I had to make changes to my AjaxSearch calls when some of the syntax changed, but usually the errors would only show up right where the search box was. I never got the kind of parse errors you’re reporting. So not entirely sure what it is that breaks some sites and not others.

          Good luck, let us know how it goes
            The Coding Pad - MODx        MODx Beginner Tutorials     
            MODx Video Tutorials 
            MODx Development