Everything was working fine and I then updated to Ubercart 7.x-3.0-rc3 and now when I click Recurring Fees from a previously completed order, it gives a 500 error. I don't have access to the logs right now, but I will report back with a more precise cause of the 500 error when I can.

Comments

tr’s picture

Project: Ubercart » UC Recurring Payments and Subscriptions
Version: 7.x-3.0-rc3 » 7.x-2.x-dev

Recurring fees are provided by the uc_recurring module.

shazar’s picture

But wouldn't this be a problem with Ubercart as it is the update that broke it?

shazar’s picture

Project: UC Recurring Payments and Subscriptions » Ubercart
Version: 7.x-2.x-dev » 7.x-3.0-rc3

The error is:

PHP Fatal error: Call to undefined function uc_order_admin()

Did Ubercart remove this function?

longwave’s picture

Project: Ubercart » UC Recurring Payments and Subscriptions
Version: 7.x-3.0-rc3 » 7.x-2.x-dev

The function generated the order admin pages; these have been replaced by Views, and this will not be reverted, so this needs to be fixed in the recurring fees module.

univate’s picture

Title: Recurring fees pane gives 500 error after update to rc3 » remove the use of the uc_order_admin

Ok, not sure if we change this here to use the ubercart view? create our own view for this page? or just remove this functionality altogether.

This will obviously require us to ensure everyone is using a current version of ubercart 7.0-rc3+

tr’s picture

@univate: In your .info file, use:

dependencies[] = uc_cart (>=3.0-rc3)
longwave’s picture

I would suggest supplying a view for whatever that page used to display, if possible. You shouldn't need to specify a dependency, a replacement view should work with rc3 and earlier versions.

longwave’s picture

Alternatively you could just copy the old functionality from uc_order into uc_recurring, as it won't be returning to Ubercart core.

SeanA’s picture

rickmanelius’s picture

Just to clarify for myself, this is found here: admin/store/orders/[order_id]/recurring and still active.

rickmanelius’s picture

Just looking at the module itself, it looks like the process to convert to views would entail: Creating new fields and filter handles and then providing a default view with a built in filter based on user id. Correct?

boon4376’s picture

I am having this problem as well. Has anyone come up with a solution?

Thanks,

dcbartlett’s picture

@boon4376, As of current, the development branch still does not support the views for this. This renders "admin/store/orders/#/recurring" as a error 500.

I will look into what needs to be done to have this working, as i too need this to work. I will post back with my finding and possibly a proposed patch.

marcjohnson’s picture

I am seeing the same issue. Any updates on creating a new view, or copying old functionality from uc_order into uc_recurring (#8)? Thanks.

univate’s picture

Status: Active » Fixed

I have added the function here, although renamed it uc_recurring_order_admin

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.