Quick Updates plugin [support]

I am using 1.5.3 and that does seem to be the issue. When installing the configuration keys, I get:

[21-Jul-2014 09:54:23 America/Chicago] PHP Warning: mysql_insert_id(): Access denied for user 'nobody'@'localhost' (using password: NO) in /home/miashop/public_html/zencart/ADMIN_NAME/includes/functions/extra_functions/quick_updates_functions.php on line 16

jeking:

I am using 1.5.3 and that does seem to be the issue. When installing the configuration keys, I get:

[21-Jul-2014 09:54:23 America/Chicago] PHP Warning: mysql_insert_id(): Access denied for user 'nobody'@'localhost' (using password: NO) in /home/miashop/public_html/zencart/ADMIN_NAME/includes/functions/extra_functions/quick_updates_functions.php on line 16

Yep this is a mysqli thing, and I am not sure of the correct replacement for mysql_insert_id. You can try mysqli_insert_id and see if that works.. but I am not sure if an additional change is needed as well..

DivaVocals:

Yep this is a mysqli thing, and I am not sure of the correct replacement for mysql_insert_id. You can try mysqli_insert_id and see if that works.. but I am not sure if an additional change is needed as well..
Or, to ensure future compatibility, you could use the $db->Insert_ID () function to retrieve that last inserted ID.

lat9:

Or, to ensure future compatibility, you could use the $db->Insert_ID () function to retrieve that last inserted ID.

So would the change from:

        $group_id = mysql_insert_id();

Look like this:

        $group_id = $db->Insert_ID();

Exactly! With the caveat that you'll need a

global $db;

statement if the processing occurs within a function.

lat9:

Exactly! With the caveat that you'll need a

global $db;

> statement if the processing occurs within a function.

and THAT's where you lost me..

Drat!!! JUST when I thought I was getting it..:laugh: going back to the lab to see if I can figure out the answer on my own.. :smile:
**
Edited to Add: **

So altogether now..:laugh:

