Quick Updates plugin [support]

yes it works,
thanks a ton paulm

I am glad it did the trick, and thanks for letting me and other users know it did :-)

I am still working on a new 3.x version, but I need some beta testers.

Download: http://www.beterelektro.nl/zen-cart/index.php?page=quick_updates (stable versions, if available, will of course be uploaded to the Zen Cart downloads section)

Basic tests have been done on a 1.3.6 and a 1.3.7 shop, but it's not really recommended for live shop usage yet.

Most changes are not visible for the user (code). Currently it does not include an sql file and there are no db admin settings (so files need to be editted to change the default configuration).

Some new features are:

-a lot more product data updateable/viewable now (columns of the products table)

-basic search function

-add specials, edit special prices and status (not start and end date). Needs GV check to be added!

-quickly switch on/off columns for view/edit

-dramaticly less update queries needed per update (depending on what's updated)

-highlight of "0 fields" (using CSS of course), for example highlights 0 weight and "no manufacturer" and "0.00" price, etc

-highlight of last editted products

-switch between horizontal (=normal) and vertical tabbing

-added "bottom header" (no need to scroll to the top of the page to check what you're viewing/editting)

But remember: it's beta, so be very carefull and backup your database before each usage! (if you decide to use it on a live shop anyway).

Todo: a lot! (maybe later)

Forgot to mention:

feature:

-now it's possible to change the sort order of the quick updates columns

known issues:

• price markups may act a bit weird excluding tax (currently configured for nice inc. tax prices only)

• trying to update columns like products margin or purchase price will result in SQL error messages, if you don't have these columns. (so you need add these to your database, or disable them for quick updates)

Quick updates is very powerful and flexible, very nice job.
I'm considering using quick updates in a different manner and need your advice.

What would need to be done in order to have quick updates display/edit the line items from an order? This would give the customer the ability to make corrections to their order. I'm thinking QU could fire up from the order confirmation email which will pass the order number. Quick updates would retrieve the products_id and products_quantity from order_products and pull the remaining data from the products table, display/edit those items and then update order_products and most importantly update the products table with the changes from that order. Updating the order_total is preferred but not a requirement (at this time).

So a quick recap is - QU fires up via url with order number parameter, display/edit order line items, update products and order_products, recalc order totals (preferred not required).
Do you think QU would be a good tool for this type of use? If not, please inform me and you can stop reading.

If you think QU is a good candidate then...
How about adding additional items to the order, selected from the products table?

That’s it for now. I know this is an odd request and modifying a completed order is a no no. But this will close the loop for my system, allowing the customer to correct discrepancies in their order. I can live (for now) with the detail not equaling the totals, as long as the products table is updated.

When you get a chance please let me know your thoughts, or if you have any questions please do not hesitate. Sorry for replying to your update notice but I could not find where to start a new thread.

Thanks,

Bill Kenny

Hi Bill Kenny,

currently I am rewriting quick updates, and hopefully it will be possible to view/edit more db tables some day using quick updates. But I think editting orders is something different and quick updates won't help much for that.

You could take a look at the Order Editor contribution (which is included in Super Orders). It's not written to allow customers to edit their own orders, but at least it's made to edit orders.

Greetings Paulm,

Thank you for your reply and directing me towards super orders. Good luck on your upgrade of quick updates.

Bill

Hey paulm,

Great mod!

I wondered what you meant by "Needs GV check to be added!" on the new specials functionality. It isn't working for me at the minute and I am going to dig in and see what the problem is, but wondering if this has something to do with it.

Cheers,
Carey

I found the problem.

If you only show the field for specials price including tax then it gets ignored. The same goes for the normal price. You need to have both fields showing on the form.

Also the specials doesn't support a percentage change, only a value.

Regards,
Carey

Hi Cary,

the warning:

Needs GV check to be added!I added because he script needs to check that no discounts are assigend to gift vouchers. If you make sure yourself you don't apply special prices to gift vouchers it's no problem.
BTW: the code for this is not complicated, I just got about 1000 uncomplicated (and some complicated) code edits to go before it's finished :-) (and of course it's never really finished..)

But you should be able to add/edit/remove/status update specials I think. Or least the latest beta does (but I really can not release that one publicly).

If you mean you can't do markups on the specials yet, then it is correct. Also not difficult, just one of the many todo things. The main reason I did not add it yet is that I was thinking about adding a more general markup "vertical update" feature. So that it would also become possible to markup/update all displayed products names or weights or whatever, in one go. But maybe I just want to much.... ;-)

Oops, did not see you last reply before posting mine.

I will check for the possible tax/markups issue, when I do tests next time, but I can't promse anything.

Using 2.03 under 1.3.7

I just noticed that if I have a category with only 1 item, it does not show up when I bring up the quick update window.

Is there a fix for this?

Liking this very much so far. Looking forward to ver 3.

@chadderuski: I did some tests, but I can't reproduce the issue with 1 product in a category in 2.03 (which does not say it's not possible, it certainly is). Do you have it with any 1 product in a cat? Does it happen within both the master cats and linked cats view?

