Miva Merchant 10.00.x Bug Reports

[jpatrickm]

It’s rare but occasionally I need to access or edit some info on mobile. The interface doesn’t allow a way to actually click into a selection. Touching an item selects it but there’s no way to edit it (that I can see). Example is Feeds... you can’t actually edit the underlying feed, only select it.

[Brennan]

jpatrickm There is a bug on touch devices causing this. We're working on addressing.

[afiumano]

Did you make sure all of the text field areas have been narrowed? Yeah, it's a real pain to have to go into each tab.

So I just realized you have to go into even 'collapsed' sections and narrow those text areas as well. This is definitely too time consuming and hopefully a fix will be implemented...

[Beefy Nugget]

Brennan was the bug with multi text custom fields and the search fixed in this latest update? 10.00.05

[Brennan]

Beefy Nugget No it did not make it into this release. It is planned for 10.01.00 which is the next release.

[InvincibleRecordings]

The new Version Miva 10.00.05 looks good but I cannot find any button to upgrade to it. Guess I am computer challenged.

[delcorsets]

The new Version Miva 10.00.05 looks good but I cannot find any button to upgrade to it. Guess I am computer challenged.

InvincibleRecordings Make sure that you are logged in as an Administrator user with 2FA - otherwise you will not see the option to upgrade.

[InvincibleRecordings]

Yes, good call, I am Admin so it should work. I was just on MIVA tech support and they cannot find the upgrade link on my site as well. So we have a ticket in to see whats going on.

[InvincibleRecordings]

FIxed - Victoria Finn in support found the fix very fast: It looks like your store was set to check for upgrades weekly, I went ahead and changed the settings to check for upgrades at every login. Thanks Victoria:)

[afiumano]

I created a dev branch and downloaded the theme.js file from the dev branch: mm5/b02/themes/colossus/ui/theme.js. I made an edit and reuploaded the file to the same place, but noticed no change was made when previewing the branch. If I made the change on the Production theme.js file, then my change was implemented on the dev branch. I thought that js was specific to the branch?

[Brennan]

Are you sure the file paths are correct. The JS/CSS should be specific to the branch you're working on.

[afiumano]

I did not edit any file paths. I simply created the branch from admin and then FTP'd down the files to edit. I don't quite know how to verify. The theme.js file is called in with the scripts.js file like this: $.loadScript(theme_path + 'ui/js/theme.js', function (). How do I determine what the "theme_path" is?

[RTHOMASDESIGN]

When navigating to the categories tab under a product. The "Parent Category" column does not show any relevant data -- it works as intended in other lists (category etc.).

[Eric Foresman]

When navigating to the categories tab under a product. The "Parent Category" column does not show any relevant data -- it works as intended in other lists (category etc.).

Hi RTHOMASDESIGN

Thanks for the heads up, I have filed a bug on this issue.


-Eric

[Kent Multer]

Another problem with the template version history: when you turn it on, the "Select One" option is selected by default. So you have no way to find out which version is currently in use. It's not always the latest one. If you make some changes and then decide to revert, you have no way to know what version to restore.

Also, if you want to see or use the history, you have to keep re-enabling it every time you update or reset the page.

Is there any plan to fix these in a future update? I find the version history to be an important tool, especially when more than one person is working on a store (which happens quite often in my experience). I'm surprised that you felt the need to hide it away, when there's plenty of unused white space all over the page. IMO you should be encouraging people to use it, not making it more difficult.

Thanks --