After migrating site, authorize.php, update.php does not work

I am having the same exact issue. The exact error I get when trying to install new modules is

Page not found

The requested page "/authorize.php?batch=1&op=start&id=124" could not be found.

What am I doing wrong? I need to add Ubercart, but can't get the module loaded!!

HELP!!

That's exactly the same issue I have. Page not found.

(Will update here if I find anything that could help.)

i got the same problem. i checked the apache log and i found that there is an error of my module called beanstag.

PHP Fatal error: Call to undefined function token_replace() in /var/www/drupal/sites/all/modules/beanstag/beanstag.module on line 271

So i disable the module and run the update again in update manager. but got the following error.

Downloading updates failed:

* Archivers can only operate on local files: temporary://update-cache/views-7.x-3.x-dev.tar.gz not supported

So i checked the drupal tempoary directory and delete all files there manually.

Finally the authorize.php returns to normal during update.

hope the above info could give u some ideas. i suggest you could disable some modules and see if that could solve the problem. checking the apache log may help too.

Please follow the steps outlined on this page and post any errors you receive.

Same issue with me...has anyone found a solution??

It doesn't really give an error, just shows a page without CSS and hangs...

@djfurman
Unfortunately what you are describing are very generic symptoms to an enormous number of possible problems. You are going to need to provide more details for us to be able to even make suggestions. Please follow the steps outlined at http://drupal.org/node/158043 and http://drupal.org/node/482956 and provide any warnings or error messages. In addition when reporting problems or requesting help it is useful to provide versions of:

• Operating System
• Apache
• PHP
• MySQL
• Drupal

with your report so we can better help you solve your problem. Please read the section titled "Issue Details" on this page http://drupal.org/node/73179 for how to structure issues. That whole page is actually pretty good information. Following these steps gives you the best chance of getting your issue resolved.

Hi Jon, i see that you looked into this thread to provide for a solution. i am having a very similar problem. i am hoping you can help me. i added a module and got this:

the error message: https://www.mydomain.biz/authorize.php , access denied, You are not allowed to access this page. when i went back with the back button, it display more error details. i am attaching both images.

it is behaving as if i am not the administrator really. it is my site and i work alone.

because of uninstalling a module i thought i didnt need, and then afterwards realizing i needed it: domain access module. the site started to display AJAX errors. so i uploaded a 3 days earlier backup that contained the site before i did the uninstall, both for the site and database. after doing this, it behaved better but found a new set of errors:

1. when editing an user, after click submit, takes me to an error page. but the action was processed.
2. after adding a module, script updating,
3. adding a new menu inside structure (it displayes as unabled, when it is) and i do not see it listed in the regular link [provide menu link menu], as i saw it in the past, or the dragging to position a menu item is gone.
4. even clicking on the home link main menu, when i am inside the administration, takes me out of the administration to the site under maintenance page.

my drupal setting is located inside a VPS linux.

thank you Jon or anyone available to share, for any lead to help me get this back to norm.

@vhiering
A few things to try

1. Temporarily set this to your settings.php file:
   $update_free_access = TRUE
   Set it back to FALSE when you are done with troubleshooting
2. Flush all caches: http://yourdomain.com/?q=admin/config/development/performance
3. Rebuild Node Permissions: http://yourdomain.com/?q=admin/content/node-settings/rebuild
4. Flush all caches again: http://yourdomain.com/?q=admin/config/development/performance
5. Set $update_free_access = FALSE

If you're getting this error after migrating site check if authorize.php have Write premissions for Group and Others. If it has, remove them. This worked for me.

I'll going to close this issue as fixed now since there has been no response since a solution was offered.

Please do reopen the issue if you still require assistance, with full instructions to recreate the error from a fresh installation of the latest version.

I am also experiencing this issue after a recent site migration.

Apache logs show:
"....AH01215: PHP Parse error: syntax error, unexpected '[' in /home/sites/{mysite}/public_html/authorize.php on line 287"

UPDATE: I noticed the authorize.php file was 16.4MB in size for some reason. Upon downloading, it seemed to be filled with binary data. I deleted and re-uploaded a backed up authorize.php file (6.45KB) - everything now seems to be working fine

I don't see any answer in here. I am having the exact issue. Cannot find update.php, authorize.ph, css and js files. All files are in the correct folders with correct permissions.

CenOS 7
Apache 2.4
PHP 5.4.16
Drupal 7

This has got to be the WORST CMS I have worked with!!

@chillyw13

I don't see any answer in here. I am having the exact issue. Cannot find update.php, authorize.ph, css and js files. All files are in the correct folders with correct permissions.

If you can't pull up your CSS and JS files from within the browser (as plain text) there HAS to be something wrong with the web-server setup rather than the CMS. Are you able to create a test.txt file in the root of your site and then pull it up from a browser (like http://www.mysite.com/test.txt) ? Does that come up with whatever text you put in it or is it a 500 error?

If not, then I highly suggest you review the web-server config, check the Apache error log for more details on what's actually going wrong, and then try the other steps listed in this thread. I had the issue myself in the past and it turned out to be a misconfiguration with Apache and a Permissions error, rather than the CMS itself.