Quick Updates plugin [support]

[paulm]

Whilst sorting by manufacturer, QU actually appears to be sorting the data by manufacturer_id, but displaying manufacturer_name.

In recent versions the above can be fixed by changing:

  if(QUICKUPDATES_MODIFY_MANUFACTURER == 'true')
    $output .= zen_quickupdates_table_head('m.manufacturers_id', TABLE_HEADING_MANUFACTURERS);

To:

  if(QUICKUPDATES_MODIFY_MANUFACTURER == 'true')
    $output .= zen_quickupdates_table_head('m.manufacturers_name', TABLE_HEADING_MANUFACTURERS);

While checking this I noticed the categories sorting has the same "problem". In addition to that the categories/master_categories switch does not alter the sort order (an issue I introduced myself). Both these sorting issues are less easy to fix than the manufacturer sorting and I will leave it as it is. Maybe only changing the text, so it says it sorts by id i.s.o. by name, is the best option ftb.

@Louis: thanks for letting me now about the purchase price enable fix :-) I think I removed it because I wanted to move that setting from one file to another or to the sql, but got interrupted and forgot to re-add it.

[qhome]

I want to first say thanks for this contrib, and wondered if you would have any interest and applying this to the attributes area.

The idea would be that on the attrib controller page, where you have your product selected, and you might have 5 options for that product listed there. Instead of having to edit each option one by one, you could make it so you can edit them all like quick updates does now, and have one update button to update them all.

Any interest? I thought about trying it using your existing quick updates file and modifying it, but there is a bit more there than I am comfortable with.

[paulm]

I want to first say thanks for this contrib, and wondered if you would have any interest and applying this to the attributes area

I think it would be great, but I doubt if the current quick updates code would help much to achieve this. Quick updates is designed to update "one to one" product relations only. I would like to rewrite it to handle "one to many" relations but that's not as easy as the "one to one" (or at least it is not easy to me ;-)). Actually that is one of the issues I am having currently trying to write a new quick updates version.

I think my next version will still be limited to "one to one" relations (like all products table columns are for example) to keep things simple.

[paulm]

I *think* I am quite close to releasing a new beta version. It will have a lot more *potential* possibilities. I am not sure yet what will be added in the next release though (but it won't be attribute and/or option editting I am afraid).

The largest part of the main engine is rewritten and that is why a I am looking for beta testers (who have some experience with programming and/or Zen Cart). It's probably not wise to try this beta on live shops!

So if you got a Zen Cart test install ready, and some spare time (and know you what you're doing) please sent me a PM with your e-mail address, and I will mail you the next beta (probably in a week or so).

[ingenuitor]

Hello do you happen to have an update for 1.3.7?

[paulm]

Hello do you happen to have an update for 1.3.7?

Is there a problem with 1.3.7?

[paulm]

I want to first say thanks for this contrib, and wondered if you would have any interest and applying this to the attributes area.

qhome, I just stumbled on the "Improved Attributes Controller" by bunyip http://www.zen-cart.com/forum/showthread.php?t=36671 doesn't that already do what you are looking for?

[qhome]

qhome, I just stumbled on the "Improved Attributes Controller" by bunyip http://www.zen-cart.com/forum/showthread.php?t=36671 doesn't that already do what you are looking for?

Well it's not the adding of the attributes to the attributes controller that I am referring to. I may have explained it wrong before. Its just the way they are listed. Quick Updates would probably work properly the way it already is, if I just updated the page form to take multiple updates at once like you did with the products.

Take a look at Catalog->Option Name Manager. Assuming you have 5-10 option names, see how they all have edit and delete buttons, and to change any part of them you would need to click on the edit button and bring up the edit page. Very similar to how the normal order updates work before you made Quick Updates. I'd like to make that part all open to edit all together.

Now look at Catalog->Option Value Manager, same thing here. Multiple edit delete buttons instead of just leaving them all edit boxes and one update button.

Now with that in mind, look at Catalog->Attributes Controller. Assuming you have a few options associated with the product, you see again there are multiple edit/delete buttons. These could also use the same method of allowing multiple changes at once. This is different than assigning attributes to a product. In this case, they are already assigned, I just want an easier way of changing their sort order and prices, however, leaving the color coded legend part the way it is. Just edit price, prefix, weight, prefix, sort, & discount.

[harry2cool]

Hi,
I have the older version of Quick updates, some questions

1) Will installing the .sql file of Quick updates again cause any problem.

2) My tables havea zen_ prefix, is this acceptable with the package included.

Please let me know asap so that I can update "Quick Updates" .

Thx

Harry

[paulm]

@qhome: thanks again (I assume you received my PM) for you explanation. By itself I think it's very interesting, but my time (and knowledge...) is limited and I don't think I will have time soon to work on it.

@Harry: I don't know much about the older versions, but I think it's best to totally remove the old quick updates files before you install the new version.

The new sql file should automaticly remove the old quick updates settings and install the new settings. If you paste the sql into the text area of the zensql tool, the prefix will be added automaticly.

Of course you better backup first!

(The version I am currently working on is delayed again. If it will ever be released it will probably be a separate 3.x alfa or beta version or something. If anyone is interested to work on the code you can send me a PM and I will see if I can zip a temporary version.)