Major error.. OPAY screen payments item not working.

[alexboyer]

Hey all,

After installing several sebenza modules, and an emporium plus module, our OPAY screen is now showing this error:

Runtime error in /mm5/5.00/modules/component/cmp-mv-paymentfields.mvc @ [0000000a:0000008e]: modules/component/cmp-mv-paymentfields.mv: Line 97: MvDO: Unable to open '/mm5/5.00/': Is a directory

The modules were:
Emporium's Basket Master

Sebenza:
Wishlist/Gift List
Product Suggestions
Order Tracking/History

Of course nobody can check out now. Any ideas about how to fix this?

Thanks!

[wcw]

What items do you have assigned to the items list of the OPAY page?

[alexboyer]

head
hdft
store
messages
payment
tax
states
countries
body
navbar
colors
fonts
buttons
basket
customer
html_profile

[wcw]

You should be able to rule out the 3rd party modules. None of them are assigned to that page.

I assume you have edited the opay page. You could try recalling an older version of the opay page and then update that template and see if it fixes it.

You could also try unassigning all of the items, click update, then assign them back one at at time and clicking update and testing.

[alexboyer]

It's the payments item... Any ideas about how to fix it? Can I copy it from my other store?

[wcw]

It does not make sense that the file would suddenly become corrupt.

Does it give you the error no matter what payment method you select?

If you are on a Miva saavy host, ask them for help.

[alexboyer]

I agree it doesn't make sense... Yes, it doesn't matter what payment method I choose.

Unfortunately, my host isn't Miva savvy...

The page has been edited, yes, but not since February. It has been working (I know it worked, I've got orders in the system) up until Thursday which is when I installed all those modules...

[alexboyer]

I tried unassigning all items, then reassigning them one at a time. When I reassigned the payments component, it put that error back in there.

Additionally, I recalled the original page that shipped with Miva. Same problem.

Additionally, I overwrote the cmp-mv-paymentfields.mvc with a copy from my other working store. Same problem.

At this point, I don't think it's the component module itself, but I'm not sure where else to look...

If I could only see what it's trying to load on line 97....

[alexboyer]

Nevermind... I'm an idiot... It was a custom modification to the system I made. The OPAY Screen wasn't getting the PaymentMethod value passed to it therefore.... Yeah...

Anyway, thanks and sorry for the trouble.