CMS Made Simple Forums

[SOLVED]

There is an issue in Orders 1.13.1
http://dev.cmsmadesimple.org/bug/view/7859

[/SOLVED]


I'm having an issue setting up (any) shipping modules for Orders 1.13.1 (CGEcommerce 1.3.9)

I think it's related to the template for the shipping form (under Orders > Templates), which is empty.

The 'Orders/templates/orig_shippingform_template.tpl' file is empty and I can't find one going back through old versions of Orders in the forge.

If anyone could provide one (a default shipping form template), or an example so I can test, it would be much appreciated.

Or if someone can confirm whether or not I need one, that would help too.

I can't get the template vars due to the issue itself, as the page where shipping details should display won't render.

The Issue

The issue is (for any one interested or having the same problem):

When proceeding from 'checkout' (where your billing / shipping details are shown) to 'shipping', the page renders from the </__body> tag and stops when it processes the {Orders} smarty tag.

The only output is:

Debug: (0.275149) - (usage: 13585816) - (peak: 13627824)

Which is where the {Orders} tag seems to break (which is why the header isn't rendering)

Turning debug on in the config doesn't change anything.

Things Tried

~ Tried using different shipping modules, each of which give the same error
~ Looked for similar bugs in the forge and forums, tried a few patches, no effect
~ Tried adding different things (headings, paragraphs) to the 'Shipping Form Templates', no effect
~ Tried clearing the cache, sessions, cookies
~ Tried setting the shipping form page in Order>Preferences to different pages and also 'none', no effect
~ Tried unstalling and reinstalling from fresh tar files

Thanks in advance if anyone has any suggestions,

Regards,

Mikey

how did you solved the issue with the empty shipping form template ?
i have installed Orders 1.13.2, already looked around the forum can not find anything about it !

thnk you to explain.

Kind regards Peter

Hi Peter,

As there was a bug, I simply went back to using the previous version (1.13).

I've yet to try version 1.13.2, although the bug I raised was marked as fixed.

I will try and get time to test the latest version over the weekend and see if I can reproduce the issue.

1.13 is a stable version however, you could comfortable use that. It's always worth testing upgrades on a separate local install before moving to production (if you don't already).

Regards and best,

Mikey