Closed (fixed)
Project:
UC Recurring Payments and Subscriptions
Version:
7.x-2.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Dec 2011 at 18:25 UTC
Updated:
9 May 2012 at 23:40 UTC
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
Comment #1
tr commentedRecurring fees are provided by the uc_recurring module.
Comment #2
shazar commentedBut wouldn't this be a problem with Ubercart as it is the update that broke it?
Comment #3
shazar commentedThe error is:
PHP Fatal error: Call to undefined function uc_order_admin()
Did Ubercart remove this function?
Comment #4
longwaveThe 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.
Comment #5
univate commentedOk, 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+
Comment #6
tr commented@univate: In your .info file, use:
Comment #7
longwaveI 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.
Comment #8
longwaveAlternatively you could just copy the old functionality from uc_order into uc_recurring, as it won't be returning to Ubercart core.
Comment #9
SeanA commentedMarked #1283352: Replace the use of uc_order_admin() with a view for the order recurring fees admin page as a duplicate of this issue.
Comment #10
rickmanelius commentedJust to clarify for myself, this is found here: admin/store/orders/[order_id]/recurring and still active.
Comment #11
rickmanelius commentedJust 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?
Comment #12
boon4376 commentedI am having this problem as well. Has anyone come up with a solution?
Thanks,
Comment #13
dcbartlett commented@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.
Comment #14
marcjohnson commentedI am seeing the same issue. Any updates on creating a new view, or copying old functionality from uc_order into uc_recurring (#8)? Thanks.
Comment #15
univate commentedI have added the function here, although renamed it uc_recurring_order_admin