function install_quick_updates() {
global $db;
$db->Execute("INSERT INTO ".TABLE_CONFIGURATION_GROUP." VALUES ('', 'Quick Updates', 'Quick Updates Configuration', '1', '1')");
$group_id = $db->Insert_ID();

    $db->Execute("UPDATE ".TABLE_CONFIGURATION_GROUP." SET sort_order = ".$group_id." WHERE configuration_group_id = ".$group_id);

if (function_exists('zen_register_admin_page')) {
if (!zen_page_key_exists('quick_updates_config')) {
zen_register_admin_page('quick_updates_config', 'BOX_CATALOG_QUICK_UPDATES','FILENAME_CONFIGURATION', 'gID='.$group_id, 'configuration', 'Y', 103);
}
}

Yes:clap:

lat9:

Yes:clap:

Well hotd@mn! :smile:

Hey Diva! You have a LAB?!?! LOL. I have a living room with too many computers! Got a letter from the electrical company telling me I use TWICE as much electricity as my neighbors. Go figure!

Anyway! I looked at your github updates...

Are you going to update the release for 1.5.3 here?
Will QuickUpdates still be backwards compatible?
Are you going to update the version number?

-chadd

Opps, my bad. I should have read back a few more pages. Confused myself ... my own experimental version of QuickUpdates is also v2.07! :p

Perhaps too late if you already submitted, but since you're dropping support for previous zencart version, mayhap a change to v3.0?

Just thinking out loud...

chadderuski:

Hey Diva! You have a LAB?!?! LOL. I have a living room with too many computers! Got a letter from the electrical company telling me I use TWICE as much electricity as my neighbors. Go figure!

Anyway! I looked at your github updates...

Are you going to update the release for 1.5.3 here?
Will QuickUpdates still be backwards compatible?
Are you going to update the version number?

-chadd
When I get some time in the next week I might update for 1.5.3.. If I do upgrade it, I have NO plans for backwards compatibility. It's JUST too much work and NOT worth my time/effort to maintain "parallell" versions of a module.. -- IMHO folks should simply UPGRADE and stop dinking around.. If they are STILL running <= v1.3.9 they REALLY need to upgrade and stop playing around..

I already updated the version number (v2.07)

That said I will only update my Github repo.. Not ready to submit it to the downloads section as there is still a MESS of crap in this module that needs to be cleaned up before it's ready to "release" IMHO (see below).. Some of these things I've already addressed in the Github repo (all that silly "popup" edit crap).. But this thing still doesn't properly work with the default editor, and the "Activate/Deactivate Commercial Margin" is not well well explained/documented.. Not sure if it works/doesn't work or WTF it's supposed to do..

Sources: http://www.zen-cart.com/showthread.php?41886-Quick-Updates-plugin-support&p=1228554#post1228554

DivaVocals:

Will be submitting this tonight..

History:
~ Fixed the installer files and corrected the admin page registration code (there were some inconsistencies that I corrected).
~ Correct typos, inconsistent punctuation, inconsistent capitalization usage, and the use of some very awkward grammar in the admin config settings
~ Re-ordered some of the configuration items to a more logical order (for example: moved the popup description edit next to the description on/off setting)
~ Added better instructions in the configuration setting for the popup edit to WARN shopowners that you should not activate the popup edit without activating the description display. (activating one without the other shifts the column headings so they do not match the data column)
~ There is a missing heading column when the description is turned off. Fixed code so that the column headings correctly display when the description display setting is set to false (last column heading is missing)
~ Dropped ALL support for Zen Cart v1.3.x. If you are running versions of Zen Cart prior to v1.5.x, you should install v2.06a
~ LOTS of cleanup of the look of the layout as follows:
+ Fixed the product description layout so it STOPS pushing the entire layout off the screen (there is a no-wrap style in the stylesheet)
+ Removed hardcoded text alignment from EVERYWHERE (if needed text alignment/layout/styling should be done in the stylesheet)..
frankly all of that hardcoded text centering did not look good and made the overall layout look dated
+ Removed a LOT of odd settings from the stylesheet (right alignment of the product description input field for example WTH???)
+ Added IDs and classes to support some of the layout corrections I made

KNOWN BUGS I DISCOVERED:
(C Jones 11-29-2013) While making the v2.07 changes/updates, a few things that need addressing with this module were discovered. I can't address/fix these items (above my skill level to fix), but they are worth noting here.
1. The popup edit feature is nice, but possibly over engineered.. The display of the store side view product description is wholly unnecessary IMHO. a simply edit button to open the popup window is really all that's needed for this feature.. Even IF the store side view of the product description is a feature that most users desire, it should be an admin configurable item to turn on/off the product description display AND it needs work as it certainly doesn't work consistently in my testing.. MANY of my clients product descriptions when the popup edit feature is turned on either did not display at all or only partially displayed.. (for example the last line of the product description is the ONLY thing you see) I won't even begin to cover the CSS conflicts that occur because of classes and IDs from the product description sharing the same names as this mods classes and IDs..
2. The editor dropdown doesn't work.. In my testing, it defaults to CKEditor (my client's default editor), yet the editor doesn't render for the product description field (which is where I'd expect to see it). Tried forcing the editor change by changing to the text editor and then changing back to CK Editor.. still no dice..
3. The back button on the product preview page SHOULD return you back to the Quick Updates product list.. Instead you are returned to the catalog product list..
4. No support for products priced by attributes
5. No support for SBA (ANY version of SBA)
**
FEATURES THAT ARE NOT WELL DOCUMENTED:**
I know that if I want to do a mass price increase that I have to activate the "Activate/Deactivate Commercial Margin". However this setting appears to do more, and it is not clear on what that is.. NO WHERE in the documentation is it clear what the "commercial margin" feature is or what it is supposed to "do". The help tip when I hover over the information icon in the UI shows this tip:
"Modify by commercial margin, if you check this box, your products will be stroked at the rates given. To stroke to 25%, means that the price is marked up of 33%"

The readme cryptically states:
"3) To make the products_purchase_price and margin feature work "products_purchase_price" (i.e. DECIMAL 15,4) and "products_margin" (i.e. DECIMAL 15,2) need to be added to your products tabel."

What EXACTLY does this all mean?? What is the purpose of this feature??

There is also code which appears to support wholesale pricing fields and NO WHERE in the readme is this functionality explained.

"Activate/Deactivate Commercial Margin" sounds like some long dead contribution... time for the weed whacker! I had a lot of that when I was cleaning up EasyPopulate ... what a tangled mess!

chadderuski:

"Activate/Deactivate Commercial Margin" sounds like some long dead contribution... time for the weed whacker! I had a lot of that when I was cleaning up EasyPopulate ... what a tangled mess!
That was what I was starting to suspect, much like the "order edit" features that USED to be part of Super Orders.. Okay weed whacking it is then!!:laugh: Do you have any updates in your version that are not captured in my Github repo??

DivaVocals:

That was what I was starting to suspect, much like the "order edit" features that USED to be part of Super Orders.. Okay weed whacking it is then!!:laugh: Do you have any updates in your version that are not captured in my Github repo??

