Seeking confirmation of an issue, please

[WSO]

Over the last few days I've been frustrated and concerned about a few issues I've encountered. Please read below and if you have the same setup and are in a position to test this, please give me some feedback. I would really appreciate it. :)

Of course, have a backup ready if you do this on anything other than a test install of Miva Merchant 5.

Start with this (yes, I know about the speed issues with 5.04):
Production Release 2
MIVA Engine v5.04
Database API: mivasql


Upgrade to this:
Production Release 2
MIVA Engine v5.06
Database API: mivasql


Then edit ANY user interface page. For example, simply add a blank line to the top of the SRCH (search) page, and click update. Is the blank line still there? It isn't for me.

Then go to the store front and check the search page. Is it broken? By broken I mean it appears the browser is sent the actual page template data and not the interpreted data. Basically, it isn't getting run through the Miva Engine. If you do a View Source you can see the Miva Merchant markup language codes, etc...

So far every store that is PR2, upgraded from v5.04 to v5.06 and using MivaSQL will break if any change is made to any template page. And using the template recall feature to revert does not fix the problem. It is possible that changes to other areas would trigger a failure, but so far I've only tested the template pages.

I don't think PR2 matters as I've tried upgrading to PR3 both before and after editing a template page and I still get the same result.

I do not have this problem on our newer stores that use MySQL. Unfortunately a few of our stores were installed using MivaSQL when Miva Merchant 5 first came out. We know better now.

I'm just looking to see if anybody can replicate this so I know if I need to just bite the bullet and begin migrating these stores from MivaSQL to MySQL or if the situation is salvageable by correcting something on my end.

Lastly, are their any known problems downgrading from v5.06 to v5.04 or even v5.03 once the store has been running under v5.06?

FYI, this is running under FreeBSD.

Thanks again, I appreciate the help.

-Chris
WSO

[WSO]

UPDATE:
I've just confirmed that this same problem occurs under this setup:
Production Release 3
MIVA Engine v5.06
Database API: mysql

So it seems to be more related to the MIVA Engine v5.06 upgrade from v5.04 in general as opposed to the Database API or Production Release in use.

Interesting side note... to get the store back to working order I only needed to restore the Merchant5 data directory. I didn't need to restore the MySQL database.

Anybody seeing anything like this?

Thanks,
Chris
WSO

[WSO]

UPDATE 2:
I'm going to keep posting. It helps me keep my troubleshooting straight and maybe someone will notice something that might unlock the key to this issue. Or maybe it will help somebody in the future.

CORRECTION to my previous update. To fix the problem I needed to restore the mm5 scripts directory, not the Merchant5 data directory. Just posted that backwards, sorry about that.

Back to my test of editing the SRCH (search) page. You don't even need to edit it at all, I simply press the update button and the problem occurs.

The file that gets changed when you update the SRCH page is here:
mm5/5.00/templates/s01/srch.mvc

Original properties:
size: 4989
date: Oct 8 11:30

After edit (I just hit the update button, no changes):
size: 2350
date: Nov 2 14:08

If I replace srch.mvc with the original, the problem goes away. So I would have to assume there is something going wrong during the recreation of this file.

If you go to the search page from the front of the store while srch.mvc is broken all that gets sent to the browser is the contents of the SRCH template.

Sure seems like there is a problem with the Miva Engine v5.06, but I just can't confirm it.

Something else to note. I can see other changed template .mvc files that were created while v5.04 was installed and they seem to be fine. Just more evidence that there might be something up with v5.06.

Sure wish somebody could test this out for me on their machine.

Thanks!
-Chris
WSO

[WSO]

I don't know if this thread had anything to do with this, but a bug report and quick fix has been posted about this issue.

http://extranet.miva.com/forums/showthread.php?t=4857