Author Topic: buildXML error  (Read 594 times)

Offline dynorodney

  • Sr. Member
  • ****
  • Posts: 120
    • View Profile
buildXML error
« on: 15/March/2010, 05:53:15 PM »
Hi

Just got the error below. Any thoughts on the cause?


Page: https://www.domain.co.uk/cms/index.php?option=com_nbill&action=profile&task=update&Itemid=98
Referrer: https://www.domain.co.uk/cms/
Error Log ID: 28
Error Message: Parameter 1 to modMainMenuHelper::buildXML() expected to be a reference, value given File Name: /home/user/public_html/cms/libraries/joomla/cache/handler/callback.php
Line Number: 99
PHP Version (and OS): 5.3.2 (Linux)

Thanks

Tony

Offline netshine

  • Administrator
  • Hero Member
  • *****
  • Posts: 4,984
    • View Profile
Re: buildXML error
« Reply #1 on: 15/March/2010, 07:33:43 PM »
That error is actually coming from Joomla, not nBill - nBill is just reporting it because it happens on a page that is processed by nBill. See http://forum.joomla.org/viewtopic.php?f=199&p=1811142

Offline dynorodney

  • Sr. Member
  • ****
  • Posts: 120
    • View Profile
Re: buildXML error
« Reply #2 on: 15/March/2010, 10:31:45 PM »
Ah thanks

I saw the joomla reference but because nBill was reporting it I thought it might be nBill making the call. Our techs applied 5.3 earlier today or yesterday I think. I shall reset to 5.2

Your a good un - but you know that

We are now on v2 btw and Ive got our PDF invoices working again  ;D. Even though this wasnt the reason for it failing originally I have found out today that html2pdf software you  use as a plug in doesnt seem to work with https (I know this isnt your code) but by running the admin area in http Ive got it working again

Tony

Offline netshine

  • Administrator
  • Hero Member
  • *****
  • Posts: 4,984
    • View Profile
Re: buildXML error
« Reply #3 on: 16/March/2010, 08:24:29 AM »
I run it over https ok on one of my own sites.  ???

Offline dynorodney

  • Sr. Member
  • ****
  • Posts: 120
    • View Profile
Re: buildXML error
« Reply #4 on: 16/March/2010, 03:47:19 PM »
whey hey - got it working with https - it was a no-cache pragma header that was stopping IE from showing the PDF