Several problems following upgrade to 2.1

[GChambers]

Hi,

I have encountered the following problems / issues after upgrading version 2.1

1) Order confirmation e-mails are no longer being formatted correctly - they appear to be plain text notifications, with no HTML formatting. For example the vendor logo no longer appears in the notification, the order summary table is no longer formatted with header rows in . (N.B. this is for notifications to both clients and site admin). Invoices, on the other hand are still being formatted correctly.

2) What has happened to the ability to use the legacy renderer for the order summary table - it no longer appears on the order form details tab? I was using it, at your suggestion, to resolve an issue (http://www.nbill.co.uk/forum/index.php/topic,2185.0.html).

3) One one particular order form I am now getting a SQL syntax error that I was not getting before (see attachment).

Regards,

Gordon.



[attachment deleted by admin]

[netshine]

In answer to your 2nd question, that option has been moved to the page properties (so you can control each page individually rather than requiring the whole form to be affected).

I am looking into the other 2 issues - I might need you to submit a support ticket giving me access to your Joomla administrator, but I will see what I can figure out on my own first. I will reply again asap.

[GChambers]

Thanks for looking into it.

Re the 2nd question, I have now found that the workaround of using legacy mode to render the order summary table no longer works. i.e. the original problem was that if the table expanded due to very long text area fields, the table was crashing into the submit button at the bottom of the page. I have checked that all pages on my order form are set to 'Render in a table' - but the original problem has returned 

Regards,

Gordon.

[netshine]

That is odd - I think I will need Joomla administrator access to look into that, so please submit a support ticket.

The only reasons I can see why a plain text email would be sent instead of an HTML one for order confirmation, would be if the wrong value was set on the vendor record for the order email template, or if the email template file did not exist.

Still to look into the database error when saving an order...

[netshine]

The database error is occurring because the shipping ID, which should be a number, is attempting to be saved as a string of text (the name of the shipping service). I just ran through a test using a shipping service, but I did not have the same problem. Do you have any custom code on your order form or anything that could be setting the name of the shipping service?

[GChambers]

OK I will raised a support ticket for the legacy rendering problem.

Re the shipping ID, in the field options dialog for this control, I have set both the value AND description fields to the same text string. I thought this was OK as the help text for the value field says "...this can be different to the text or value that is displayed to the user" - so I thought it was also OK for it to be the same? In any case, I have changed it now to be a numeric value - but the SQL error still occurs. BTW - on other order forms that also have the same shipping field, also with a text string as the value, I do not get the SQL error?

Gordon.

[netshine]

The problem appears to be that the upgrade did not complete successfully - not all of the files were uploaded/overwritten as they should have been, so you have some files from version 2.0.9 and some from 2.1.1 (for example, the image files for the new 'fees' and 'housekeeping' menu items are missing). Please try re-applying the upgrade, and if you use the manual upgrade patch to do so, please pay special attention to any FTP errors that occur while uploading - it might be that some files need to have their ownership or permission settings modified so that they can be overwritten with the latest version.

[GChambers]

OK - After trying to FTP the files several times, and getting errors each time I finally realised that it would probably be better to FTP the whole zip file and unzip it on the server. Of course this is what I should have been doing all along  . Result:  successful upgrade and no more formatting issues on either the order summary page or with the notification e-mails. You can close this support ticket now thank you.

Regarding the SQL error - this was also my fault - sometime during development I had forgotten that there was a tie between the shipping id's on the shipping rates configuration page and the  corresponding value in the edit field on the order form - so I set those to match the descriptions. I still don't know why my other order forms continued to work with this change - but in any case, after changing them back to numerical values it all works fine now.

Thanks again for your tremendous support.

Gordon.