MM5.5 Features List

[William Davis]

Re: MM5.5 Features List

What about when you delete a product -its associated product images would be deleted from the srver as well.

We currently have this problem with our MM4 store and don't know what to do?

[Brandon MUS]

Re: MM5.5 Features List

What about when you delete a product -its associated product images would be deleted from the srver as well.

We currently have this problem with our MM4 store and don't know what to do?

In the past we have used the same picture for multiple products. As long as those products aren't broken, this feature would be okay.

[William Davis]

Re: MM5.5 Features List

In the past we have used the same picture for multiple products. As long as those products aren't broken, this feature would be okay.

Sorry that is not what I meant. Currently when you delete a product from Miva, the image still remains on the server. We never thought about that and we found out years later. Now we have tons of images we no longer use and paying extra storage for same every month. I thought it might be a good idea to add some type of check box asking if you wish to delete all images associated with this product at the same time -or something like that for MM5.

By the way, if you have any suggestions for MM4 -We love to hear it.

[1st Ergo]

Re: MM5.5 Features List

Rick,

I know you have discussed different skins being available for 5.5. What about different layouts with the click of a mouse? So if you wanted a category page to be 2 or 3 columns. Or you wanted to display the nav on the side and/or top of the cat page. etc.... This would save a bunch of time for store owners.

Also, what about a pop up wysiwyg editor for product/cat descriptions, headers, footers, etc...

Thank you
David

[tbogus]

Re: MM5.5 Features List

Sorry that is not what I meant. Currently when you delete a product from Miva, the image still remains on the server. We never thought about that and we found out years later. Now we have tons of images we no longer use and paying extra storage for same every month. I thought it might be a good idea to add some type of check box asking if you wish to delete all images associated with this product at the same time -or something like that for MM5.

By the way, if you have any suggestions for MM4 -We love to hear it.

We had this problem with our transition to M5 from M4. It was quite a pain - but in the end, it's been a very methodical process - if you think about it - you already have the product/image associations in your products.dat and/or custom fields. What we did from there - we manually removed images - in our case it was in large chunks - granted we had the advantage of working a dev site - where we copied our images...

Tim.

[Capt'n Morgan]

Re: MM5.5 Features List

I'm excited about the integration with DW!
It's a lot of extra work to copy and past code b/t MM and DW currently. My biggest peeve is when DW convoludes the code and sends the miva tags out of whack. I'm using MX, not sure if that happens with new versions. Thanks God MM is smart enough to know when the tags are mis-matched before saving.

[Gilbert]

Re: MM5.5 Features List

DW doesn't with the newest version (for mac) – thanks God

[William Davis]

Re: MM5.5 Features List

We just got DW -don't have any ideas what you folks are talking about. Please clue me in. I just finished installing DW and waiting for my host to setup our new MM5 store.

Second, whats the best was to learn DW, watch the video that comes with ti first or just dive in DW?

[Gilbert]

Re: MM5.5 Features List

The MX version of DW Mac would "delete" some MIVA tags when saving the file or when cutting and pasting the code back to MIVA. Extremely odd behaviour that does not happen any-longer.

Dive – though the interface remains odd for Mac – with the manual next to you (or the online help) that's at least the way I did it admittedly long time ago.

[William Davis]

Re: MM5.5 Features List - Enhancement Suggestion

Many feeds now request <lastmod> (last modified) data attribute, however MIVA does not track this information. With the advent of feeds and their popularity, it may be a good idea to incorporate a dynamic "date added" and "last modified" fields that would automatically populate itself when a category and product, etc... pages are added and/or modified.

Providing this information, would allow search engines to spyder pages that have been added since they last spydered the site. Thus time allocated to spyder site would be on new and updated pages versus old content that has already been spyred and save bandwith, etc..

[RayYates]

Re: MM5.5 Features List

I second that. I would love to see time stamps fields all over the place.

[K Series Parts]

Re: MM5.5 Features List

Would it be possible to allow a single category to be assigned to multiple parent categories?

[tbogus]

Re: MM5.5 Features List

Would it be possible to allow a single category to be assigned to multiple parent categories?

I would second this one. 'Recreating' content is not a practical approach to having a hierarchical structure.

It's doable, but definitely not practical.

Tim.

[Leon]

Re: MM5.5 Features List

I would also like to see an easy way to duplicate a product without having to re-enter everything from scratch. We often add one or two new items; importing is too much hassle and they may be 90% the same as another item, so a "make copy" function would be great.

[RayYates]

Re: MM5.5 Features List

I'd like to see an extra field added to the CategoryxProducts table so that a category could be designated as the primary category for the product.

When displaying a product that has been assigned to multiple categories and the category is unknown (e.i. the customer clicked on a search result, short link or product list etc.) it is sometimes necessary to lookup the category (breadcrumbs for example). This can lead to ambiguous results since the first category assigned is the one returned.

Designating a primary category would solve the problem and also allow the category tree to open to the most appropriate location even though no category was specified.