Hi Diva,
Yes, but I'd have to look at the code again. I did add quantity min, quantity units, and then some custom custom fields (UOM, UPC).
Not sure now if Status and Sort Order were already in there now, but I see you have those too. I could have sworn that getting Status to work was a challenge, but you having it working smoothly.

Your description edit feature (no popup) is pretty nice. Much simpler. Did you remove the ability to browse for an image? I didn't seen that.

I thought about adding a delete check box, but then what do you do about linked products? Hmm... so I left well enough along :p

Oh, just fyi. It seems the "Uninstall" button doesn't work... ??

chadderuski:

Hi Diva,
Yes, but I'd have to look at the code again. I did add quantity min, quantity units, and then some custom custom fields (UOM, UPC).
Not sure now if Status and Sort Order were already in there now, but I see you have those too. I could have sworn that getting Status to work was a challenge, but you having it working smoothly.I think custom fields should NOT be included in the base core code. That said a readme instruction for adding them could be included. Not everyone will have/need these custom product fields..

chadderuski:

Your description edit feature (no popup) is pretty nice. Much simpler. Did you remove the ability to browse for an image? I didn't seen that.All that popup editing crap was just plan old over engineered crap which was more about flash and less about real needed functionality IMHO.. I don't remember any ability to browse for images..

chadderuski:

I thought about adding a delete check box, but then what do you do about linked products? Hmm... so I left well enough along :pI imagine that the functionality would be the same thing you do about linked products when deleting them from the admin product listings..

chadderuski:

Oh, just fyi. It seems the "Uninstall" button doesn't work... ??Right and this is a minor thing to address in the scheme of things since pricing is incorrectly adjusted using this module for products priced by attributes. I think this is a BIGGER priority to add to the module versus fixing the uninstaller.

Upgraded from 2.06 to 2.07 today on a 1.5.3 site. Only problem I had was 2.06 related: the GD uninstall button would not work so had to manually remove old configuration keys using phpMyAdmin.

Subsequently 2.07 installed just fine and works a treat.

Thanks Diva :hug:

Cheers / Frank

frank18:

Upgraded from 2.06 to 2.07 today on a 1.5.3 site. Only problem I had was 2.06 related: the GD uninstall button would not work so had to manually remove old configuration keys using phpMyAdmin.

Subsequently 2.07 installed just fine and works a treat.

Thanks Diva :hug:

Cheers / Frank

You're welcome.. Suggest upgrading.. Just pushed a new pull request this morning.. Can't take credit for implementing the improvements only identifying the need for them:laugh:..

DivaVocals:

You're welcome.. Suggest upgrading.. Just pushed a new pull request this morning.. Can't take credit for implementing the improvements only identifying the need for them:laugh:..

Goodie goodie - just pulled it :thumbsup:

Compared 2.08 to 2.07 and noted that the files

admin/includes/functions/extra_functions/quick_updates_functions.php
admin/includes/functions/extra_functions/reg_quick_updates.php

have been made obsolete.

If I understand it right the update procedure (2.07 > 2.08) is meant to be

1. Uninstall 2.07 using the 'Uninstall' button in admin (ofc backup first....)
2. delete the 2 files mentioned above
3. upload the 2.08 file set (ofc rename the admin folder first....)
4. log into admin again etc etc

And, if needed, use the included uninstall.sql to remove 2.08 ??

Sorry to be a PITN (medically defined as the milder form of PITA :p) but couldn't find that info in the readme's.

Cheers / Frank

frank18:

Goodie goodie - just pulled it :thumbsup:

Compared 2.08 to 2.07 and noted that the files

admin/includes/functions/extra_functions/quick_updates_functions.php
admin/includes/functions/extra_functions/reg_quick_updates.php

have been made obsolete.

If I understand it right the update procedure (2.07 > 2.08) is meant to be

1. Uninstall 2.07 using the 'Uninstall' button in admin (ofc backup first....)
2. delete the 2 files mentioned above
3. upload the 2.08 file set (ofc rename the admin folder first....)
4. log into admin again etc etc

And, if needed, use the included uninstall.sql to remove 2.08 ??

Sorry to be a PITN (medically defined as the milder form of PITA :p) but couldn't find that info in the readme's.

Cheers / Frank
Sounds right, but honestly I haven't test what the actual upgrade steps are and I have not upgraded the readme yet.... The site I was using this on was a test site.. So I wiped out everything and started over..

DivaVocals:

Sounds right, but honestly I haven't test what the actual upgrade steps are and I have not upgraded the readme yet.... The site I was using this on was a test site.. So I wiped out everything and started over..

Thanks a zillion, will try this on a local install sometime later tonite (weather is too nice now, need to take my dog for a run on the beach...)