@kelvyn: the higher number indicates its newer, but it's not better by definition. v3.0-beta-2 is probably more stable and better/safer for practical usage, that is why I left it there after releasing newer versions. And v3.0-beta-6.1 should actually be replaced soon (it has quite some bugs for sure). And it looks like v3.0-beta-2 misses some files :blink: (probably it's best to use it as an upgrade for 2.03).

I think I will start a new thread about 3.x (which I already should have started some time ago). Because most issues with, and fixes for, 3.x will be totally unrelated to any 2.x version.

Hi Paulm,

With the specials tax issue it is just a case of in the big switch it is checking for the specials field that does not include tax - just needs a bit of logic here. I haven't done it as I can work around it.

The way specials are done is a bit of a pain for me anyway. Unlike the salemaker, it doesn't record the actual type of offer you are doing - just the ammended price. So if you update the base price the special doesn't change.

This causes me a problem because I use global update and would like the special prices to be in sync with the imported prices.

But this is both irrelevant and nothing to do with your excellent mod!

Thanks again for the great contribution.

Hi Paul - okay, this is like when you take your car to the vet and it totally behaves... LOL. Now I cannot reproduce it, but I am CERTAIN that it did do it. Should I be using "Master Category View" for everything. I do not think I have linked categories yet, and that was the default view I had when I noticed this.

I have a feature request:

The ability to add/edit extended price breaks. I have been editing the main price in your module, then jumping out to edit extended pricing. This would help data entry flow.

Any plans on adding text or sql imput/output?

Can't wait to see what you do in version 3!

Does this mod allow price updates of attributes too? I would like to find a solution that will list all attributes in a table and the client can just go through and update instead of chooing each one individually.
Thanks

Do you have an uninstall procedure?

I installed 3.0 beta 2... which seemed to work, but then noticed some "odd" things like manufacturer's id changing. So I uploaded the 2.03 files and re-ran the update.sql file, and now it no long works. Getting error:

Fatal error: Cannot redeclare zen_quickupdates_table_head() (previously declared in /home/royalind/public_html/store/admin/quick_updates.php:32) in /home/royalind/public_html/store/admin/includes/functions/extra_functions/quick_updates.php on line 14

any ideas?

Ah! Found the commented section in the quick_update.sql and ran that. Also made sure I deleted both version's of files (2 and 3) on server before reloading and then reran sql patch. Appears to be working now.

Due to the problems with the GOOGLE FROOGLE FEEDER handling product_type, I was wondering if it would be easier if the QUICK UPDATES had another blank input field for setting a custom Google product types that would be stored in the SQL as product_type?

I don't know anything about GOOGLE FROOGLE FEEDER (I think it's US only, isn't it?) and it's product_type handling. But quick updates does not add any input fields because quick updates is designed to update existing fields only, not add new fields.

If you need a new field you need to add it to your database, and if you want to update that new field using quick updates 2.x you would need to update the code for it as well.

And if GOOGLE FROOGLE FEEDER is a contribution I think you should ask about this issue in the support thread of that contribution (or start one yourself).

I'm trying to keep the contributions compatible. We've found a work around for the product_type in Google Froogle. But if we were to create such a field, then the quick updates would also need to match it. So far, no need... yet