Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
batch system
Priority:
Minor
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Feb 2012 at 08:24 UTC
Updated:
3 Oct 2014 at 15:09 UTC
Jump to comment: Most recent
Comments
Comment #1
greenwork commentedComment #2
greenwork commentedOk I have narrowed this down to secure pages and here is how I produced it
If i:
Login->strait to modules staying in SSL->install new modules everything works
But if I leave SSL and then go to modules with the direct link to install the module it will redirect me to "no batch" message. I tried setting the install page to force the SSL version but that did not seem to fix it. Any other suggestions other then clearning my browser memory and going strait to the module page?
Comment #3
greenwork commentedI added had to add the whole update module process to the ignore list. I hope this helps people since looking at drupal.org they have 100s of people complaining in each module for the "no active batch" problem I noticed the notice appears on the opposite type of page https vs http.
Comment #4
greenwork commentedMoving this back because even running everything through http had problems and I had to apply the patch manually.
Comment #5
sol1313 commentedSame issue here. It seems to be related to the Secure Pages as I was encountering the same issue. Anytime the page tries to go to https then it says No Active Batch. I might disable the module and test that for a while and see what happens, but I need the secure site for payment processing. If anyone has any updates, please post.
Comment #6
sol1313 commentedI temporarily solved some of the issues by adding http://mysitename.com/update.php to the list of non-secure pages. This at least let me update my modules without the error. Hope this helps someone else.
Comment #6.0
sol1313 commentedDrupal version 7.12
Comment #7
markwittens commentedThis is not really a bug, this happens when you enable secure pages with only the preselected pages to be secured. Just add the path "batch" to the list of secured pages in the secure pages settings and the problem will be gone.
(I Know this post is 2 years old but maybe it helps someone who is searching for the error message)
Comment #8
dcam commentedThank you, @markwittens. Hopefully this will help other people in the future.
Comment #9
xl_cheese commentedI'm having this issue. I added batch to my list of secured pages as suggested above and it seems like a step backwards.
I have the issue where I can download updates, but when I click the button to install I get redirected to the front page with the Batch error.
When I add batch to my list of secured pages I get the batch error as soon as I try to download the updates.
I've also read where people have success with adding *batch* to the ignore list. This doesn't make any difference for me. Any other suggestions would be greatly appreciated!
Thanks.
Comment #10
greenwork commentedOk here is the solution we used: You need to make the admin role be 100% https. Its a settings option. Batch/updates and all the functionality being dropped before worked and we are not battling the future of the drupal update process.
EDIT: Make sure you have HTTPS working before hand.
Comment #11
greenwork commented@mark @dcam for many people including myself adding variations of batch to the list did not fix the problem. I believe its a cookie security issue and any fix like that (if it works for you) could break later with a change to the drupal update system.
Comment #13
xl_cheese commentedgreenwe,
Thanks for the suggestion. However when I make the admin role https as suggested I get a new issue. Upon clicking install updates, I get a new screen that is white with plain text with Installing update on it. But nothing seems to be happening. I don't get the usual flow.
What else can I try?
Comment #14
xl_cheese commentedI experience the same issue when trying to install a new module. I have do do them the old fashion way with FTP.
Comment #15
greenwork commentedXL
Remember to always make backups of everything first.
Make sure when you are manually updating by ftp you do not have multiple folders of the same module at any point. It creates errors as well. A good way to do this is to delete the whole folder before updating it.
Comment #16
xl_cheese commentedgreenwe,
Thanks for the help. Do you know of someone that will do freelance and look at my site to help fix it?
The issue I'm having with installing modules is just another issue I'm having which I think is related to this one.