I'm running MAMP and VirtualHostX on my MacBook. I have a number of development sites set up that up until now have worked fine. Today when I tried to install a new theme or module after selecting the .gz file I get this URL and but then nothing happens (maybe WSOD?):
http://dev.git-test/authorize.php?batch=1&op=start&id=8
I created a fresh install of 7.15 and it all works fine. I can update modules and themes without problem.
The problem seems to be the authorize.php script. Any ideas on what I should do to make it work again?
Thanks. Warren
Hey Warren,
Might the non-working site have the Secure Pages module (or something similar) running?
Sometimes the "quick/transparent switch" between HTTP and HTTPS URLs -- especially as it relates to the built-in module update process involving the authorize.php script -- can play havoc with you. If you have an HTTP/HTTPS switching configuration, try disabling it with your site in maintenance mode and see if that works.
The one mitigating factor here that doesn't jibe with my own experience is your apparent WSOD. With the HTTP/HTTPS issue, you are more likely to get your home page with a "No active batch" error message.
--Sohodojo Jim--
I'm running MAMP and VirtualHostX on my MacBook. I have a number of development sites set up that up until now have worked fine. Today when I tried to install a new theme or module after selecting the .gz file I get this URL and but then nothing happens (maybe WSOD?):
http://dev.git-test/authorize.php?batch=1&op=start&id=8
I created a fresh install of 7.15 and it all works fine. I can update modules and themes without problem.
The problem seems to be the authorize.php script. Any ideas on what I should do to make it work again?
I don't think it is that because the sites are very basic -- I was just playing with different themes. No HTTPS at all.
Thanks for the suggestion, though.
Warren
On Feb 4, 2013, at 11:04 AM, Sohodojo Jim wrote:
Hey Warren,
Might the non-working site have the Secure Pages module (or something similar) running?
Sometimes the "quick/transparent switch" between HTTP and HTTPS URLs -- especially as it relates to the built-in module update process involving the authorize.php script -- can play havoc with you. If you have an HTTP/HTTPS switching configuration, try disabling it with your site in maintenance mode and see if that works.
The one mitigating factor here that doesn't jibe with my own experience is your apparent WSOD. With the HTTP/HTTPS issue, you are more likely to get your home page with a "No active batch" error message.
--Sohodojo Jim--
I'm running MAMP and VirtualHostX on my MacBook. I have a number of development sites set up that up until now have worked fine. Today when I tried to install a new theme or module after selecting the .gz file I get this URL and but then nothing happens (maybe WSOD?):
http://dev.git-test/authorize.php?batch=1&op=start&id=8
I created a fresh install of 7.15 and it all works fine. I can update modules and themes without problem.
The problem seems to be the authorize.php script. Any ideas on what I should do to make it work again?
-- [ Drupal support list | http://lists.drupal.org/ ]
When I set up a subdomain for testing stuff and mirrored the live site in the subdomain, I had the exact same thing happen. At first I thought it was .htacces that needed tweaking. But no, not at all. In my setting.php file the root was specified, and of course that was changed. So I simply changed this to the correct definition, and all was well.
Pia
I'm running MAMP and VirtualHostX on my MacBook. I have a number of development sites set up that up until now have worked fine. Today when I tried to install a new theme or module after selecting the .gz file I get this URL and but then nothing happens (maybe WSOD?):
http://dev.git-test/authorize.php?batch=1&op=start&id=8
I created a fresh install of 7.15 and it all works fine. I can update modules and themes without problem.
The problem seems to be the authorize.php script. Any ideas on what I should do to make it work again?
Thanks. Warren -- [ Drupal support list | http://lists.drupal.org/ ]
Hmmm. Interesting, but probably not applicable to these sites because they were working one day and not working the next, and I did not touch them in the interim.
I'm thinking that it might have something to do with MySQL, but I stopped and restarted the servers, but no success.
Thanks for the suggestions.
Warren
On Feb 4, 2013, at 12:42 PM, Pia Oliver wrote:
When I set up a subdomain for testing stuff and mirrored the live site in the subdomain, I had the exact same thing happen. At first I thought it was .htacces that needed tweaking. But no, not at all. In my setting.php file the root was specified, and of course that was changed. So I simply changed this to the correct definition, and all was well.
Pia
I'm running MAMP and VirtualHostX on my MacBook. I have a number of development sites set up that up until now have worked fine. Today when I tried to install a new theme or module after selecting the .gz file I get this URL and but then nothing happens (maybe WSOD?):
http://dev.git-test/authorize.php?batch=1&op=start&id=8
I created a fresh install of 7.15 and it all works fine. I can update modules and themes without problem.
The problem seems to be the authorize.php script. Any ideas on what I should do to make it work again?
Thanks. Warren -- [ Drupal support list | http://lists.drupal.org/ ]
--
Randall House (member Antiquarian Booksellers' Association of America - http://www.ABAA.org , ILAB, IOBA) 835 Laguna Street Santa Barbara, California 93101
(805) 963-1909 fax (805) 963-1650 http://www.RandallHouseRareBooks.com
Know who your Internet bookseller is! Look for the ABAA membership logo, the Antiquarian Booksellers' Association of America - now more than 50 years of professional organization requiring its members to have a proven track record of knowledge and experience, and to abide by a written code of ethics. -- [ Drupal support list | http://lists.drupal.org/ ]
Have you checked your Apache/PHP error logs for any clues?
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 2/4/2013 5:40 PM, Warren Keuffel wrote:
Hmmm. Interesting, but probably not applicable to these sites because they were working one day and not working the next, and I did not touch them in the interim.
I'm thinking that it might have something to do with MySQL, but I stopped and restarted the servers, but no success.
Thanks for the suggestions.
Warren
On Feb 4, 2013, at 12:42 PM, Pia Oliver wrote:
When I set up a subdomain for testing stuff and mirrored the live site in the subdomain, I had the exact same thing happen. At first I thought it was .htacces that needed tweaking. But no, not at all. In my setting.php file the root was specified, and of course that was changed. So I simply changed this to the correct definition, and all was well.
Pia
I'm running MAMP and VirtualHostX on my MacBook. I have a number of development sites set up that up until now have worked fine. Today when I tried to install a new theme or module after selecting the .gz file I get this URL and but then nothing happens (maybe WSOD?):
http://dev.git-test/authorize.php?batch=1&op=start&id=8
I created a fresh install of 7.15 and it all works fine. I can update modules and themes without problem.
The problem seems to be the authorize.php script. Any ideas on what I should do to make it work again?
Thanks. Warren -- [ Drupal support list | http://lists.drupal.org/ ]
--
Randall House (member Antiquarian Booksellers' Association of America - http://www.ABAA.org , ILAB, IOBA) 835 Laguna Street Santa Barbara, California 93101
(805) 963-1909 fax (805) 963-1650 http://www.RandallHouseRareBooks.com
Know who your Internet bookseller is! Look for the ABAA membership logo, the Antiquarian Booksellers' Association of America - now more than 50 years of professional organization requiring its members to have a proven track record of knowledge and experience, and to abide by a written code of ethics. -- [ Drupal support list | http://lists.drupal.org/ ]
Thanks, that was what I needed. For anyone interested, the php log is located in
/Applications/MAMP/logs
Apparently the issue was that I had devel_themer enabled and it did not like that I was trying to install (not yet enable) a new theme. Should I I report this as an issue or should I have known to turn off devel first?
Warren
On Feb 4, 2013, at 3:56 PM, Jamie Holly wrote:
Have you checked your Apache/PHP error logs for any clues?
Jamie Holly http://www.intoxination.net http://www.hollyit.net