Closed (works as designed)
Project:
Omega
Version:
7.x-3.1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
29 Feb 2012 at 22:42 UTC
Updated:
2 Oct 2014 at 17:03 UTC
Jump to comment: Most recent
Comments
Comment #1
finedesign commentedI am using Omega 3.0 and UC 7.x-3.0 with Paypal as the payment gateway and don't receive the same issues.
Comment #2
Anonymous (not verified) commentedI probably should have mentioned that it was with the direct transfer payment and paypal express ( although i was only testing with paypal express for a short time ) it was working with the normal paypal standard
Comment #3
marcoka commentedi think for this complicated setup a demo would be good. otherwise i dont think that someone will configure all that stuff only to test that.
as i understand redirection goes wrong.
do NOT use omega as an administration theme. its not meant for that
Comment #4
Anonymous (not verified) commentedits not a complicated setup
drush dl ubercart omega uc_bank_transfer
drush en -y ubercart omega uc_bank_transfer
create 1 product and test
Comment #5
cellar door commentedhmmmm I'm not seeing what Omega would do that would cause a re-route like this. Do you have any further debug info on this? Maybe the code around the submit button? The only thing I can think of (and this is a waaaay long shot) is that the js in omega is somehow conflicting w/ that of the ubercart. But commerce guys use omega in their theming so I know it can handle the e-commerce stuff just fine.
More info would be great
Comment #6
Anonymous (not verified) commentedI am not to sure what other info i can give. I do not see any errors in chrome inspector. The thing is this was not working for a few others and i am not sure they were using the omega theme or not
http://drupal.org/node/1187632
ubercart seemed to have resolved the problem with the latest update, i was not too sure where to post this because i am not sure if it might be an error in the ubercart code that conflicts with omega or visa versa. But either way if omega is not the theme for that checkout process it works fine. Also this is not an administration theme issue because the checkout is not an administration page, i only referred to the problem omega was having with it as administration theme with the media module ( although this seems to have been fixed )
Comment #7
cellar door commentedTo be honest this sounds like an ubercart thing. If it's a bug that's been addressed in the past through the module then that's probably where the fix needs to occur. The issue with media/admin was a permissions based issue, not a conflict with the module itself.
For now I would work w/ the ubercart team in order to figure out the root of the issue, if it's deemed to be an Omega thing then we can open it back up and incorporate what needs to be fixed. Not being ubercart pros though we'd be spinning our wheels trying to figure out the module interaction.
Another thing to look into like I said prior is Commerce. Not sure how deeply integrated w/ Ubercart the site is but Commerce is known to work very well w/ Omega without any issues.
Good luck and let us know if you find something that needs to be patched w/ the ubercart guys
Comment #8
Anonymous (not verified) commentedcool .. yeah i thought it might be more a ubercart issue, just was not too sure.
I actually used the commerce module first and did not particularly like they way one had to setup products twice and the attributes settings was a bit weird as well. probably just a personal thing though. Will probably look at it for future commerce development.
Comment #9
joemoraca commentedI am having a very similar issue - except trying to use authorize.net as the payment gateway http://drupal.org/node/1532130